tazjin

Interesting! I started working on the issues you reported yesterday - but time is currently a scarce resource :-)

Hey! I think this could be handled by loading all services and collecting data about which certificates to load from that. If multiple services specify the same `secretName` they could...

Open question here is how to support this for a certificate list that spans multiple domains 🤔 One way would be to have an additional annotation that lets users specify...

> I wonder if just upgrading that dependency would fix this? That's a good bet! I don't actively maintain this at the moment, but if you'd like to try doing...

Hm, thanks for pinging! I've also seen this a few times on a GCP cluster, though it eventually sorts itself out. Still worth investigating whether I've misread the docs about...

I've read through the docs again and as far as I can tell, `DONE` should mean done (but doesn't). I'll up the wait timer and investigate the Let's Encrypt API...

From the [ACME spec](): ``` Clients SHOULD NOT respond to challenges until they believe that the server’s queries will succeed. If a server’s initial validation query fails, the server SHOULD...

Update on this: acme4j has been updated and there is a pending 2.0 release (currently available as a snapshot release), which will be released in stable form before Let's Encrypt...

@joeherwig Yep, it's on the TODO-list. I won't have time before the end of next week though. If any changes (other than a version bump of the ACME-lib) are required,...

@mansona Hey! As far as I know acme4j (the upstream library this project uses for speaking to Let's Encrypt) has been updated with support for wildcard certificates, so the first...