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

Changing Rancher version breaks Private Registry CA #12679

Open
torchiaf opened this issue Nov 26, 2024 · 1 comment
Open

Changing Rancher version breaks Private Registry CA #12679

torchiaf opened this issue Nov 26, 2024 · 1 comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/backport-candidate
Milestone
v2.11.0

Comments

@torchiaf
Copy link
Member

Setup

  • Rancher version: SUSE Rancher 2.9.2, SUSE Rancher 2.8.8
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

Related issue: #10725

When attempting to upgrade from RKE2 1.25 to 1.26 with private registries, the UI changes the private registry CA and then passes invalid yaml to Rancher, causing the upgrade to fail.

Workaround: Check certificates are valid before trying to complete upgrade.

To Reproduce

Create downstream cluster on Rancher 2.7 with private registry
Upgrade to Rancher 2.8
Using Rancher UI, change Kubernetes version on cluster with private registry with private CA

Result

Private Registry CA gets corrupted

Screenshots

image

Additional context
@torchiaf torchiaf added this to the v2.10.1 milestone Nov 26, 2024
@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed area/cluster labels Nov 26, 2024
@gaktive gaktive modified the milestones: v2.10.1, v2.11.0 Nov 26, 2024
@gaktive
Copy link
Member

gaktive commented Nov 26, 2024

/backport v2.10.1

@github-actions github-actions bot mentioned this issue Nov 26, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/backport-candidate
Projects
None yet
Milestone
v2.11.0
Development

No branches or pull requests
2 participants
@gaktive @torchiaf