4802f1d96a
Based on investigation by Matt, the tiller-deploy pod was running in the cluster network namespace and therefore not inheriting host TCP keepalive parameters. During a swact, when the floating IP is taken down, tiller keepalive is so large its the kube-apiserver detects the timeout after 15 minutes (5 probes * 180 seconds) The cluster namespace values are 9 probes at 75 second intervals. The host TCP values are 5 consecutive probes at 1 second intervals. By changing the tiller pod to be deployed using the host network, it will inherit the host sysctl values and detect much more quickly. (10 seconds) Adding additional override settings during helm init for tiller helm init <params> --override spec.template.spec.hostNetwork=true These changes were added to the ansible playbook. Change-Id: I218e4ef37100950c8ac5a0cb9759d9df50d9e368 Closes-Bug: 1817941 Partial-Bug: 1818123 Co-Authored-By: Matt Peters <Matt.Peters@windriver.com> Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
3 lines
41 B
Plaintext
3 lines
41 B
Plaintext
SRC_DIR="playbookconfig"
|
|
TIS_PATCH_VER=2
|