-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 3247, GITOPS Sprint 3248, GITOPS Sprint 3249
Story (Required)
Ensure the operator can be successfully installed on both staging and in production environmentÂ
Background (Required)
There are some challenges when if comes to installing the operator on hosted clusters. This story is intended to solve such problemsÂ
Out of scope
Testing the operator functionality
Approach (Required)
Follow the regular approach we use for installation of RC and a productized version. Note the challenges and come up with solution for any issues faced
Dependencies
You are able to get a hypershift cluster
Acceptance Criteria (Mandatory)
- Operator installation on a Hypershift cluster is successfulÂ
- Acceptance tests are run (KuTTL and ArgoCD UI login)
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
- Unit and integration 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
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- is cloned by
-
GITOPS-3482 Installation of GitOps operator in staging and production
- Closed
- mentioned on