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

Support for specifying Application Installation namespace #6858

Open
ahmedwaleedmalik opened this issue Sep 19, 2024 · 1 comment
Open

Support for specifying Application Installation namespace #6858

ahmedwaleedmalik opened this issue Sep 19, 2024 · 1 comment
Labels
customer-request kind/feature Categorizes issue or PR as related to a new feature. sig/ui Denotes a PR or issue as being assigned to SIG UI.
Milestone

Comments

@ahmedwaleedmalik
Copy link
Member

What would you like to be added? / User Story:
As a KKP user, I'd like the ability to explicitly specify the namespace in which my ApplicationInstallation resource will be created. Right now, we are only allowed to specify a single namespace that then is used for both the ApplicationInstallation and application.spec.namespace.name which determines where the resources for application will be created/installed.

This makes it a bit ambiguous as it should be possible to create all the ApplicationInstallations in a single namespace irrespective of where the resources are created since they have a separate dedicated field.

@ahmedwaleedmalik ahmedwaleedmalik added kind/feature Categorizes issue or PR as related to a new feature. sig/ui Denotes a PR or issue as being assigned to SIG UI. labels Sep 19, 2024
@ahmedwaleedmalik
Copy link
Member Author

With this feature, we should also add a field somewhere; seed, datacenter, KubermaticSettings, or KubermaticConfiguration that can store the default namespace for ApplicationInstallations. Some users might want to let's say have a dedicated namespace apps where they'd like to place their ApplicationInstallations.

@csengerszabo csengerszabo added this to the KKP 2.27 milestone Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-request kind/feature Categorizes issue or PR as related to a new feature. sig/ui Denotes a PR or issue as being assigned to SIG UI.
Projects
None yet
Development

No branches or pull requests

2 participants