[stable/kong] specify ingress class for Ingress Controller (helm#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 <[email protected]>
PTC-Global · Dec 16, 2018 · 68cb50c · 68cb50c
1 parent a0392d8
commit 68cb50c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/stable/kong/Chart.yaml b/stable/kong/Chart.yaml
@@ -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
diff --git a/stable/kong/templates/controller-deployment.yaml b/stable/kong/templates/controller-deployment.yaml
@@ -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: