Exposer pods continue to run after cert is issued

tnozicka / openshift-acme

ACME Controller for OpenShift and Kubernetes Cluster. (Supports e.g. Let's Encrypt)

Apache License 2.0

319 stars 116 forks source link

Exposer pods continue to run after cert is issued #149

Closed lukastheblack closed 3 years ago

lukastheblack commented 3 years ago

I had to create a large amount of routes recently for work, and this deployment successfully issued lets encrypt certs for them. The problem is that I have 60+ exposer pods still running in the namespace, no errors in the openshift-acme logs, no errors on the pods themselves, and I'm confused as to how to remove them correctly. Please advise, and let me know what other information I can provide.

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

lukeelten commented 3 years ago

I have the same issue and found the problem. The controller does not set the correct API Version in the owner reference of the dependent resources. It sets the API Version to v1 while route.openshift.io/v1 would be the proper version for kubernetes to actually run garbage collection on those resources.