-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provisioner on k3s switches namespace, config after reboot #232
Comments
@samstride |
@derekbit , thanks for responding. When I installed I reinstalled the provisioner in Here is the output you requested: kubectl get pods -A | grep local-path-provisioner
kube-system local-path-provisioner-84bb864455-47fv4 1/1 Running 2 (2d16h ago) 13d Another thing that happens after a restart, is that the configmap seems to change. I originally had something like this:
Then after a node restart, it changed to this:
There is a small possibility that the k3s version might have upgraded from |
some problem with "v1.22.5+k3s1". I update the local-path-config configmap to use the other disk volume other than the default patch. When retart the pods "local-path-provisioner-xxxx", it OK. But when restart the k3s, it restore to default path "/var/lib/rancher/k3s/storage". I also try to update the config under /var/lib/rancher/k3s/server/manifests/local-storage.yaml. the effect is the same, when restart k3s, it also restore to default path. |
@chenyg0911 The default path in k3s is set by |
Is there any way to make the configuration stick other than restart k3s with |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Hi,
Thanks for maintaining this repo.
I have installed the provisioner on a single node
k3s
cluster (home lab) using:The provisioner originally installs itself in namespace
local-path-storage
.However, after a node restart (power outage), the provisioner has deployments and configs setup in
kube-system
and the original deployment fails with an error regarding service account permissions. Sorry, don't have the exact message handy.Thanks.
The text was updated successfully, but these errors were encountered: