ADR: CI/CD for Kubernetes

[ben851]

Description

As a developer of notify, I would like to have a clear understanding of how the CICD for Kubernetes works, as well as provide a road map for improvements.

WHY are we building?

There's no documentation on how CI/CD is done for Kubernetes. Since we are in the process of migrating from Kustomize to Helmfile, it would be a good time to document both the existing process, as well as the changes required to implement helmfile.

WHAT are we building?

An ADR documenting how our CI/CD works.

VALUE created by our solution

Increased knowledge at the team level Easier troubleshooting of environments

Acceptance Criteria

• [ ] The current CI/CD process is documented
• [ ] Any changes required for Helmfile are documented and approved by the team
• [ ] The team has reviewed the ADR and does not have any questions or concerns.

[ben851]

Working on first PR with existing CICD

[ben851]

Existing CICD ADR has been PR'ed

https://github.com/cds-snc/notification-adr/pull/71

[ben851]

Reworked the existing ADR to include both current and future state for the release process.

[sastels]

All should read the ADR and we should discuss. Will discuss at dev review with the thought being we'll talk about it in depth next week.

[ben851]

Wanting to expand on the ADR diagrams, I decided to look into auto-generated workflow maps. I'm work on a github workflow that will auto-generate this.

[jimleroyer]

Jimmy reviewed the ADR and Ben to reply on his comments, questions or suggestions.

[ben851]

Started reviewing this yesterday - merged the quick suggestions, will work on the others.

[ben851]

Added in diagrams of all the CI/CD processes for PR and merge to main/releases

[ben851]

Updated the PR to be a bit more focused in messaging. Ready to be reviewed.

[ben851]

Jimmy and Pond reviewed - I will review their review