-
Notifications
You must be signed in to change notification settings - Fork 44
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
[argoconfig] ability to create namespaces #115
Comments
Namespace autocreation is in Argo CD's scope and will be available with >1.7.8 (argoproj/argo-cd#3976) We will need to configure it in
I'm not sure if we can set some global default syncOptions to enable this everywhere if we decide to go down that route. Given that we are considering to use namespaces as a security boundary i'm not all that sure if I'd not rather manage namespaces somewhere else (ie. together with rbac and other security things). |
How would we manage setting labels on namespaces then for being able of using rbac-manager correctly? Isn't this then ending up with having a own |
Also, how are we handling AppProject creation when bootstrapping a new cluster? Is this done manually? |
Initial creation of the first AppProject might need to be manual (like deploying ArgoCD with the Helm chart) and then we can probably use the raw YAML approach we're using for |
Is your feature request related to a problem? Please describe.
There is no way to manage namespaces as of now.
Describe the solution you'd like
I thought about having argoconfig create namespaces according to the applications'
destination.namespace
Describe alternatives you've considered
creating a standalone chart for namespace creation
Affected chart
infra-apps
Additional context
A.e. the application
velero
ininfra-apps
sets it'sdestination.namespace
toinfra-velero
.Argoconfig
could make sure the namespace is also created.The text was updated successfully, but these errors were encountered: