https://pulumi.com logo
Join Slack
Powered by
Going off my last issue with being unable to updat...
# google-cloud
a
Going off my last issue with being unable to update an existing cluster's nodepools from within pulumi, is it possible to update something within the console/cli then import that change to pulumi? As it stands the only solution to continue using pulumi is to completely delete the current cluster and recreate it with the new nodepool configuration, which is not something that I can do. Any help would be appreciated.
b
yes, you can use 
pulumi import
or the 
import
resource provider
if you update the nodepool, then do 
pulumi refresh
(if you've already written pulumi code) pulumi will tell you what has changed
a
Ok great I'll try that. Thank you.
It seems like when I try to refresh the stack it keeps the cluster's old config and setting the value to the actual config makes it think that there is a change that needs to be applied when in reality there shouldn't be.
n
Been there, done that.. so..
Copy code
pulumi.IgnoreChanges(
			[]string{
				`metadata.annotations["<http://deployment.kubernetes.io/revision|deployment.kubernetes.io/revision>"]`,
				`metadata.selfLink`,
				`nodeConfig`,
				`nodePools`,
			},
		),
☝️ This is basically the only way I found to stop 
pulumi
from replacing my cluster on each update
And it works great 😛
a
Thank you I'll put this in.
✅ 1
n
My pleasure ^^
2 Views
Open in Slack
PreviousNext
Powered by