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

Make namespace creation as optional #292

Open
sumeet-zuora opened this issue Feb 20, 2024 · 5 comments
Open

Make namespace creation as optional #292

sumeet-zuora opened this issue Feb 20, 2024 · 5 comments

Comments

@sumeet-zuora
Copy link

Can we make the creation of namespace as optional at https://github.com/percona/percona-helm-charts/blob/main/charts/psmdb-operator/templates/namespace.yaml as we might already have namespace created from different automation

@spron-in
Copy link
Collaborator

Hello @sumeet-zuora ,

yeah, we have it in our plans and it might be delivered under https://perconadev.atlassian.net/browse/K8SPSMDB-930

@sumeet-zuora
Copy link
Author

Can this be also added to pxc, pg and ps operator seems all have same issue

@tplavcic
Copy link
Member

@sumeet-zuora From what I see pxc is affected and I will create a PR for it, ps and pg don't seem to be affected since they don't create namespaces (but correct me if I'm wrong and don't see something).

@sumeet-zuora
Copy link
Author

In ps the watch namespace is only for where it is deployed, pg watch namespace have proper variable.

Role and rolebindings have mentioned the watch namespace, but values.yaml don't have it defined.

In both, it is expected as string or single namespace. Where as I think in psmdb it is multiple namespaces separated by comma.

@abh
Copy link

abh commented Oct 6, 2024

in ps-operator it'd be nice if it'd be possible to set the WATCH_NAMESPACE variable through the chart, instead of having it fixed to the namespace of the operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants