Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

asked 2018-05-15 20:34:10 -0500

don gravatar image

Magnum enable cloud-controller-manager

I see that magnum creates a file /etc/kubernetes/kube_openstack_config. But this doesn't seem to be used. I'm finding that my external-ip stay pending for ever on services using e.g. https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/master/examples/loadbalancers/external-http-nginx.yaml

It seems that there should be a cloud-controller-manager running (https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/), presumably w/ some access to that file.

The kube_openstack_config seems to be setup properly. And heat's bit is working (e.g. creating instances, creating load-balancers for the API). But the post-heat bits are not working.

External cloud managers were intro into 1.6 of Kubernetes, and I'm on 1.9.3.

I'm not clear on whether magnum should have enabled this, or whether I am to do it manually and feed it that file.

https://github.com/kubernetes/cloud-provider-openstack has the docs on the subject I guess.

Does anyone have any input? is anyone actually using magnum?

Magnum enable cloud-controller-manager

I see that magnum creates a file /etc/kubernetes/kube_openstack_config. But this doesn't seem to be used. I'm finding that my external-ip stay pending for ever on services using e.g. https://raw.githubusercontent.com/kubernetes/cloud-provider-openstack/master/examples/loadbalancers/external-http-nginx.yaml

It seems that there should be a cloud-controller-manager running (https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/), presumably w/ some access to that file.

The kube_openstack_config seems to be setup properly. And heat's bit is working (e.g. creating instances, creating load-balancers for the API). But the post-heat bits are not working.

External cloud managers were intro into 1.6 of Kubernetes, and I'm on 1.9.3.

I'm not clear on whether magnum should have enabled this, or whether I am to do it manually and feed it that file.

https://github.com/kubernetes/cloud-provider-openstack has the docs on the subject I guess.

Does anyone have any input? is anyone actually using magnum?

from looking @ the code, it seems like TRUST_ID needs to be set (and its empty, so the bash script on master/minion have not populated). I do have

magnum-api/magnum.conf:trustee_domain_admin_password = XXXX                                                                          
magnum-api/magnum.conf:trustee_domain_admin_name = magnum_trustee_domain_admin                                                                                           
magnum-api/magnum.conf:trustee_domain_name = magnum

i'm not sure if that is the trust_id referred to. If i do a 'trust list', I see two (both for heat). Was one of them meant to be passed?

I also see https://bugs.launchpad.net/magnum/+bug/1762743 and https://github.com/kubernetes/cloud-provider-openstack/issues/48 suggests that we are still using the inbuilt provider.

What is the TRUST_ID referred to the script? How would I populate that?