Does the operator support cross-namespace deployments? about mongodb-kubernetes-operator HOT 9 CLOSED

Then env variables it is. I'll start working on it next week.

from mongodb-kubernetes-operator.

This good point. We will add at cluster-wide watch option

from mongodb-kubernetes-operator.

I am willing to implement such a feature. If it is okay for you?

from mongodb-kubernetes-operator.

Hi @thesayyn, if you want to implement this that would be great. Bear in mind a few of things that would need to be done.

1. You would need to sign the CLA
2. Provide a mechanism (perhaps an Env variable) to configure the watch namespace.
3. You would need to provide a new set of cluster roles for the operator (for now, I think the easiest way to do this is to have 2 directories a deploy/namespaced and a deploy/clusterwide. Even if there's a little duplication I think that's fine for now )
4. We would also need to write an E2E test ensuring that the operator is correctly configured to watch resources at a cluster wide level

you can run tests locally with

./scripts/dev/setup_kind_cluster.sh # setup cluster
python ./scripts/dev/e2e.py <test-name> # run the test

Let me know if you would like to do this!

from mongodb-kubernetes-operator.

I'd like to implement it. Also, I think that we should accept cmd options instead of env variables. IMHO env variables aren't as easily discoverable as cmd options.
So instead of passing env variables around, we should accept cmd options since we can validate them and they are easy to track.

What do you think?

from mongodb-kubernetes-operator.

@thesayyn Using cmd options is definitely one of the extensively used patterns we've seen. I think I prefer using envs while we don't have that many configuration options. Interested to hear from @bznein @antonlisovenko @LouisPlisso on this.

from mongodb-kubernetes-operator.

@thesayyn @chatton I also prefer environment variables. They are better integrated with Kubernetes in the sense that they can be set from a ConfigMap or Secret.

from mongodb-kubernetes-operator.

This issue is labeled as stale because it has been open for more than 30 days with no activity. Remove stale label or comment or this will be closed in a few days.

from mongodb-kubernetes-operator.

Marking this issue as closed, as this will be supported with the next release.

from mongodb-kubernetes-operator.