When updating from 1.0.0 to 1.1.0 the images are upgraded
Summary
When upgrading from 1.0.0 to 1.1.0 all the images of an SGCluster (or SGDistributedLogs) before running any security upgrade SGDbOps.
Current Behavior
After StackGres is upgraded the SGCluster (or SGDistributedLogs) should not be in PendingRestart
.
Steps to reproduce
- Install StackGres 1.0.0
- Create a cluster
- Upgrade StackGres to 1.1.0-beta1
Expected Behavior
After StackGres is upgraded the SGCluster (or SGDistributedLogs) is not in PendingRestart
.
Possible Solution
Create a list of previous image versions for all previous StackGres versions and apply accordingly to the operator version annotation present on the SGCluster or SGDistributedLogs
Environment
- StackGres version: 1.1.0-beta1
- Kubernetes version: ?
- Cloud provider or hardware configuration: ?
Relevant logs and/or screenshots
Run e2e test dbops-secutiry-upgrade by setting STACKGRES_PREVIOUS_VERSION
env var to 1.0.0
.