Rancher 2.12.2 Ingress form editor cannot properly edit backend.service.port.name

[orgC]

Setup

• Rancher version: 2.12.2
• Rancher UI Extensions:
• Browser type & version: firefox

Describe the bug
We found an issue in Rancher UI when editing an existing Ingress resource.

The Ingress itself is valid and can be edited/saved successfully in YAML mode.
However, in the Rancher form-based editor, the backend Service port is not correctly rendered when the Ingress uses:

spec.rules[].http.paths[].backend.service.port.name

As a result, the port field appears empty in the form UI, and the Save button is disabled or the form cannot be saved normally.

This looks like a UI/form rendering issue rather than a Kubernetes API issue.

To Reproduce

1. Create or apply an Ingress resource with backend.service.port.name, for example:
   port:
   name: http

2. Open the Ingress in Rancher UI.

3. Switch to the form-based edit page.

4. Observe that the backend service port field is not properly populated/rendered.

5. Try to save the form.

Result

• The backend service port field is blank or not correctly populated in the form editor.
• The form cannot be saved correctly, or the Save button is disabled.
• YAML mode can still save the same resource successfully.

Expected Result
Rancher UI should correctly render and allow editing of Ingress resources using:

backend.service.port.name

The form editor should treat service port name and service port number as equally valid backend definitions.

Screenshots

Additional context

[github-actions]

🤖 Issue grooming analysis

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

✅ Clear Problem Statement
The title clearly summarizes the bug. The description explains that in Rancher 2.12.2's UI form editor, Ingress resources using backend.service.port.name render with a blank port field, preventing the form from being saved. The YAML editor works correctly, isolating this as a UI rendering issue.

✅ Acceptance Criteria
The expected result is clearly stated: the form editor should correctly render and allow editing of backend.service.port.name, treating port name and port number as equally valid backend definitions. This is user-facing and verifiable.

✅ Technical Details
The specific Kubernetes field path is identified (spec.rules[].http.paths[].backend.service.port.name), the affected component is identified (Ingress form editor), and the environment is specified (Rancher 2.12.2, Firefox).

✅ Reproducibility
Five numbered reproduction steps are provided, along with clear expected vs. actual behavior and stated preconditions (Rancher 2.12.2, an Ingress using port.name).

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

Generated by Daily Issue Grooming · ◷