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 namespaceOverride #2534

Closed
robinliubin opened this issue Feb 20, 2024 · 0 comments · Fixed by #2564
Closed

Add namespaceOverride #2534

robinliubin opened this issue Feb 20, 2024 · 0 comments · Fixed by #2564
Labels
argo-workflows enhancement New feature or request

Comments

@robinliubin
Copy link

Is your feature request related to a problem?

in my case, we are creating one umbrella helm chart, Argo-workflow is one sub-chart among 10s other sub-charts.
I want argo goes into argo namespace, while 10s other sub-charts goes into own namespace individually.

when helm install --namespace umbrella:

umbrella chart -> namespace: umbrella
argo-workflow -> namespace: argo
postgres -> namespace: postgres
minio -> namespace: minio
redis -> namespace: redis
(...)
postgres/minio/redis etc. we used the helm chart from bitnami
so we can properly place them, while argo now is the issue.

argo would follow the helm release namespace, if helm install --namespace argocd, argo will be deployed in argocd, however argocd is one sub-chart that we dont want it follow the umbrella helm chart release.

would you please cover this scenario by adding namespaceOverride

Related helm chart

argo-workflows

Describe the solution you'd like

when helm install --namespace umbrella:

umbrella chart -> namespace: umbrella
argo-workflow -> namespace: argo
postgres -> namespace: postgres
minio -> namespace: minio
redis -> namespace: redis
(...)

Describe alternatives you've considered

na

Additional context

#1884

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

Successfully merging a pull request may close this issue.

2 participants