-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ensure kubeclient ns is release ns for helm actions #2652
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thorbenbelow Thank you for this update Thornben!
Signed-off-by: Thorben Below <56894536+thorbenbelow@users.noreply.github.com>
6064dc4
to
3cc1a32
Compare
Hello all, when will this PR get merged? It can cause huge problems. |
Hey @derailed, are you missing something in this PR for it to be mergeable? |
Don't want to start a dogpile here, but this bug also manifests in how Helm rollbacks works, it appears, and has caused a production incident for us in the past using k9s. Would love to see this fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thorbenbelow Thank you for the updates Thornben
Signed-off-by: Thorben Below <56894536+thorbenbelow@users.noreply.github.com>
Fixes #2634
Also looks like this is the same issue as with #1033
From my understanding helm will use the namespace from
flags
to determine where it runs actions. Imo this should always be the release namespace.