GKE provisioning is missing private registry configuration

[mantis-toboggan-md]

Setup

• Rancher version: v2.15-d0c047bbc6d202e953d7557b82cbb354367db6ae-head
• Rancher UI Extensions: n/a
• Browser type & version: ff

Describe the bug
The GKE provisioning form is missing the 'Registries' section: currently, the section is shown only when importing GKE clusters.

To Reproduce
Navigate to the cluster management cluster list view and click 'create'
Select GKE
Enter credentials

Result
No registries section

Expected Result
A 'Registries' section should be rendered, containing the same configuration options as the Registries section in AKS and EKS provisioning forms

Screenshots

Additional context
Running the ui locally I see the following error in the console

TypeError: can't access property "privateRegistryURL", _ctx.normanCluster.importedConfig is undefined

[github-actions]

🎯 Agentic Issue Triage

Summary: The GKE cluster provisioning form is missing the Registries (private registry) section that already exists in AKS and EKS provisioning forms. The section renders correctly during import but is absent during provisioning.

🔍 Root Cause Analysis

The bug is in pkg/gke/components/CruGKE.vue.

GKE's defaultCluster (used when creating a new provisioning cluster) does not include importedConfig:

// pkg/gke/components/CruGKE.vue ~L124
const defaultCluster = {
  dockerRootDir:           '/var/lib/docker',
  enableClusterAlerting:   false,
  enableClusterMonitoring: false,
  enableNetworkPolicy:     false,
  labels:                  {},
  annotations:             {},
  windowsPreferedCluster:  false,
  // ❌ importedConfig is missing here
};

By contrast, AKS's defaultCluster does include it:

// pkg/aks/components/CruAks.vue ~L87
const defaultCluster = {
  ...
  importedConfig: {},  // ✅ present
};

In fetch(), when creating a new cluster (non-import path), normanCluster is set from defaultCluster — so normanCluster.importedConfig becomes undefined. The safeguard at line 207 only runs when this.value?.id exists (i.e., editing an existing cluster), so a brand-new provisioning cluster never gets importedConfig initialized.

The template then attempts normanCluster.importedConfig.privateRegistryURL which throws a TypeError on undefined, preventing the Registries accordion from rendering.

🛠 Suggested Fix

Option A (preferred — matches AKS pattern): Add importedConfig: {} to defaultCluster in CruGKE.vue:

 const defaultCluster = {
   dockerRootDir:           '/var/lib/docker',
   enableClusterAlerting:   false,
   enableClusterMonitoring: false,
   enableNetworkPolicy:     false,
   labels:                  {},
   annotations:             {},
   windowsPreferedCluster:  false,
+  importedConfig:          {},
 };

Option B (broader guard): Remove the this.value?.id && condition from the safeguard at line 207 so it also fires for new clusters:

-if (this.value?.id && !this.normanCluster.importedConfig) {
+if (!this.normanCluster.importedConfig) {
   this.normanCluster.importedConfig = {};
 }

Option A is preferred for consistency with AKS.

Note: The :context="PRIVATE_REGISTRY_CONTEXT.IMPORTING" prop on <PrivateRegistry> is consistent with AKS and EKS behaviour — no change needed there.

🔁 Reproduction Steps

1. Navigate to Cluster Management → Clusters and click Create.
2. Select Google GKE.
3. Enter valid GCP credentials and project.
4. Scroll through the form — observe that no Registries accordion is present.
5. Compare with AKS or EKS provisioning forms — both show a Registries section.
6. For import path (working): repeat the above but select Import mode — the Registries section is visible.

🧪 Testing Checklist

• Registries accordion is rendered in the GKE provisioning form (create flow)
• Registries accordion is still rendered in the GKE import flow
• Setting a private registry URL during provisioning is persisted to the cluster object
• Clearing the URL removes it from normanCluster.importedConfig
• No JS console errors when loading the GKE provisioning form
• Unit tests updated in pkg/gke/__tests__/ to cover the registry section visibility

📚 Relevant Files

File	Relevance
pkg/gke/components/CruGKE.vue	Main fix location (defaultCluster definition ~L124)
pkg/aks/components/CruAks.vue	Reference implementation (working)
pkg/eks/components/Config.vue	Reference implementation (working)
shell/components/form/PrivateRegistry.vue	The shared registry component
shell/components/form/PrivateRegistry.constants.ts	Context constants (IMPORTING, PROVISIONING)

Generated by Agentic Triage for issue #18211 · ● 925.6K · ◷

[github-actions]

🤖 Issue grooming analysis

This issue meets all four primary grooming criteria and is ready for triage.

✅ Clear Problem Statement
The GKE cluster provisioning form (Create flow) is missing the 'Registries' section that exists in the AKS and EKS provisioning forms and in the GKE import flow. The missing section prevents users from configuring private registries during GKE cluster creation.

✅ Acceptance Criteria
Expected Result defines the criterion: a 'Registries' section should be rendered in the GKE create form, containing the same configuration options as in the AKS and EKS provisioning forms.

✅ Technical Details
Specific Rancher version (v2.15-d0c047bbc6d202e953d7557b82cbb354367db6ae-head), a precise JS console error (TypeError: can't access property "privateRegistryURL", _ctx.normanCluster.importedConfig is undefined) pointing directly to the affected code path, and a clear description of where the section appears (import flow) vs. where it is missing (create flow).

✅ Reproducibility
Numbered steps to reproduce: navigate to Cluster Management → Create → GKE → enter credentials → observe no Registries section. Expected vs. actual behavior is explicitly stated.

i️ Dependencies
AKS and EKS provisioning forms are referenced as the implementation model for the missing section.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ● 1.1M · ◷