Add ingress controller configuration and backend to kubernetes clusters.
A new label 'ingress_controller' defines which backend should serve
ingress, with traefik added as the only option for now.
It is defined as a DaemonSet, with instances on all nodes defined with a
certain role. This role is set as an additional cluster label
'ingress_controller_role', with a default value of 'ingress'.
For now no node is automatically set with this role, with users or operators
having to do this manually after cluster creation.
Reviewed: https:/ /review. openstack. org/528756 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=0b18989a50e c7c7323d23f5e84 c94dda70363fba
Committed: https:/
Submitter: Zuul
Branch: master
commit 0b18989a50ec7c7 323d23f5e84c94d da70363fba
Author: Ricardo Rocha <email address hidden>
Date: Mon Dec 18 16:31:30 2017 +0000
[kubernetes] add ingress controller
Add ingress controller configuration and backend to kubernetes clusters.
A new label 'ingress_ controller' defines which backend should serve
ingress, with traefik added as the only option for now.
It is defined as a DaemonSet, with instances on all nodes defined with a controller_ role', with a default value of 'ingress'.
certain role. This role is set as an additional cluster label
'ingress_
For now no node is automatically set with this role, with users or operators
having to do this manually after cluster creation.
Change-Id: I5175cf91f37e29 88dc3d33042558d 994810842f3
Closes-Bug: #1738808