Endpoint changes with k8s 1.5 about gluster-kubernetes HOT 8 CLOSED

It will be removed with when OCP 3.5 is released or we could even have version specific defs

from gluster-kubernetes.

Here's an example of k8s automatically creating the endpoint:

ubuntu@kube1:~$ sudo kubectl create -f docs/examples/hello_world/gluster-pvc.yaml
persistentvolumeclaim "gluster1" created
ubuntu@kube1:~$ sudo kubectl get endpoints
NAME                         ENDPOINTS                                      AGE
glusterfs-dynamic-gluster1   172.16.35.11:1,172.16.35.12:1,172.16.35.13:1   10s
heketi                       192.168.149.139:8080                           23h
heketi-storage-endpoints     172.16.35.11:1,172.16.35.12:1,172.16.35.13:1   23h
kubernetes                   172.16.35.11:6443                              2d

from gluster-kubernetes.

@screeley44 OCP? Sorry, not familiar with that.

from gluster-kubernetes.

OpenShift Container Platform - I don't think Kubernetes 1.5 is officially released yet is it? OCP is always behind Kube as that is downstream and Kube is upstream, so we might have to manage those differences in some way, I guess we also need an OCP version of HelloWorld doc as well

from gluster-kubernetes.

OK, thanks. Familiar with OpenShift, just not that acronym. Kubernetes v1.5 was just released a couple days ago.

from gluster-kubernetes.

We do need to maintain compatibility with both Kubernetes and OpenShift. This will require a few changes in various places, starting with https://github.com/heketi/heketi. The setup-openshift-heketi-storage command of heketi-cli will need to be trimmed down so it only creates the DB secret and the copy job. Then we'll still need to create the endpoints manually for OpenShift and also Kube < 1.5 (which will require a version check). Once these things are done we should be able to get away with not creating them for Kube 1.5.

@ravishivt Would you be willing to open the issue on the heketi project, as a compatibility request for Kubernetes 1.5?

from gluster-kubernetes.

Sure, heketi/heketi#628

from gluster-kubernetes.

Since this PR was last updated, it has been determined that the heketi-storage-endpoints are still required since the heketidbstorage volume is statically provisioned. Further, the Hello World example has been updated to indicate that endpoints: should be omitted from Kube >= 1.6.

from gluster-kubernetes.