.status.dbOps is not updating during operation in SGCluster custom resources
Summary
Field .status.dbOps
in SGCluster
custom resource is not being updated when the dbops perform change in the internal status. This is happening for restart
and securityUpgrade
operations.
Steps to reproduce
- Create a sgcluster
- Create a sgdbops of type
restart
that reference the created sgcluster
Expected Behaviour
When operation is starts, fails, completes, a pod is added, a pod is restarted, or when the switchover is performed the .status.dbOps
field should be updated.
Possible Solution
After operation is starts, fails, completes, a pod creation, a pod restart or a switchover update the status of the operation in the sgcluster under the field .status.dbOps
Environment
- StackGres version: 1.0.0-beta1-SNAPSHOT
- Kubernetes version: ?
- Cloud provider or hardware configuration: ?
Edited by Matteo Melli