-
Bug
-
Resolution: Done
-
Normal
-
None
-
1.5.0
-
False
-
-
False
-
-
Description of the problem:
When deploying Orchestrator with serverless and serverlessOperator disabled, if the workflow namespace exists, it would be repeatedly removed by the operator.
This seems like an issue because my understanding for disabling serverless/serverlessOperator would be that the user already manages and has those instances installed. If they are using the workflow namespace, then it should not be removed.
How reproducible:
100%
Steps to reproduce:
1. Deploy Orchestrator via CR with serverless and serverlessLogic operators disabled
2. Create sonataflow-infra namespace
Actual results:
sonataflow-infra ns is deleted
Expected results:
I expect it would stay if it was created manually
- depends on
-
FLPATH-2239 [m5] Need method to understand which Orchestrator CR params can change day 2
-
- Closed
-
- relates to
-
FLPATH-2164 [m5] After deleting orchestrator CR, DI pod isn't removed after OSL and serverless operators are deleted
-
- Closed
-