clusterctl support for downloading kubeconfig as context within existing kubeconfig

ivelichkovich commented 8 months ago

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

killianmuldoon commented 8 months ago

/triage accepted

Sounds reasonable to me.

/help

k8s-ci-robot commented 8 months ago

@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](https://github.com/kubernetes-sigs/cluster-api/issues/10133): >/triage accepted > >Sounds reasonable to me. > >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

killianmuldoon commented 8 months ago

A kubeconfig flag

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

AvineshTripathi commented 7 months ago

Wrong email previously ;) /assign

AvineshTripathi commented 6 months ago

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 commented 6 months ago

/priority backlog

kubernetes-sigs / cluster-api