From 68cb50cdfaa423afc6c0c99a7adbf09af71e9a97 Mon Sep 17 00:00:00 2001 From: Harry Date: Sat, 15 Dec 2018 17:46:52 -0800 Subject: [PATCH] [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 --- stable/kong/Chart.yaml | 2 +- stable/kong/templates/controller-deployment.yaml | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/stable/kong/Chart.yaml b/stable/kong/Chart.yaml index bdadb12943..8257a9fbdf 100644 --- 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 index 7824bde6f6..851abd7cb6 100644 --- 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: