I have a couple of GCR containers behind a load ba...
# google-cloud
s
I have a couple of GCR containers behind a load balancer with a custom domain, but when I update one of the containers using pulumi, the domain doesn’t point to the new container. Do I need to do something manually in my pulumi script, or is it more likely that I’ve simply misconfigured this in Google Cloud itself?
Notice that these services have randomized hashes on the end. When I create my next build, it has a new randomized hash, and the load balancer doesn’t follow along.
w
You could give your containers a fixed name in pulumi (with the name=attribute), but I'm not shure if updating the containers would work seamless.
The better way is to add your load balancer to your pulumi script and update it with the new container names.
s
Thank you, I will look into doing that.