Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Trying to test a "hybrid" deployment structure with Zarf and what we already designed/use for bootstrapping our cluster.
Workflow:
Ansible deploys rke2
Zarf adopts the cluster and we deploy a zarf package that really only contains images that our apps need. Solely using Zarf for its docker image repo.
Use our homegrown helmfile solution to bootstrap the cluster and deploy argocd, which then deploys our apps.
The issue I have found is that we have to "pre-define" all namespaces that would end up being created for applications deployed to have secrets deployed to those namespaces for the internal git and docker image repos. I would have expected that since any new pods created after adoption have the secret reference applied by the mutating webhook, that any new namespaces created after adoption would also have the secret applied to them, but this is not the case.
Describe the solution you'd like
Ultimately I would like to see when a namespace is created, after cluster adoption, that those secrets would be replicated/deployed to that new namespace unless I applied the "ignore flag" label on the namespace.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Trying to test a "hybrid" deployment structure with Zarf and what we already designed/use for bootstrapping our cluster.
Workflow:
The issue I have found is that we have to "pre-define" all namespaces that would end up being created for applications deployed to have secrets deployed to those namespaces for the internal git and docker image repos. I would have expected that since any new pods created after adoption have the secret reference applied by the mutating webhook, that any new namespaces created after adoption would also have the secret applied to them, but this is not the case.
Describe the solution you'd like
Ultimately I would like to see when a namespace is created, after cluster adoption, that those secrets would be replicated/deployed to that new namespace unless I applied the "ignore flag" label on the namespace.