-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tillerless: Wrong kubeContext is ignored #642
Comments
I've checked it out without tillerless plugin and it worked as expected. The following error message was shown:
So it is a tillerless plugin causing this issue. |
I bet it's related to this one: rimusz/helm-tiller#32 |
I think this also brakes the possibility to manage kubeContex based on the environment. So, this
will be ignored even if gke_XXXX_europe-west1-b_mydevcluster is a valid context. The workaround is to deal with context outside of the helmfile, but it's not the best solution for sure. |
Probably we should rename the issue. |
Ah, thanks! The helm-tiller issue you've shared makes sense.
Theoretically we can enhance But helm-tiller is implemented in (perhaps posix) shell AND I believe that's why @rimusz has suggested setting |
So it's getting very interesting... Which of the following works for you?
|
I thought about almost the same you described under 2. |
@mumoshu, since Helm 3 is GA, should we probably close this issue? I don't think anybody will work on it. |
@andrewnazarov Thanks for triaging this - Yes, I believe we can close this now! |
I've noticed that if I set kubeContext to the wrong value (i.e. the value that doesn't match any existing kube contexts) it will get silently ignored and the existing one will be used. I'm using tillerless helm plugin.
Some snippets
Notice that kubeContext is set to wrong_kubecontext.
I don't have the context of that name.
wrong_kubecontext is passed to
helm ..
command, but nothing wrong happens.Versions:
Probably it's not a helmfile issue, but anyway. If the expected behaviour is spitting errors it should be consistent.
The text was updated successfully, but these errors were encountered: