Installing ArangoDB in different namespaces

[saruman67]

Error installing ArangoDB if there is already an ArangoDB instance installed in a different namespace in the k8s cluster:

Error: INSTALLATION FAILED: Unable to continue with install: CustomResourceDefinition "arangolocalstorages.storage.arangodb.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "prod": current value is "dev"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "namespace-prod": current value is "namespace-dev"

It is also impossible to install operators in different namespaces, because setting the flag --set "operator.scope=namespaced" results in an error:

> helm install dev kube-arangodb-1.2.42.tgz -n dev --set "operator.features.storage=true" --set "operator.scope=namespaced"

Error: INSTALLATION FAILED: execution error at (kube-arangodb/templates/deployment.yaml:6:3): Storage Operator not supported in namespaced scope!

I see a similar problem here https://github.com/arangodb/kube-arangodb/pull/735 and here https://github.com/arangodb/kube-arangodb/pull/551

[ajanikow]

Hello!

The issue is that the Storage Operator is centralized, while other Operators are namespaces.

We will provide instructions on dealing with that + additional manifests to allow you to work with it.

Best Regards, Adam.