[stable/kong] specify ingress class for Ingress Controller (#10031)

If multiple Kong Ingress controllers are deployed with different
ingress-class parameters to satisfy different kinds of ingresses
in the same k8s cluster,
they will attempt to take aquire leader status on the same
election key, meaning only one of the ingress-class will ever be
satisfied.

This change ensures that a unique key is used for leader election for
every ingress-class.

Signed-off-by: Harry Bagdi <harrybagdi@gmail.com>
This commit is contained in:
Harry
2018-12-15 17:46:52 -08:00
committed by Kubernetes Prow Robot
parent a0392d8ab6
commit 68cb50cdfa
2 changed files with 2 additions and 1 deletions
+1 -1
View File
@@ -12,5 +12,5 @@ maintainers:
name: kong
sources:
- https://github.com/Kong/kong
version: 0.6.7
version: 0.6.8
appVersion: 0.14.1
@@ -120,6 +120,7 @@ spec:
- --publish-service={{ .Release.Namespace }}/{{ template "kong.fullname" . }}-proxy
# Set the ingress class
- --ingress-class={{ .Values.ingressController.ingressClass }}
- --election-id=kong-ingress-controller-leader-{{ .Values.ingressController.ingressClass }}
env:
- name: POD_NAME
valueFrom: