The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
/var/lib/rancher/k3s/server/manifests/ should not contain any manifests after creating cluster. This was fixed in the past but it might have snuck back in when refactoring? The issue is that if manifests are there, the will be reapplied by k3s which doesn't allow you to upgrade or change those manifests without editing them directly.
Expected Behavior
/var/lib/rancher/k3s/server/manifests/should not contain any manifests after creating cluster. This was fixed in the past but it might have snuck back in when refactoring? The issue is that if manifests are there, the will be reapplied by k3s which doesn't allow you to upgrade or change those manifests without editing them directly.