Add an option to remove the need of floating IPs
Add support for an option to allow to provision a bay with no floating IPs. The rational is that not every clouds have floating IPs, and Magnum should be usable regardless of the cloud have floating IP or not.
Blueprint information
Related branches
Related bugs
Sprints
Whiteboard
Comments from Monty Taylor <email address hidden>:
Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have magnum work with all of the above.
* If the cloud does not require using a floating IP (as most do not) to get externally routable network access, magnum should work with that.
* If the cloud does require using a floating IP (as some do) to get externally rouatable network access, magnum should be able to work with that.
* In either case, it's also possible the user will not desire the thing they are deploying in magnum to be assigned an IP on a network that routes off of the cloud. That should also be supported.
Gerrit topic: https:/
Addressed by: https:/
Allow k8s cluster without Floating IP
Gerrit topic: https:/
Addressed by: https:/
Allow k8s cluster without LBaaS
Addressed by: https:/
Add floating_ip_enabled field to baymodel
(hongbin) Yuanying, it looks this feature has been implemented. Are we ready to close this BP?
Gerrit topic: https:/
Addressed by: https:/
[coreos] Allow k8s cluster without floating ip
Addressed by: https:/
[coreos] Allow k8s cluster without floating ip
Addressed by: https:/
Convert floating_ip_enabled from boolean to enum
