[FEAT] - Remove kubeconfig key from KubeConfig Secrets

[IvoGoman]

Priority

(Medium) I'm annoyed but I'll live

User Story

No response

Description

When onboarding a Cluster a Secret with the kubeconfig is created. Once the cluster bootstrap is done, the Secret will have the greenhousekubeconfig key containing the KubeConfig with the token for the ServiceAccount used to access the cluster.

Greenhouse will always use the KubeConfig with the ServiceAccount token after the cluster was successfully bootstrapped. In order to avoid having a potentially personal admin KubeConfig in the secret, the key should be removed.
When re onboarding a Cluster via greenhousectl both keys in the secret are overwritten with a user provided kubeconfig. This KubeConfig is then reconciled by the Cluster controller.

Acceptance Criteria

• After successfully bootstrapping the Cluster the kubeconfig key is removed
• greenhousectl updates the greenhousekubeconfig key when re onboarding a Cluster

Reference Issues

No response