UI is deleting the default port numbers of ingress controllers

[IsaSih]

Setup

• Rancher version:

Rancher v2.14.1-alpha2
Dashboard v2.14.1-alpha1
Rancher CLI v2.14.0

Describe the bug
When creating a RKE2/k3s cluster after switching from K3s to RKE2, the default values of the Ingress Controller ports for Traefik and Ingress-NGINX are not displayed in the UI. This was observed for multiple cloud providers

To Reproduce

1- Navigate to Cluster Management > Clusters > Create.

2- create a cluster using RKE2/K3s

3- Scroll down to the Basics tab under Cluster Configuration.

4- Observe the Ingress section (Traefik is selected by default) and port default values.

5 - Click on Ingress-NGINX.

6- Observe the port default values.

7- Switch the kubernetes version to K3s

8- Then, switch back to a RKE2 kubernetes version

Result
The default values of the Ingress Controller ports for Traefik and Ingress-NGINX are not displayed in the UI.

Expected Result
The default values of the Ingress Controller ports for Traefik and Ingress-NGINX must be displayed in the UI, regardless of the user's previous selection of kubernetes version.

Screenshots

Screen.Recording.2026-04-15.at.12.23.58.AM.mov

[github-actions]

🎯 Agentic Issue Triage

Summary: When creating a RKE2/k3s cluster, switching from K3s to RKE2 (or vice versa) causes the default port values for Traefik and Ingress-NGINX ingress controllers to be cleared from the UI. This affects multiple cloud providers and occurs in the Basics tab → Ingress section during cluster creation.

🔍 Root Cause Analysis

The issue lies in shell/edit/provisioning.cattle.io.cluster/tabs/Ingress.vue.

The traefikMerged and nginxMerged reactive refs are initialized once at component creation:

const traefikMerged = ref(initYamlEditor(traefikChart));
const nginxMerged = ref(initYamlEditor(nginxChart));

The initYamlEditor function pulls default values from versionInfo[chart]:

function initYamlEditor(chart: string) {
  const defaultChartValue = versionInfo[chart];
  return mergeWithReplace(defaultChartValue?.values, userChartValues[chart]);
}

When the user switches from K3s to RKE2, the versionInfo prop and traefikChart/nginxChart props (computed in Basics.vue via chartVersionKey()) change — but traefikMerged and nginxMerged are not re-initialized. They either retain stale values or render empty/undefined because the chart version key has changed and the new key isn't found.

The port values (ports.web.hostPort, ports.websecure.hostPort, controller.hostPort.ports.http, etc.) rely on versionInfo defaults being present in traefikMerged/nginxMerged, so when these aren't re-initialized, the port fields display nothing.

🔧 Suggested Fix

Add a watch on the versionInfo prop (or traefikChart/nginxChart) in Ingress.vue to re-initialize the merged values when they change. Be careful to preserve any user-entered values when re-merging:

watch(() => [traefikChart, nginxChart, versionInfo], () => {
  traefikMerged.value = initYamlEditor(traefikChart);
  nginxMerged.value = initYamlEditor(nginxChart);
}, { deep: true });

Or use watchEffect to automatically track dependencies.

Important: The re-initialization should merge in any existing user values to avoid overwriting intentional user changes.

🔁 Reproduction Steps

1. Navigate to Cluster Management > Clusters > Create
2. Select RKE2/K3s provider and configure a cluster
3. Go to Basics tab > Cluster Configuration > Ingress section
4. Observe the default port values for Traefik (HTTP/HTTPS)
5. Switch ingress to Ingress-NGINX and observe default port values
6. Change the Kubernetes version to K3s
7. Switch the Kubernetes version back to RKE2
8. Observe that the Ingress port default values are now missing/empty

🧪 Testing Guidance

• Unit test in shell/edit/provisioning.cattle.io.cluster/__tests__/Ingress.test.ts:
  • Add a test that changes the versionInfo or chart props and asserts that port default values are re-populated
• Manual test on all supported cloud providers (the issue reporter notes it affects multiple providers)
• Test switching K3s → RKE2 and RKE2 → K3s to ensure bidirectionality

📁 Relevant Files

• shell/edit/provisioning.cattle.io.cluster/tabs/Ingress.vue — Main file to fix (traefikMerged/nginxMerged initialization)
• shell/edit/provisioning.cattle.io.cluster/tabs/Basics.vue — Parent component that computes traefikChart, nginxChart, versionInfo and passes them as props
• shell/edit/provisioning.cattle.io.cluster/ingress/IngressConfiguration.vue — Renders the port fields
• shell/edit/provisioning.cattle.io.cluster/shared.ts — Constants for chart names
• shell/edit/provisioning.cattle.io.cluster/__tests__/Ingress.test.ts — Existing tests to extend

📋 Sub-tasks Checklist

• Add a watch in Ingress.vue to re-initialize traefikMerged and nginxMerged when versionInfo, traefikChart, or nginxChart props change
• Ensure the watch correctly merges new defaults with existing user-entered values
• Add/update unit tests in Ingress.test.ts to cover the prop-change scenario
• Manually verify fix on at least 2 cloud providers
• Verify bidirectional switching (K3s ↔ RKE2) restores defaults correctly

---

Triaged by bot/issue-triage

Generated by Agentic Triage for issue #17267 · ◷

[github-actions]

🤖 Issue grooming analysis

This issue is well-groomed and ready for triage. Here's the analysis against the checklist:

✅ Clear Problem Statement
The title and description clearly explain the bug: when switching Kubernetes distributions (RKE2 ↔ K3s) during cluster creation, default Ingress Controller port values for Traefik and Ingress-NGINX disappear from the UI. Rancher and Dashboard versions are specified.

✅ Acceptance Criteria
Clearly defined: the default port values for Traefik and Ingress-NGINX must be displayed in the UI regardless of the user's previous Kubernetes version selection.

✅ Technical Details
The affected area is pinpointed (Cluster Management → Create → Basics tab → Ingress section), versions are listed (Rancher v2.14.1-alpha2, Dashboard v2.14.1-alpha1), and a screen recording demonstrating the issue is attached.

✅ Reproducibility
Seven numbered reproduction steps are provided, along with clear expected vs. actual results and preconditions (starting on RKE2/K3s creation with Traefik as default).

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

Generated by Daily Issue Grooming · ◷