https://pulumi.com
Join Slack
This message was deleted.
# google-cloud
s
This message was deleted.
g
Pulumi preview show the worst case scenario. A change in the cluster may cause a change in the k8s Provider, changing the Provider means Pulumi don't know if any of the resources that are created from it will be available, they might not be and would need to be replaced with a new one. There is probably a missing value in your 
privateClusterConfig
that is being filled with a default value by the API and being cleared by Pulumi every time. Check the docs to see if something is missing.
r
you again 😉 thx so much for the help and the pointers 😉
Hmmm this is the detailed output from Pulumi:
and this how privateClusterConfig is specified in Pulumi:
Copy code
privateClusterConfig: { enablePrivateEndpoint: false, enablePrivateNodes: true, masterGlobalAccessConfig: {enabled: false}, masterIpv4CidrBlock: config.clusterMasterIpv4CidrBlock },
based on the output I would have thought I havent specified enabled...
g
Ok, this is a particularity of the GKE api, this whole block is removed when it is disabled, since it is the default. So Pulumi is trying to add it again, it is the opposite of what I said. You can either not add it on your config or explicitly tell Pulumi to ignore it.
I'm not sure if Pulumi can ignore just the 
masterGlobalAccessConfig
or if it can just ignore root attributes (
privateClusterConfig
in this case)
4 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by