From 8bad8db978ff04ca7ec5a106541dc6ced2b5eca8 Mon Sep 17 00:00:00 2001
From: cyberops7 <18562612+cyberops7@users.noreply.github.com>
Date: Sun, 5 Jul 2026 21:18:24 -0600
Subject: [PATCH] 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 | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/Kubernetes/K3S-Deploy/kube-vip b/Kubernetes/K3S-Deploy/kube-vip
index 389c626..91185c8 100644
--- a/Kubernetes/K3S-Deploy/kube-vip
+++ b/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: {}