-
Bug
-
Resolution: Done
-
Minor
-
1.1, 1.2
-
1
-
False
-
-
False
-
-
Removed Functionality
-
Done
-
-
-
RHDH Core Team 3259, RHDH Core Team 3260
Description of problem:
Trying to install 2 independent Backstage instances using Helm in the same namespace.
The second install failed with the error below:
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "dynamic-plugins" in namespace "my-ns" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "my-backstage-2": current value is "my-backstage-1"
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
git clone https://github.com/redhat-developer/rhdh-chart.git
helm install my-backstage-1 charts/backstage
helm install my-backstage-2 charts/backstage
You can get a similar error when using the OCP console - see the screenshot attached.
Actual results:
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "dynamic-plugins" in namespace "my-ns" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "my-backstage-2": current value is "my-backstage-1"
Expected results:
Both installs should pass. I noticed that the name of the 'dynamic-plugins' ConfigMap is currently hardcoded in the Helm Chart: https://github.com/redhat-developer/rhdh-chart/blob/main/charts/backstage/templates/dynamic-plugins-configmap.yaml#L4
Helm Chart authors usually include the release name in all the resources created by the Chart, so that multiple releases of the same Chart can be done in the same namespace.
This can be common as a use case, for example, when the user only has access to a single namespace (like on Dev Sandbox) and wants to expose different versions of RHDH.
Note:
This does not affect the Operator, as it includes the Custom Resource name in the resources it creates and manages. So it is possible to create 2 different Operator-backed instances of RHDH in the same namespace.
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Additional info (Such as Logs, Screenshots, etc):
- links to