From: "OTSUKA, Motohiro" <yuany...@oeilvert.org<mailto:yuany...@oeilvert.org>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Monday, July 13, 2015 at 8:11 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum] The way magnum-conductor communicates with k8s master
Hi, Wanghua Currently magnum-conductor can communicates with k8s master which has a floating ip in all-in-one deployment. But if magnum-conductor is not deployed on the neutron network node which has the br-ex, how can magnum-conductor communicate with k8s master. The magnum-conductor node then has no access to the k8s master. Currently this is a limitation of our architecture. The floating IP is a public routed network, so it should be able to communicate in a properly setup cloud. Another question: Magnum-conductor only communicate with k8s master, why k8s minion has a floating ip too? What is the floating ip of k8s minion used for? I think, there is no reason. Historically, Our heat template come from larsks/heat-kubernetes [1] template. larsks/heat-kubernetes provides floating ip to minion nodes, this is just a reason. The minion floating ips are needed to access the micro-service front ends from the internet. Regards -steve [1]: https://github.com/larsks/heat-kubernetes Thanks -Yuanying
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
