Use init-container to prepare /etc/hosts file for kube-vip

[glitchcrab]

let's try this to see if kube-vip works

kube-vip/kube-vip#692

[vxav]

[github-actions]

There were differences in the rendered Helm template, please check! ⚠️

Output

=== Differences when rendered with values file helm/cluster-vsphere/ci/test-wc-values.yaml ===

/stringData/content  (v1/Secret/release-name-kubevip-pod)
  ± value change in multiline text (one insert, no deletions)
    +   initContainers:
    +   - name: update-hosts-record
    +     image: gsoci.azurecr.io/giantswarm/busybox:1.37.0
    +     command: ["/bin/sh", "-c", "echo '127.0.0.1  kubernetes' >> /etc/hosts"]
  
  

[glitchcrab]

CI tested locally, cluster creation is fixed