sablumiah
commented
2 years ago Current list of user EBS Volumes:
NAMESPACE NAME
c100-application-metabase metabase-datadir
check-financial-eligibility-uat data-ap-3364-update-ingress-check-financial-postgresql-0
check-financial-eligibility-uat data-ap-3415-update-uat-postgres-postgresql-0
check-financial-eligibility-uat data-postgresql-0
check-financial-eligibility-uat data-test-postgresql-0
dso-monitoring-dev grafana-dev
dso-monitoring-dev prometheus-alertmanager
dso-monitoring-dev prometheus-server
dso-monitoring-prod grafana
dso-monitoring-prod prometheus-alertmanager
dso-monitoring-prod prometheus-server
helloworldjotw-dev pvc-mysql
helloworldjotw-dev pvc-wordpress
helloworldjotw-dev www-web-0
hmcts-mock-api-dev data-hmcts-mock-postgresql-0
hmpps-probation-webops-poc data-multi-container-app-postgresql-0
laa-court-data-adaptor-dev data-postgresql-0
laa-court-data-adaptor-prod data-postgresql-0
laa-court-data-adaptor-stage data-postgresql-0
laa-court-data-adaptor-test data-postgresql-0
laa-court-data-adaptor-uat data-postgresql-0
laa-test-viewer laa-test-viewer-pvc
laa-test-viewer laa-tv-chart-pvc
Background
To reduce cost and improve security on the platform we need to delete old EBS snapshots.
Approach
Clean-up old snapshots
Which part of the user docs does this impact
N/A
Questions / Assumptions
Do we need to communicate changes to our users? Do we have the necessary authority to delete EBS snapshots/Do we need permission from teams? Should we be automating this process?
Definition of done
Reference
How to write good user stories