Creating an unknown feature flag breaks the Global Settings > Feature Flags

[valaparthvi]

Setup

• Rancher version: head/2.14 (v2.14-985c2d143c019e7812431b3e3adb2effe7d92f7c-head)
• Rancher UI Extensions: release-2.14 ae2d748
• Browser type & version: Chrome

Describe the bug

If an unknown feature flag is created via Import YAML or kubectl, Global Settings > Feature Flags page breaks and is unable to show existing Feature Flags.

To Reproduce

1. Create an unknown feature flag via Import YAML or kubectl.

apiVersion: management.cattle.io/v3
kind: Feature
metadata:
  name: unknown-flag
spec:
  value: true

2. Go to Global Settings > Feature Flags. The page will be broken, it will not display any features.
3. Delete the feature and go back to Global Settings > Feature Flags. The page should display features again.

Result
If an unknown feature is added, the feature flag page breaks, it is completely blank. But it resumes working once the feature is deleted.

Expected Result

The page should not break. Perhaps it can show error when an unknown feature is encountered.

Screenshots

Screencast.from.2026-04-13.15-21-46.webm

Additional context

[github-actions]

🤖 Issue grooming questions

The problem description, reproduction steps, and expected vs. actual behavior are clear and well-structured — thank you for including the version info and the video recording. A couple of things are still needed before this can be fully triaged:

1. Acceptance criteria: What specific criteria should be met for this bug to be considered fixed? For example:

   • When an unknown feature flag exists, the Feature Flags page still loads and displays all known feature flags without any breakage
   • The page handles unknown feature flags gracefully (e.g., shows an inline warning or skips the unknown entry rather than crashing the entire page view)

2. Error details: When the page breaks, are there any browser console errors (JavaScript errors, failed network requests)? A screenshot or copy of the console output would help pinpoint the component throwing the error.

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ◷

[nwmac]

Note, you need the page size to be 50, to ensure you are loading all of them, including the broken one

[nwmac]

Feature flags don't have a public API, so if you create them this way via Steve, they don't form correctly, so are missing a number of expected fields, such as status.

We can update the UI to cope with this.

[izaac]

Moving to done, the test coverage is enough to validate the fix.