K3S-Deploy: regenerate kube-vip with --inCluster for k3s

The kubeadm default mounts /etc/kubernetes/admin.conf, which does not
exist on k3s. --inCluster uses the kube-vip ServiceAccount (provided by
the applied rbac.yaml) instead, which is the correct mode for k3s.

Kubernetes/K3S-Deploy/kube-vip

@@ -75,22 +75,12 @@ spec:
             - NET_RAW
             drop:
             - ALL
-        volumeMounts:
-        - mountPath: /etc/kubernetes/admin.conf
-          name: kubeconfig
-      hostAliases:
-      - hostnames:
-        - kubernetes
-        ip: 127.0.0.1
       hostNetwork: true
+      serviceAccountName: kube-vip
       tolerations:
       - effect: NoSchedule
         operator: Exists
       - effect: NoExecute
         operator: Exists
-      volumes:
-      - hostPath:
-          path: /etc/kubernetes/admin.conf
-        name: kubeconfig
   updateStrategy: {}