Skip to content

Add dropdown for namespace selection on App Wizard#62

Merged
rewenila merged 4 commits intoSUSE:mainfrom
rewenila:feat/add-namesoace-dropdown
Feb 26, 2026
Merged

Add dropdown for namespace selection on App Wizard#62
rewenila merged 4 commits intoSUSE:mainfrom
rewenila:feat/add-namesoace-dropdown

Conversation

@rewenila
Copy link
Contributor

This PR introduces improvements to the App Wizard (both Install and Manage pages), focusing on namespace selection and user experience.

Key changes:

  • Improved Namespace Input UI: Refactored the namespace input in the basic info step. It now uses a "creatable select" component, allowing users to choose an existing namespace or type a new one.
  • Namespace Filtering: Implemented a prefix-based filter to automatically hide internal Rancher system namespaces (e.g., c-xxxxxx, p-xxxxxx, kube-system, cattle-system) from the dropdown, providing users with a cleaner and more relevant list of available namespaces.
  • Preserved Default Namespace: Maintained the existing behavior of suggesting <app-name>-system as the default namespace in the Install page, ensuring it remains available as an option and is pre-selected after fetching and filtering other namespaces. For the Manage page, the pre-selected option is the namespace where the app is currently installed.
Screenshot from 2026-02-20 05-32-19

- Implemented prefix-based filtering to hide system namespaces (p-, c-, kube-, etc.).
- Refactored the UI to use a single "creatable" dropdown for a cleaner user experience.
- Ensured `<app-name>-system` is always suggested as the default.
Previous changes made the `<app-name>-system` namespace the option selected by default in the namespace dropdown during app installation and management. Now, the installed namespace is the selected option during app management.
Copy link
Contributor

@leooamaral leooamaral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Also tried to install ollama in a custom namespace called test in my local cluster and didn't work. This was a not pre-created ns, so the extension does not create ns?

Copy link
Contributor

@leooamaral leooamaral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

Also tried to install ollama in a custom namespace called test in downstream cluster and didn't work. This was a not pre-created ns, so the extension does not create ns in downstream also?

@rewenila
Copy link
Contributor Author

It should be able to create the namespace, I'll try to reproduce the issue.

When creating a new namespace in the App Wizard using the "creatable" dropdown, the component was incorrectly passing an object (e.g., `{ label: 'new-ns' }`) to the form model instead of a simple string. It now checks if the incoming value is an object and extracts the string name from its `label` property, ensuring a valid string is always passed to the backend.
Copy link
Contributor

@leooamaral leooamaral left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes validated:

  • I could install ollama in pre-created namespace
  • I could install ollama in non-existent namespace
  • I could install ollama in ollama-system namespace

Also worked installing the apps in the current rancher server and downstream servers

@rewenila rewenila merged commit b22b851 into SUSE:main Feb 26, 2026
4 checks passed
@rewenila rewenila deleted the feat/add-namesoace-dropdown branch February 26, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants