Closed lainra closed 3 years ago
@Lain92 did you reload the daemon config and restart the kubelet after placing the ENV variables in .service
?
$ systemctl daemon-reload
$ systemctl restart kubelet
@wallnerryan yes, i did it dozens of times while troubleshooting
FYI, This project is moving to https://github.com/ScatterHQ/flocker, a small number of the clusterhq folks will try to maintain it to a certain degree if the community wants it.
Hello,
I tried to install Flocker with my Kubernetes cluster. K8s version : 1.5.1 Flocker version : 1.15.0 I have problems similar to this old issue : https://github.com/kubernetes/kubernetes/issues/17651 My nodes are on Centos 7.3. I'm using VMWare-flocker-plugin to provision the storage. Everything is working as long as it doesn't deal with Kubernetes. I tried both https://clusterhq.com/2015/12/22/ha-demo-kubernetes-flocker/ demo and https://github.com/vmware/vsphere-flocker-driver installation instructions.
The problem is that kubelet cannot reach the control node because it cannot fetch the environment variables : FLOCKER_CONTROL_SERVICE_HOST FLOCKER_CONTROL_SERVICE_PORT FLOCKER_CONTROL_SERVICE_CA_FILE FLOCKER_CONTROL_SERVICE_CLIENT_KEY_FILE FLOCKER_CONTROL_SERVICE_CLIENT_CERT_FILE
I tried every single way to pass these variables :
Unfortunately, kubelet/flocker-agent doesn't seem to get these variables.
The datasetUUID for volume with datasetName='volume1' can not be found using flocker: Get https://localhost:4523/v1/configuration/datasets: dial tcp 127.0.0.1:4523: getsockopt: connection refused
This is because the https://github.com/kubernetes/kubernetes/blob/v1.5.1/pkg/volume/flocker/flocker.go defines default variables as :I took the flocker.go module NewClient function from kubernetes/kubernetes github to test it on my machine :
and I get the variable :
I don't know what to do, there is only this problem left for my Kubernetes to work with Flocker.