-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 3244, GITOPS Sprint 3245, GITOPS Sprint 3246, GITOPS Sprint 3250, GITOPS Sprint 3251, GITOPS Sprint 3252, GITOPS Sprint 3253, GITOPS Sprint 3254
Story (Required)
As a QE trying to automate the z stream releases, I want to add Operator upgrade task as part of downstream CI
Background (Required)
As of now, we do not have any automated way of testing operator upgrade and it adds to manual effort spent by QE team. By automating operator upgrade task, we can deliver faster results
Out of scope
Openshift upgrade is not covered as part of this story
Approach (Required)
- Find a way to accommodate both direct installation and upgrade
- Create necessary secrets in the bootstrap cluster
- Write a task for upgrading operator
- Add the task into acceptance Pipeline
- Upgrade path for all the supported operator version should be connected (Example: v1.8.z upgrade path should be tested from v1.6.z )
Dependencies
N/A
Acceptance Criteria (Mandatory)
- Points in Approach list above is covered
- Acceptance test pipeline is passing for upgrade test
- Upgrade task is not breaking the further execution
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Acceptance criteria are met