Document cleanup procedures after deletion
Summary
When our chart is deleted, several items are left behind: multiple Secrets, and the PersistentVolume & PersistentVolumeClaim from the Gitaly StatefulSet. We should add simple documentation on how to ensure all items from this chart are cleaned up.
Steps to reproduce
$ helm install gitlab/gitlab -n gitlab
$ helm delete --purge gitlab
$ kubectl get secrets,pv,pvcConfiguration used
(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))
(Paste sanitized configuration here)Current behavior
$ kubectl get secrets,pv,pvc,hpa,pdb
NAME TYPE DATA AGE
secrets/default-token-fsrj8 kubernetes.io/service-account-token 3 184d
secrets/gitlab-gitlab-initial-root-password Opaque 1 13d
secrets/gitlab-acme-key Opaque 1 13d
secrets/gitlab-gitaly-secret Opaque 1 13d
secrets/gitlab-gitlab-runner-secret Opaque 2 13d
secrets/gitlab-gitlab-shell-host-keys Opaque 8 13d
secrets/gitlab-gitlab-shell-secret Opaque 1 13d
secrets/gitlab-gitlab-workhorse-secret Opaque 1 13d
secrets/gitlab-minio-secret Opaque 2 13d
secrets/gitlab-postgresql-password Opaque 1 13d
secrets/gitlab-rails-secret Opaque 1 13d
secrets/gitlab-redis-secret Opaque 1 13d
secrets/gitlab-registry-httpsecret Opaque 1 13d
secrets/gitlab-registry-secret Opaque 2 13d
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pv/pvc-58a48976-de0e-11e8-81bb-42010a800196 50Gi RWO Delete Bound default/repo-data-gitlab-gitaly-0 standard 13d
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
pvc/repo-data-gitlab-gitaly-0 Bound pvc-58a48976-de0e-11e8-81bb-42010a800196 50Gi RWO standard 13dExpected behavior
$ kubectl get secrets,pv,pvc,hpa,pdb