otomi-core
otomi-core copied to clipboard
Leverage ArgoCD to deploy Otomi apps
WHY
To improve platform robustness, reliability, time to deploy and self healing.
User Story
AS A a platform engineer I WANT TO all Helm releases to be independently deployed SO I can benefit from the controller pattern
Acceptance criteria
GIVEN all Helm releases defined in the helmfile.d/
WHEN Tekton pipeline is triggered
THEN it deploys all Helm releases as ArgoCD Applications
GIVEN installed Helm releases in existing instance of Otomi WHEN Otomi upgrade happens THEN ArgoCD application can takeover control over the already installed Helm releases
Design document: https://redkubes.atlassian.net/wiki/spaces/KB/pages/5283217409/GitOps+-+deployment+pipeline Spike: https://app.zenhub.com/workspaces/dev-5e7e84dddc966f05a627a19b/issues/gh/redkubes/unassigned-issues/576
Definition of done
- [ ] Relevant PRs are merged
- [ ] Tested by peer
- [ ] Updated documentation reviewed by peer
- [ ] Short demo video recorded and stored on google drive (if applicable)