<p>I've updated the SSL certificate for my Kubernetes Ingress services, but I don't know how to restart the instances to use the updated cert secret without manually deleting and restarting the Ingress instances. That isn't ideal because of the number of ingresses that are making use of that specific cert (all sitting on the same TLD). How do I force it to use the updated secret?</p>

<p>Turns out the reason why it wasn't updating was that the certs weren't chained properly; I uploaded the ca-bundle without the actual end cert, and I guess Google refuses to update the LB certs if they're not a valid chain. Which is weird, but, okay, sure.</p>
