disposab1e/sealed-secrets-operator-helm

Error with multiple sealed secrets instances

Opened this issue · 3 comments

chetan-rns commented

When the operator from OperatorHub is installed in multiple namespaces and CR instances are created in their respective namespaces. The instances fail with the following error

failed to install release: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: namespace: , name: sealedsecrets.bitnami.com, existing_kind: apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition, new_kind: apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition

Steps to reproduce:

  1. Create a namespace foo. Install the operator in namespace foo and create the CR in foo
  2. Create a new namespace bar. Install the operator in namespace bar and create the CR in bar

Operator Version: 0.0.2
Environment: OpenShift 4.6

disposab1e commented

Thx for reporting... do you think it's an usual usecase to install the operator in different namespaces or better install once and watch on all namespaces? Not sure an helm operator can do this....

disposab1e commented

@chetan-rns Did you try with crd.create=false for your second instance?

chetan-rns commented

Thanks, @disposab1e. Will try with crd.create=false