-
Notifications
You must be signed in to change notification settings - Fork 123
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
fix : rules to load client configuration to connect to a kubernetes cluster #419
Conversation
Hello @sudermanjr @transient1 Any news please ? Thanks in advance. Sophian |
Hello @sudermanjr @transient1 Any news please ? Thanks in advance. Sophian |
@smehboub can you please rebase your PR? |
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.
Looks like this needs a rebase now.
fdb6093
to
e2faddd
Compare
Hello @sudermanjr Thanks you for feedbacks, It's done. Rgs, |
93f8063
to
9bbfea2
Compare
9bbfea2
to
19e0fbe
Compare
Hi, @smehboub . Just wanted to let you know I will be reviewing this PR over the next day or so. |
Thank you :-) |
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.
LGTM. Thanks for the contribution!
Thank you too :-) |
fix : rules to load client configuration to connect to a kubernetes cluster
This PR :
Fixes #418
Checklist
Description
What's the goal of this PR?
The same rules to load client configuration for all commands that need to connect to a kubernetes cluster
What changes did you make?
Use the same way to load client configuration to connect to a kubernetes cluster as the detect-helm command for all commands
What alternative solution should we consider, if any?
None