Revert "Revert "Changing tiller pod networking settings to improve swact time""
This reverts commit fe10dcbfed9fd4a6b0e4494cd6d414bf78f03bab.
It was thought that setting the TCP timeouts for the cluster
network was enough to address the issues with the helm commands
hanging after a controller swact. This is not the case. In
particular, swacting away from the controller with the
tiller-deploy pod seems to cause tcp connection from that pod to
the kube-apiserver to hang. Putting the tiller-deploy pod back on
the host network "fixes" the issue.
Reviewed: https:/ /review. opendev. org/672742 /git.openstack. org/cgit/ starlingx/ ansible- playbooks/ commit/ ?id=5a1fe1616e1 c541a4cdd076b67 2f217c22d5c843
Committed: https:/
Submitter: Zuul
Branch: master
commit 5a1fe1616e1c541 a4cdd076b672f21 7c22d5c843
Author: Bart Wensley <email address hidden>
Date: Wed Jul 24 14:41:57 2019 -0500
Revert "Revert "Changing tiller pod networking settings to improve swact time""
This reverts commit fe10dcbfed9fd4a 6b0e4494cd6d414 bf78f03bab.
It was thought that setting the TCP timeouts for the cluster
network was enough to address the issues with the helm commands
hanging after a controller swact. This is not the case. In
particular, swacting away from the controller with the
tiller-deploy pod seems to cause tcp connection from that pod to
the kube-apiserver to hang. Putting the tiller-deploy pod back on
the host network "fixes" the issue.
Change-Id: I89c4db6dc063f2 38c70fad4e91357 7046e5452f5
Related-Bug: 1817941
Partial-Bug: 1837055
Signed-off-by: Bart Wensley <email address hidden>