Kubernetes-enabled Drone CI currently has two problems.
- Cleaning up jobs is dependent on TTL, which is not enabled by default in most Kubernetes clusters.
- someone made a really nice tool to clean jobs/pods that are completed. https://github.com/lwolf/kube-cleanup-operator
- For each app's pipelines, it creates a namespace. Which is really nice, but sometimes it creates forever terminating namespaces.
- I just added a hacky bash script to filter terminating drone CI created namespaces and used this to forcibly kill those: https://github.com/ctron/kill-kube-ns
You also have to give it the right authorization on a RBAC-enabled cluster. I don't recommend using this on a production cluster. Probably waiting for Drone CI to mature is a better idea.