-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
1.5.0
-
False
-
-
False
-
-
-
Moderate
Description of the problem:
Changing the sonataflow platform resources in the Orchestrator CR post deployment (day 2) does not propagate to the sonataflow-platform resource.
How reproducible:
100%
Steps to reproduce:
1. Deploy Orchestrator operator m5
2. Deploy orchestrator resource
oc get orchestrators.rhdh.redhat.com orchestrator-sample -o yaml
platform:
eventing:
broker: {}
monitoring:
enabled: false
namespace: sonataflow-infra
resources:
limits:
cpu: 500m
memory: 1Gi
requests:
cpu: 250m
memory: 64Mi
3. After deployment, change resource values in orchestrator cr
resources: limits: cpu: 550m memory: 1Gi requests: cpu: 260m memory: 64Mi
4. Check sonataflow platform resource
oc get sonataflowplatforms.sonataflow.org sonataflow-platform -n sonataflow-infra -o json | jq '.spec.build.template'
Actual results:
Values never change (waited 5 minutes and even restarted orch operator controller pod)
{
"resources": {
"limits": {
"cpu": "500m",
"memory": "1Gi"
},
"requests": {
"cpu": "250m",
"memory": "64Mi"
}
},
"timeout": "0s"
}
Expected results:
Changes propagate
- is duplicated by
-
-
- Closed
-