snap helm cannot read configs

[ryan-peachey-seon]

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:

$ echo $KUBECONFIG
/home/rpeachey/.kube/dev-k8s

Installation:

$ sudo snap refresh helm --edge
helm (edge) 2.6.2 from 'snapcrafters' refreshed
$ which helm
/snap/bin/helm

but the helm app is completely broken without forcing a single config file in a single location?

$ helm version
Please copy Kubernetes config to /home/rpeachey/snap/helm/common/kube/config.

This completely ignores the env variable KUBECONFIG and also completely ignores the --kubeconfig parameter introduced in what I believe was v 2.6.1

$ helm --kubeconfig ~/.kube/dev-k8s version
Please copy Kubernetes config to /home/rpeachey/snap/helm/common/kube/config.

When I manually install helm from tgz, this non-default configuration is not required
Installation:

$ mkdir helm && cd helm
$ wget https://storage.googleapis.com/kubernetes-helm/helm-v2.6.2-linux-amd64.tar.gz
$ tar -zxvf helm-v2.6.2-linux-amd64.tar.gz
$ cd ~ && mkdir bin
$ ln -sf ~/helm/linux-amd64/helm ~/bin/helm

helm just works with my config via environment variable

$ helm init
Creating /home/rpeachey/.helm 
Creating /home/rpeachey/.helm/repository 
Creating /home/rpeachey/.helm/repository/cache 
Creating /home/rpeachey/.helm/repository/local 
Creating /home/rpeachey/.helm/plugins 
Creating /home/rpeachey/.helm/starters 
Creating /home/rpeachey/.helm/cache/archive 
Creating /home/rpeachey/.helm/repository/repositories.yaml 
$HELM_HOME has been configured at /home/rpeachey/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Happy Helming!

$ helm version
Client: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}

[joedborg]

Hi @ryan-peachey-seon,

To my knowledge of Snapd, even with the home plug, snapped apps cannot read hidden dirs and files. A workaround would be to set $KUBECONFIG to a non-hidden directory.

[ryan-peachey-seon]

@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.

[FredericLeroy]

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 ?
Do you plan to fix the issue ?

± snap info --verbose helm
name:      helm
summary:   The Kubernetes package manager
publisher: snapcrafters
contact:   https://github.com/snapcrafters/helm/issues
license:   unknown
description: |
  Helm is a tool for managing Kubernetes
  charts. Charts are packages of
  pre-configured Kubernetes resources.
snap-id: VY12auPDSljUlac4CZaOdMExw7IASsgB
commands:
  - helm
notes:               
  private:           false
  confinement:       strict
  devmode:           false
  jailmode:          false
  trymode:           false
  enabled:           true
  broken:            false
  ignore-validation: false
tracking:            stable
installed:           2.7.2 (26) 9MB 
refreshed:           2017-11-28 13:13:52 +0100 CET
channels:                       
  stable:            2.7.2 (26) 9MB -
  candidate:         2.7.2 (26) 9MB -
  beta:              2.7.2 (26) 9MB -
  edge:              2.7.2 (26) 9MB -

[joedborg]

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 kubectl.

[jcassee]

After installing using --classic, calling helm without the wrapper seems to work fine. No need for ~/snap/helm/common/kube/config.

[zub0r]

sudo snap install --classic helm didn't help, does this need to be merged first?

[gjergjkastrioti]

sudo snap install --classic helm didn't work. I gave up trying Snap and used the Script installation instead, works fine.

[plallin]

The issue does not seem fixed indeed.

$ snap install helm --classic
helm 2.9.1 from 'snapcrafters' installed
$ helm 
Please copy Kubernetes config to /home/pauline/snap/helm/common/kube/config.

Downloading the binaries and placing them in your path works fine though.

[mhjort]

Same issue here

[Oblynx]

same here

[jpnarkinsky]

here as well. Finally just copied the file in desperation, but this is a serious pain in the neck.

[dankirkpatrick]

This is still an issue in 2.9.1 Helm, on both Stable and Edge. Why was this closed?

[ricardofbarros]

My current workaround for this:

sudo snap install helm --classic
ln -s /home/$(whoami)/.kube/config /home/$(whoami)/snap/helm/common/kube/config

[codycraven]

This is still an issue in 2.9.1 Helm, on both Stable and Edge. Why was this closed?

This isn't closed. The reference above your comment is for another repository by jonashackt having to do with Ansible.

[joedborg]

Snap has been classic for a while, so closing. If this is still an issue for anyone, please speak up and I'll reopen.