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
m
most-lighter-95902
11/27/2021, 3:18 AMIt looks as though running
pulumi upk8s.yaml.ConfigFileb
brave-ambulance-98491
11/29/2021, 5:08 PMThis is working-as-expected if you're reusing config map names and not letting Pulumi generate it.
Here's an issue with more info: https://github.com/pulumi/pulumi-kubernetes/issues/1568
m
most-lighter-95902
11/29/2021, 5:23 PM@brave-ambulance-98491 thanks for this! So is the solution here setting the
replaceOnChangesBut not sure if this is the cause actually since I didn’t change anything - just doing
pulumi upb
brave-ambulance-98491
11/29/2021, 5:29 PMThis sounds like multiple problems, and might be a problem with the remote file; it could be a caching issue.
Can you try downloading a local copy instead, and seeing if that doesn't trigger an update?
m
most-lighter-95902
11/29/2021, 5:30 PMSo this error happens only intermittently - but so far, downloading it locally doesn’t seem to cause this error
Is there a way for me to confirm more definitively if locally downloading it is indeed not causing this error?
Oh hmm - ok so I might actually be changing something when I rerun this. The flow is 1) Knative Operator install sets up some default ConfigMaps and 2) I’m setting some config values using this Operator which alters these default ConfigMaps. So when I run the flow again, I guess Knative Operator is trying to rerun the default ConfigMaps which triggers an update - or rather a replacement?
Still not sure what this error means or how to resolve it?
Why does updating ConfigMaps cause this
Circularb
brave-ambulance-98491
11/29/2021, 5:39 PMSo, I can't speak as much to that; mostly, the attempt to delete & recreate is what I was speaking to.
I could see updating a configmap in-place triggering extra deletes & recreates, if change detection is buggy. You should try using dynamic names of the configmaps, if that's possible, which might help this part.
m
most-lighter-95902
11/29/2021, 5:41 PMI don’t think I can change the dynamic names since that might break the default Operator behavior
Maybe I could use
replaceOnchanges: ['*']