openstack
/
magnum
Code Issues Proposed changes

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 <dy090.guerra@gmail.com>
This commit is contained in:
Diogo Guerra 2019-07-04 16:09:39 +02:00 committed by Diogo Guerra
parent 8146e8d737
commit 48e42ec07b
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
magnum/drivers/common/templates/kubernetes/fragments/enable-auto-scaling.sh
View File

@ -108,7 +108,6 @@ spec:
node-role.kubernetes.io/master: ""
securityContext:
runAsUser: 1001
hostNetwork: True
tolerations:
- effect: NoSchedule
operator: Exists