Open wingying opened 1 month ago
Yes, you probably use some advanced volume features, and in that case you need to mound the root directory of the local-path-provisioner (/var/local-path-provisioner
) into the kubelet: documentation.
You'd need to patch the machine config with something like:
machine:
kubelet:
extraMounts:
- destination: /var/local-path-provisioner
type: bind
source: /var/local-path-provisioner
options:
- bind
- rshared
- rw
interesting, I patch the node, some helmrelease within local-path storageclass works while some not work, like error below:
though I patched the node successfully, but same issue message.
Hard to say check the volume path using talosctl ls
. Local-path-provisioner works without issues with Talos so far (we have integration tests). So there might be some misconfiguration, but hard to guess.
is it expected result or not?
I don't know, it's hard to read screenshots. Probably you should ls
the volume path?
I listed related folder
talosctl --talosconfig=./talosconfig -n 10.95.115.126 ls /var/local-path-provisioner . pvc-345bf6d9-e7c0-4427-a801-8f6235436fc6_cdp-system_git-server pvc-43a3614b-2970-4892-80c4-735c75ac549a_cdp-system_git-server pvc-95a52b13-df22-4aae-a605-8b049207e3d6_cdp-foundation_storage-loki-0
seems related pvc not created while others works.
Bug Report
Description
Hi,
I installed Talos v1.7.5, one controlpanel and one worker node, and I installed local-path-provisioner v0.0.28 as storageclass. ocal-path-provisioner v0.0.28 is installed successfully, however, when I tried to install any helmchart, like loki, git-server, pvc cannot mounted successfully. See error message below from loki pod, and the pod keep in creating status.
loki pod log:
However, it display pv and pvc were created successfully from local-path-provisioner pod
local-path-provisioner pod log:
More Information
Below are troubleshooting steps I did:
Could you help me the issue?