-
Bug
-
Resolution: Done
-
Normal
-
None
-
1.5.0
-
False
-
-
False
-
-
-
Low
Description of the problem:
After successfully deploy Orchestrator Operator and having it deploy rhdh, if the rhdh name or project name are changed in the orchestrator cr, a new project or backstage instance is created, but the original instance is not cleaned up.
How reproducible:
100%
Steps to reproduce:
- Deploy Orchestrator operator M5 and have Orchestrator deploy RHDH
Orchestrator CR rhdh example:
rhdh: devMode: false installOperator: true name: rhdh namespace: rhdh
- Edit orchestrator CR and change the name or namespace to a difference value
Actual results:
A new backstage and/or namespace are created, but the original is not removed.
Expected results:
Seems more logical the original would be removed.
- depends on
-
FLPATH-2239 [m5] Need method to understand which Orchestrator CR params can change day 2
-
- Closed
-