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 the default namespace in application.properties #10046

Closed
rohit-s8 opened this issue Jun 16, 2020 · 3 comments · Fixed by #10674
Closed

Support for Specifying the default namespace in application.properties #10046

rohit-s8 opened this issue Jun 16, 2020 · 3 comments · Fixed by #10674
Assignees
Labels
Milestone

Comments

@rohit-s8
Copy link

Description
The kubernetes extension for quarkus always generates the resource definitions for the default namespace and there is no way to configure this during build time.
It would be great if we could have a system property like quarkus.kubernetes.namespace and set the namespace of the app without having to edit the generated sources each time

@rohit-s8 rohit-s8 added the kind/enhancement New feature or request label Jun 16, 2020
@gsmet
Copy link
Member

gsmet commented Jun 16, 2020

/cc @iocanel @geoand

@geoand
Copy link
Contributor

geoand commented Jun 16, 2020

To be clear, the generated manifests do not reference the default namespace, they omit it completely which means that when you apply them, they are applied to whatever namespace is used in your current kubectl context

@geoand
Copy link
Contributor

geoand commented Jul 13, 2020

#10674 adds this capability

geoand added a commit that referenced this issue Jul 13, 2020
Add support for specifying the namespace of the generated k8s resources
@gsmet gsmet added this to the 1.7.0 - master milestone Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants