5 ms·
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
by alpb 5y ago
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.
- egberts1 5y agoHTTP 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.
- rmhrisk 5y agoWith the recent GCP Cloud Certificate Manager release the global propagation time is minutes. (I should note I was a PM for this feature)