/etc/rancher/k3s directory does not exist, causing `FileOrCreate` hostpath mount for `/etc/rancher/k3s/k3s.yaml` to fail. about cilium HOT 3 OPEN

Thanks for this issue @andsens, but I'm not sure if Cilium can fix this for you. That setting sets where the kubeconfig is stored, and defaults to "~/.kube/config" as per

It seems like the method you are using to install Cilium on k3s is overriding that?

Per https://kubernetes.io/docs/concepts/storage/volumes/#hostpath-volume-types, the FileOrCreate mode does not create parent directories, sadly.

from cilium.

Agreed. Though I think it's more of a documentation issue in this case. The docs state that things should just work when spinning up k3s nodes, which is not true. A note regarding this would help a lot I think.
I also discovered that the default k8sServiceHost setting in helm is 127.0.0.1, which tripped me up even further. Adding a note telling the user to specify --set k8sServiceHost=<K8SAPI IP/HOSTNAME> if they intend to run multiple k3s nodes would help enormously.

from cilium.

Thanks for that, yes, I agree that documentation updates would be ideal. As always, PRs are welcome (😄 ), otherwise I will assign this to the correct team and they will prioritize it accordingly.

from cilium.