From 7a106352a69c0965b96fa7089e3bf616bcb02c6d Mon Sep 17 00:00:00 2001 From: Valerii Ponomarov Date: Wed, 23 Aug 2023 19:33:37 +0300 Subject: [PATCH] fix(k8s-eks): use latest haproxy ingress controller version With the scylla-operator-1.10 we started getting HA problems [1] with the 'haproxy' service. So, fix it by using the latest available ingress controller version for haproxy. [1] https://github.com/scylladb/scylla-operator/issues/1341 --- .../10_haproxy-kubernetes-ingress.deploy.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdcm/k8s_configs/ingress-controller/10_haproxy-kubernetes-ingress.deploy.yaml b/sdcm/k8s_configs/ingress-controller/10_haproxy-kubernetes-ingress.deploy.yaml index 6229f6d3fd..195769a069 100644 --- a/sdcm/k8s_configs/ingress-controller/10_haproxy-kubernetes-ingress.deploy.yaml +++ b/sdcm/k8s_configs/ingress-controller/10_haproxy-kubernetes-ingress.deploy.yaml @@ -24,7 +24,7 @@ spec: serviceAccountName: haproxy-kubernetes-ingress containers: - name: haproxy-ingress - image: haproxytech/kubernetes-ingress:1.9.0 + image: haproxytech/kubernetes-ingress:1.10.6 args: - --configmap=haproxy-controller/haproxy-kubernetes-ingress - --default-backend-service=haproxy-controller/haproxy-kubernetes-ingress-default-backend