Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
s
straight-magician-37467
07/14/2021, 6:58 PMI 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
witty-dentist-91954
07/14/2021, 9:02 PMYou 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
straight-magician-37467
07/14/2021, 9:20 PMThank you, I will look into doing that.