Charles Moulliard

> If you run with single replica workloads, you should attempt to disable leader election. Unfortunately when we install the YAML resource file, cert-manager is deployed under its namespace: cert-manager...

> Anything interesting in the cert-manager log when this occurs? No. This is what the log of cert-manager reports ``` I0624 08:25:01.647245 1 controller.go:89] "enabled controllers: [certificaterequests-approver certificaterequests-issuer-acme certificaterequests-issuer-ca certificaterequests-issuer-selfsigned...

I don't know if this is related but the Webhook is reporting such errors ``` E0624 09:05:00.551225 1 dynamic_source.go:221] "Failed to generate serving certificate, retrying..." err="no tls.Certificate available yet, try...

Is the PR already released part of the latest catchup plugin and available on kodi ? Does it fix the issue reported ?

Such a feature is not documented at all as all the examples use `//` ;-)

this is what I did in our util class ``` /** * The array list of the kubernetes resources should be formated as such * * --- * manifest1 *...

> **Edit:** Anyone in here now how to extend the delay? I want to try this by the answer I got: https://community.letsencrypt.org/t/challenge-failed-and-got-error-dns-problem-nxdomain-looking-up-txt/225975/4?u=david-gh If I understand well the issue, this plugin...

This is where within the code we call GoDaddy to check if the TXT record exists: https://github.com/snowdrop/godaddy-webhook/blob/main/main.go#L226

I don't really know when the function `cleanUp(` is called or triggered. To figure out what it happens we will have to contact core engineers working on cert-manager.

Here is how cert manager is calling the Webhook cleanup From Adam Talbot ``` There are two cases I can see in the cert-manager codebase When a challenge has reached...