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

GKE: Restrict editing extra zones for Regional clusters #13145

Open
cpinjani opened this issue Jan 17, 2025 · 1 comment
Open

GKE: Restrict editing extra zones for Regional clusters #13145

cpinjani opened this issue Jan 17, 2025 · 1 comment
Labels
area/clusterprovisioningv2 area/gke kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression team/highlander Highlander

Comments

@cpinjani
Copy link

Setup
Rancher - v2.10-969f790e32c71d592e23b9284c8048fd963ac40d-head
Dashboard - release-2.10 8a339a5

Describe the bug
While editing regional GKE cluster, extra zones fields are editable. GKE UI does not allow it, so we should disable it as well. Its only allowed to be edited for zonal clusters.
See also: #12260

To Reproduce

  • Provision regional GKE cluster from Rancher UI
  • Edit cluster and add extra zones.

Screenshots
v2.10:

Image

v2.8 (as expected):

Image

GKE:

Image
@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 Jan 17, 2025
@IsaSih IsaSih mentioned this issue Jan 29, 2025
Open
@IsaSih
Copy link
Contributor

IsaSih commented Jan 29, 2025

Created QA automation task to expand GKE test coverage rancher/qa-tasks#1662

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/clusterprovisioningv2 area/gke kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression team/highlander Highlander
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@IsaSih @cpinjani @eva-vashkevich