-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
upgrade witout resources recreation
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
NEW
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Make sure that some resources (statefulsets, especially those whose Pods take time to restart, for example Prometheus) are not unintentionally recreated to avoid downtime.
Why is this important?
- Avoid downtime.
- Avoid cases where Kubernetes cannot handle correctly the recreation of the resource. => All the resource's pods are stuck e.g.
- prometheus-operator uses foreground deletion when an immutable field of a statefulset e.g. is modified, see https://issues.redhat.com/browse/OCPBUGS-17346 where matchLabels was modified.
Scenarios
Acceptance Criteria
- We have a test (origin?) that makes sure of this during upgrades.
- It should be easy to temporarily disable the test in case we cannot avoid a recreation during an upgrade.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- I thought about adding an origin test during upgrades, we had a discussion with Simon on https://issues.redhat.com/browse/OCPBUGS-17346?focusedId=22743037&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-22743037 (about the maintainability of such tests)
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is caused by
-
OCPBUGS-17346 Avoid recreating prometheus Statefulset during 4.13 > 4.14 upgrades
- Closed