As a developer/operator of GC Notify, I would like to be able to take backups of the EKS cluster configuration before each apply on the manifests repository.
WHY are we building?
Right now, if the kubernetes configuration gets corrupted, we are relying only on the Kustomization to reapply. While this is good, it may not have the complete picture, and is unable to do point-in-time snapshots of the EKS cluster.
WHAT are we building?
Implement Velero into staging and production EKS.
Add velero backup create commands to any Github action that modifies the EKS cluster
VALUE created by our solution
This will increase our resiliency and enable faster disaster recovery. It will also put us in a position to leverage Velero in the future for any persistent data stored in Kubernetes.
Acceptance Criteria
[ ] Velero implemented as deployment as code
[ ] Velero backup create integrated within GH Actions
QA Steps
[ ] Run velero backup create and velero backup restore in staging with no issues.
Description
As a developer/operator of GC Notify, I would like to be able to take backups of the EKS cluster configuration before each apply on the manifests repository.
WHY are we building?
Right now, if the kubernetes configuration gets corrupted, we are relying only on the Kustomization to reapply. While this is good, it may not have the complete picture, and is unable to do point-in-time snapshots of the EKS cluster.
WHAT are we building?
VALUE created by our solution
This will increase our resiliency and enable faster disaster recovery. It will also put us in a position to leverage Velero in the future for any persistent data stored in Kubernetes.
Acceptance Criteria
QA Steps