Skip to content
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

Support import of a cluster that is the non-active kubecontext in a kubeconfig #197

Closed
gurnben opened this issue Apr 12, 2022 · 0 comments
Closed
Assignees
Labels
enhancement New feature or request (Release Note New Feature)

Comments

@gurnben
Copy link
Member

gurnben commented Apr 12, 2022

Summary of Request

Currently, if you run oc cm attach cluster <name> --cluster-kubeconfig=<some-kubeconfig-file>, it will only import the cluster indicated by the active kubecontext in that kubeconfig file.

Ideally, the user could provide the name of a kubecontext in a kubeconfig file for import like:

oc cm attach cluster <name> --cluster-kubeconfig=<some-kubeconfig-file> --cluster-kubecontext=<context>
@itdove itdove added the enhancement New feature or request (Release Note New Feature) label Apr 12, 2022
@itdove itdove self-assigned this Apr 12, 2022
@itdove itdove closed this as completed Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request (Release Note New Feature)
Projects
None yet
Development

No branches or pull requests

2 participants