-
Notifications
You must be signed in to change notification settings - Fork 461
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
Properly use custom kubeconfig for all clientsets #1110
Conversation
53bdca4
to
b6f95bd
Compare
b6f95bd
to
8286de6
Compare
Rebased against latest branch. |
Ping, is this waiting for something? |
ace6f38
to
fbaf567
Compare
pinging again |
fbaf567
to
b4595c6
Compare
Hello, rebased again. Apologies for bumping the PR repeatedly, but we would greatly benefit from this fix. Is it possible to move this forward? Thank you |
PTAL @dvaldivia @Alevsk @cniackz |
Hi, any updates on this? Thanks! |
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.
It looks good to me.
Tested to create the tenant with this change, is not breaking the logic as far as I can see it.
Plus it allows the config to be loaded in advance.
Summary
Closes #1109
Notes
This change works for me. I think it would make sense to pull the
clientcmd.ClientConfig
creation in a separate function to avoid code duplication (and similar issues in the future), but I decided against it, as it touches more parts of the codebase than I believe are required.I'd be willing to go ahead with the change if the maintainers find that it is OK.