Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: update kubeconfig logic to use kubconfig, clustername, and context name #84

Closed
qdzlug opened this issue Feb 2, 2022 · 0 comments · Fixed by #167
Closed

feat: update kubeconfig logic to use kubconfig, clustername, and context name #84

qdzlug opened this issue Feb 2, 2022 · 0 comments · Fixed by #167
Assignees
Labels
enhancement New feature or request

Comments

@qdzlug
Copy link
Contributor

qdzlug commented Feb 2, 2022

Is your feature request related to a problem? Please describe.
Currently, we only use the kubeconfig file when running. This works well when there is only one K8 installation defined in the configuration file, but can cause issues if there are multiple clusters and contexts.

Describe the solution you'd like
We should prompt for, validate, and use all three pieces of information when addressing a cluster.

Describe alternatives you've considered
None.

Additional context
None.

@qdzlug qdzlug added the enhancement New feature or request label Mar 15, 2022
@qdzlug qdzlug linked a pull request Aug 19, 2022 that will close this issue
7 tasks
@qdzlug qdzlug self-assigned this Aug 19, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant