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.

Sign up for GitHub

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

Jump to bottom

Allow to specify multiple clusters per get-kubeconfig command #567

Closed
raliev12 opened this issue Jun 9, 2021 · 1 comment
Closed

Allow to specify multiple clusters per get-kubeconfig command #567

raliev12 opened this issue Jun 9, 2021 · 1 comment
Assignees
@raliev12
Labels
7-NiceToHave Relates to issues of lower priority that are not part of critical functionality or have work arounds enhancement New feature or request priority/low Items that are considered non-critical for functionality, such as quality of life improvements size m
Milestone
v2.1

Comments

@raliev12
Copy link
Contributor

raliev12 commented Jun 9, 2021

Problem description (if applicable)
Currently it is possible to request kubeconfig for entire site (contains contexts with all clusters) or with just one context. No possibility to retrieve kubeconfig with variable amount of contexts of desired clusters.

Proposed change
Allow to specify multiple clusters per get-kubeconfig request and return kubeconfig with appropriate contexts.

Potential impacts
None.
@raliev12 raliev12 added enhancement New feature or request triage Needs evaluation by project members labels Jun 9, 2021
@jezogwza jezogwza added 7-NiceToHave Relates to issues of lower priority that are not part of critical functionality or have work arounds priority/low Items that are considered non-critical for functionality, such as quality of life improvements and removed triage Needs evaluation by project members labels Jun 9, 2021
@jezogwza jezogwza added this to the Future milestone Jun 9, 2021
@raliev12
Copy link
Contributor Author

raliev12 commented Jun 9, 2021

Please assign this one to me. The work in progress PS is here https://review.opendev.org/c/airship/airshipctl/+/794904

@eak13 eak13 added the size m label Jun 23, 2021
@eak13 eak13 modified the milestones: Future, v2.1 Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raliev12 raliev12

Labels
7-NiceToHave Relates to issues of lower priority that are not part of critical functionality or have work arounds enhancement New feature or request priority/low Items that are considered non-critical for functionality, such as quality of life improvements size m
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
3 participants
@eak13 @jezogwza @raliev12