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

clusterctl support for downloading kubeconfig as context within existing kubeconfig #10133

Open
ivelichkovich opened this issue Feb 9, 2024 · 6 comments · May be fixed by #11942
Open

clusterctl support for downloading kubeconfig as context within existing kubeconfig #10133

ivelichkovich opened this issue Feb 9, 2024 · 6 comments · May be fixed by #11942
Assignees
@AvineshTripathi
Labels
area/clusterctl Issues or PRs related to clusterctl help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ivelichkovich
Copy link

ivelichkovich commented Feb 9, 2024 •
edited
Loading

What would you like to be added (User Story)?

As a developer & operator & user I want to be able to load kubeconfigs into an existing kubeconfig. So that I can have a single kubeconfig as contexts of all my clusters for ease of switching between clusters.

Detailed Description

A kubeconfig flag in "clusterctl get kubconfig" which will create the file or add the kubeconfig as a new context.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
/area clusterctl
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/clusterctl Issues or PRs related to clusterctl needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 9, 2024
@killianmuldoon
Copy link
Contributor

/triage accepted

Sounds reasonable to me.

/help

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/triage accepted

Sounds reasonable to me.

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 14, 2024
@killianmuldoon
Copy link
Contributor

A kubeconfig flag

Maybe consider --into-kubeconfig to make the behaviour clear.

@avinesh-tripathi-s1 avinesh-tripathi-s1 removed their assignment Mar 15, 2024
@AvineshTripathi
Copy link
Contributor

Wrong email previously ;)
/assign

@AvineshTripathi
Copy link
Contributor

Hey team,

I did the changes and tested the kubeconfig updation part however I could not test it with actual capi-quickstart guide written here https://cluster-api.sigs.k8s.io/user/quick-start.html.

I have a 3 node kind cluster running
here is the output of describe cluster name

NAME                                                                            READY  SEVERITY  REASON                           SINCE  MESSAGE                                                       
Cluster/capi-quickstart                                                         False  Warning   ScalingUp                        24m    Scaling up control plane to 1 replicas (actual 0)              
├─ClusterInfrastructure - DockerCluster/capi-quickstart-gfcrz                   False  Warning   LoadBalancerProvisioningFailed   24m    0 of 1 completed                                               
├─ControlPlane - KubeadmControlPlane/capi-quickstart-t8fn6                      False  Warning   ScalingUp                        24m    Scaling up control plane to 1 replicas (actual 0)              
└─Workers                                                                                                                                                                                               
  ├─MachineDeployment/capi-quickstart-md-0-8txfm                                False  Warning   WaitingForAvailableMachines      24m    Minimum availability requires 1 replicas, current 0 available  
  │ └─Machine/capi-quickstart-md-0-8txfm-qgxg7-m86sl                            False  Info      WaitingForInfrastructure         24m    0 of 2 completed                                               
  │   ├─BootstrapConfig - KubeadmConfig/capi-quickstart-md-0-9qlcb-l4gmv        False  Info      WaitingForClusterInfrastructure  24m                                                                   
  │   └─MachineInfrastructure - DockerMachine/capi-quickstart-md-0-hm6dk-npxrn                                                                                                                          
  └─MachinePool/capi-quickstart-mp-0-xl89r                                      False  Info      WaitingForClusterInfrastructure  24m                                                                   
    └─MachinePoolInfrastructure - DockerMachinePool/capi-quickstart-mp-0-7kf48

some help would be appreciated. Thanks

@fabriziopandini
Copy link
Member

/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Apr 11, 2024
@dmvolod dmvolod linked a pull request Mar 7, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AvineshTripathi AvineshTripathi

Labels
area/clusterctl Issues or PRs related to clusterctl help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
6 participants
@fabriziopandini @ivelichkovich @k8s-ci-robot @killianmuldoon @AvineshTripathi @avinesh-tripathi-s1