Operator on different namespace #649
Comments
|
Hello! We support currently I will update this issue once PR will be ready. Best Regards, |
|
How's the progress on this issue? We are really looking forward to use arango operation on cluster mode. |
|
Looking into this also. Need multiple Arango instances in distinct namespaces, but we don't want an operator per namespace. |
|
I need support for this as well. |
|
I'm looking forward to using this feature once it gets included in a release. Any updates on the timeframe? |
|
Hey, did this feature ever get included? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We process resources isolation betweens namespaces, and use differents namespaces for services.
What's the best practice ? I've tried to have an
arangodbnamespace with operators & crd, and It seems impossible to have the operator andarangodeployments.database.arangodb.comon different namespaces.I guess that today I will have to deploy one operator instance per namespace, but some other k8s softwares provide an selector to tell which namespace to use to talk with operator.
If it's expected to have shared operators between many namespaces, this is a feature request (or a RTFM answer, but, I've searched :/)
If it's expected to have one operator deployment per namespace, maybe this best practice should be added to docs
If it's expected to have one operator deployment per namespace, maybe a database creation script can be added to helm chart ?
Best regards,
Gaël
The text was updated successfully, but these errors were encountered: