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

[Backport v2.6] [BUG] Updating internal server URL, internal server CA, and user token invalidates CAPI kubeconfig secret #40742

Closed
rancherbot opened this issue Mar 1, 2023 · 2 comments
Closed

[Backport v2.6] [BUG] Updating internal server URL, internal server CA, and user token invalidates CAPI kubeconfig secret #40742

rancherbot opened this issue Mar 1, 2023 · 2 comments
Assignees
@Oats87 @nickwsuse
Labels
area/capr/rke2 RKE2 Provisioning issues involving CAPR area/provisioning-v2 Provisioning issues that are specific to the provisioningv2 generating framework kind/bug Issues that are defects reported by users or that we know have reached a real release team/area3 team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Milestone
v2.6.11

Comments

@rancherbot
Copy link
Collaborator

This is a backport issue for #40741, automatically created via rancherbot by @Oats87

Original issue description:

Rancher Server Setup

  • Rancher version: v2.7

Describe the bug
When updating the internal server URL, internal server CA, and/or Rancher token for a given v2prov cluster, the CAPI kubeconfig secret becomes outdated because Rancher relies on the old version of the secret.

To Reproduce
Set up a Rancher installation
Create a v2prov cluster and wait for it to provision
Update the internal server URL, internal server CA, and/or delete/modify the user token that corresponds with the kubeconfig secret of the cluster

Result
Observe the kubeconfig secret is not updated

Expected Result
The kubeconfig secret should be updated

Screenshots

Additional context
@rancherbot rancherbot added area/clusterprovisioningv2 area/provisioning-v2 Provisioning issues that are specific to the provisioningv2 generating framework area/capr/rke2 RKE2 Provisioning issues involving CAPR kind/bug Issues that are defects reported by users or that we know have reached a real release labels Mar 1, 2023
@rancherbot rancherbot added this to the v2.6.11 milestone Mar 1, 2023
@Oats87 Oats87 mentioned this issue Mar 1, 2023
Merged
@Sahota1225 Sahota1225 added team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support [zube]: To Test labels Mar 2, 2023
@snasovich snasovich mentioned this issue Mar 2, 2023
Closed
@ronhorton
Copy link

ronhorton commented Mar 2, 2023 •
edited

@nickwsuse this should be validated with @Oats87 when testing round 2 of the fix for #40300

@nickwsuse
Copy link
Contributor

Verified on v2.6-head ID: 5e33172

This did indeed fix the RKE2 migration issue (#40300), and I did some additional testing outside of that use case.

I deleted the Rancher pods to trigger this change and saw a message in the logs stating the kubeconfig secret for the cluster is being deleted.

@zube zube bot removed the [zube]: Done label Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Oats87 Oats87

@nickwsuse nickwsuse

Labels
area/capr/rke2 RKE2 Provisioning issues involving CAPR area/provisioning-v2 Provisioning issues that are specific to the provisioningv2 generating framework kind/bug Issues that are defects reported by users or that we know have reached a real release team/area3 team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Projects
None yet
Milestone
v2.6.11
Development

No branches or pull requests
5 participants
@Oats87 @rancherbot @ronhorton @Sahota1225 @nickwsuse