0b18989a50
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. Change-Id: I5175cf91f37e2988dc3d33042558d994810842f3 Closes-Bug: #1738808
9 lines
350 B
YAML
9 lines
350 B
YAML
---
|
|
features:
|
|
- |
|
|
Add new labels 'ingress_controller' and 'ingress_controller_role' enabling
|
|
the deployment of a Kubernetes Ingress Controller backend for clusters.
|
|
Default for 'ingress_controller' is '' (meaning no controller deployed),
|
|
with possible values being 'traefik'.
|
|
Default for 'ingress_controller_role' is 'ingress'.
|