Open paulcwarren opened 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/175746818
The labels on this github issue will be updated when the story is started.
As you can see in https://github.com/cloudfoundry/cf-for-k8s/commit/72988bc38bfe5993ad6e31b0938259b5384ca9ca, we found a relatively simple workaround. We just need to force delete the pod (after first deleting the statefulset backing it) to get kapp delete working even on newer versions of Kubernetes.
kubectl delete statefulset cf-db-postgresql -n cf-db
kubectl delete pod cf-db-postgresql-0 -n cf-db --force --grace-period 0
We'll do some more investigation to figure out a path forward towards a proper solution to this problem but for now, we're at least unblocked and now running the latest K8s versions for our EKS and GKE tests.
Describe the bug
On two different k8s 1.18 distros (gcp and eks) we have seen a failure to delete cf-for-k8s because the database PV fails to delete.
To Reproduce*
Steps to reproduce the behavior:
kapp delete -a cf
Expected behavior
The kapp deletion is successful
cf-for-k8s SHA
Latest develop
Cluster information
Observed so far on 1.18 GCP & EKS