Revert "Revert "Changing tiller pod networking settings to improve swact time""

This reverts commit fe10dcbfed.

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: I89c4db6dc063f238c70fad4e913577046e5452f5
Related-Bug: 1817941
Partial-Bug: 1837055
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>

playbookconfig/src/playbooks/bootstrap/roles/bringup-essential-services/tasks/bringup_helm.yml

@@ -142,6 +142,7 @@
   command: >-
     helm init --skip-refresh --service-account tiller --node-selectors
     "node-role.kubernetes.io/master"="" --tiller-image={{ tiller_img }}
+    --override spec.template.spec.hostNetwork=true
   become_user: sysadmin
   environment:
     KUBECONFIG: /etc/kubernetes/admin.conf
@@ -155,6 +156,7 @@
     command: >-
       helm init --skip-refresh --service-account tiller --node-selectors
       "node-role.kubernetes.io/master"="" --tiller-image={{ tiller_img }}
+      --override spec.template.spec.hostNetwork=true
     environment:
       KUBECONFIG: /etc/kubernetes/admin.conf
       HOME: /home/sysadmin