Fix --kubeconfig flag priority about arkade HOT 10 CLOSED

So looking at this issue it carries thru all app installs currently.

I would like to make following changes:

• use only the current kubectlTask and remove the kubectl function and add tests.
• change the helm3 function so that it returns the task as well and add tests

/cc @alexellis

from arkade.

use only the current kubectlTask and remove the kubectl function and add tests.

This sounds good, please go ahead and raise the first PR for it.

change the helm3 function so that it returns the task as well and add tests

There is no helm3() function, which do you mean?

from arkade.

helm3Upgrade

from arkade.

When should we expect a PR @phumberdroz ? 😄

from arkade.

Hopefully today @alexellis :)

from arkade.

Please could someone suggest a simpler alternative fix?

from arkade.

Sooo... Is this going to be fixed or ?

from arkade.

See my comment from a month ago. What specific issue are you running into? Some people don't set their KUBECONFIG variable correctly. If you do that, then you shouldn't need this flag.

from arkade.

My KUBECONFIG variable is set to ./kubeconfig but I figured that when setting the --kubeconfig paramenter, one could override which kubeconfig ark would use.

from arkade.

You should never use ./, always use pwd to get the whole absolute path. Otherwise it won't work when you move out of the folder or another app does.

from arkade.