From 48e42ec07b32c5e79000cc37ee7bbbfda4b724c7 Mon Sep 17 00:00:00 2001 From: Diogo Guerra Date: Thu, 4 Jul 2019 16:09:39 +0200 Subject: [PATCH] Allow for cluster-autoscaler deployment roll-out hostNetwork: True ties the pod to the host ip:port. When a CA update roll-out is triggered, the new pod cannot bind to the port because it is already in use by the pod to be replaced, making the new pod fail, and in consequence the update. This patch removes this restriction Story: 2006161 Task: 35670 Change-Id: I039b2ed91c9623883635bf9e72d85135f1bdae89 Signed-off-by: Diogo Guerra --- .../common/templates/kubernetes/fragments/enable-auto-scaling.sh | 1 - 1 file changed, 1 deletion(-) diff --git a/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-scaling.sh b/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-scaling.sh index d9e09e7ad6..132a5b0f28 100644 --- a/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-scaling.sh +++ b/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-scaling.sh @@ -108,7 +108,6 @@ spec: node-role.kubernetes.io/master: "" securityContext: runAsUser: 1001 - hostNetwork: True tolerations: - effect: NoSchedule operator: Exists