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

The registries advanced section should always be displayed in RKE2/K3s Custom Cluster page #11134

Open
ly5156 opened this issue May 29, 2024 · 0 comments · May be fixed by #11135
Open

The registries advanced section should always be displayed in RKE2/K3s Custom Cluster page #11134

ly5156 opened this issue May 29, 2024 · 0 comments · May be fixed by #11135
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@ly5156
Copy link
Contributor

ly5156 commented May 29, 2024 •
edited
Loading

Setup

  • Rancher version: v2.7.2 - v2.8.4

Describe the bug

if the Enable cluster scoped container registry for Rancher system container images is unchecked，the registries advanced section is hidden, but system-default-registry and registries.configs registries.mirrors are not inclusive.

To Reproduce

  1. Go to the Create RKE2/K3s Custom Cluster page
  2. In the Cluster Configuration section, click the Registries tab
  3. Unchecked the Enable cluster scoped container registry for Rancher system container images

Result
The registries advanced section is hidden.

Expected Result

The registries advanced section should always be displayed

Screenshots

test
Additional context
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label May 29, 2024
@ly5156 ly5156 linked a pull request May 29, 2024 that will close this issue
Open
7 tasks
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(registries): always show advanced section ly5156/dashboard
1 participant
@ly5156