snap helm cannot read configs #10
Comments
To my knowledge of Snapd, even with the |
@joedborg That doesn't sound right. kubectl is also installed through snap and it doesn't seem to have any issues accessing the specified config file(s). That being said, I'm not 100% sure that I've only ever used the snap kubectl binary and not inadvertently used a different binary that happened to get installed outside of snap. I'll keep an eye out going forward to see if I can confirm this or not. |
Same issue here with helm v2.7.2, Kubectl installed with snap can access ~/.kube/config. Is this because helm confinment is set to strict whereas kubectl confinment is set to classic ?
|
Hi @FredericLeroy, @ryan-peachey-seon, I have opened https://forum.snapcraft.io/t/classic-confinement-for-existing-helm-snap/4375/1 to get the snap moved to classic confinement as I agree that it should be as |
After installing using |
Helm should be packaged as classic snap (as kubectl snap does) to be able to access kubectl configurations in `~/.kube/config`. Already approved at https://forum.snapcraft.io/t/classic-confinement-for-existing-helm-snap/4375 Fixes snapcrafters#10
|
|
The issue does not seem fixed indeed.
Downloading the binaries and placing them in your path works fine though. |
Same issue here |
same here |
here as well. Finally just copied the file in desperation, but this is a serious pain in the neck. |
This is still an issue in 2.9.1 Helm, on both Stable and Edge. Why was this closed? |
My current workaround for this:
|
This isn't closed. The reference above your comment is for another repository by jonashackt having to do with Ansible. |
Snap has been classic for a while, so closing. If this is still an issue for anyone, please speak up and I'll reopen. |
There seems to be something weird with the snap version of helm as it's not properly reading cluster configs. The default via environment config is ignored, and even the manually specified parameter is also ignored.
config location:
Specific:
~/.kube/dev-k8s
Generic:
~/.kube/<env>-k8s
Environment Variable set:
Installation:
but the helm app is completely broken without forcing a single config file in a single location?
This completely ignores the env variable KUBECONFIG and also completely ignores the --kubeconfig parameter introduced in what I believe was v 2.6.1
When I manually install helm from tgz, this non-default configuration is not required
Installation:
helm just works with my config via environment variable
The text was updated successfully, but these errors were encountered: