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.
This fixes an "issue" that causes manifests to be reapplied each time the k3s service is started. This will remove the contents of /var/lib/rancher/k3s/server/manifests after the cluster has applied the files.
This fixes an "issue" that causes manifests to be reapplied each time the k3s service is started. This will remove the contents of
/var/lib/rancher/k3s/server/manifestsafter the cluster has applied the files.k3s advanced docs
If you are experiencing this with you cluster, the fix is simple
remove the contents of
/var/lib/rancher/k3s/server/manifestsfrom each server (leave the manifest files in place).This closes #51