Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Kubernetes namespace selection #245

Open
tliron opened this issue Feb 1, 2023 · 1 comment
Open

Add support for Kubernetes namespace selection #245

tliron opened this issue Feb 1, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@tliron
Copy link

tliron commented Feb 1, 2023

The UI currently tracks related CRs (e.g. Repository) in the "default" namespace only.

Ideally there would be a dropdown to select an individual namespace or all namespaces.

@tliron tliron added the enhancement New feature or request label Feb 1, 2023
@ChristopherFry
Copy link
Collaborator

The UI currently tracks related CRs (e.g. Repository) in the "default" namespace only.

Confirming the Config as Data UI does support looking for resources in a namespace other than "default" today. The UI looks for resources as defined by the resourcesNamespace value in the app-config.yaml file as defined by the Configuration as Data Backend Plugin.

This value can be updated by either updating the value directly in the app-config.yaml, extending the app configuration with another configuration file overriding any values as needed (this is the pattern that Nephio follows), or setting the APP_CONFIG_configAsData_resourcesNamespace environment variable using environment variable overrides.

Ideally there would be a dropdown to select an individual namespace or all namespaces.

I can look into adding this. Although the UI does support looking for resources in another namespace, the namespace does need to be defined upfront.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants