Re:Automate Public Certificates Lifecycle Management via RFC...
by alpb on Tuesday April 12, 2022 @02:19AM
(#30999255)
One major problem with Google’s L7 load balancers is that the config changes take 5-20 mins to take effect. So google trying to set up an ACME challenge on a LB, solving it, and setting the managed TLS cert on it can take non-negligible time (15-30 mins?). I hope this gets fixed someday.
[ Parent
| on HN ]
Re:Automate Public Certificates Lifecycle Management via RFC...
by rmhrisk on Tuesday April 12, 2022 @08:51AM
(#31001955)
With the recent GCP Cloud Certificate Manager release the global propagation time is minutes. (I should note I was a PM for this feature)
Re:Automate Public Certificates Lifecycle Management via RFC...
by egberts1 on Tuesday April 12, 2022 @04:56AM
(#31000175)
HTTP caching is probably and should be turned off when accessing a specific subdomain for ACME challenge (at Google reverse proxy level), I think.
One should not have to do anything extra unless the requester too also run a load balancer in front of their subdomain in question.
That’s why ACME challenge offers several different type of protocols (to get by the many caching servers.