red-area-47037
10/07/2020, 11:04 AM~ ├─ gcp:container:Cluster staging-k8s update [diff: ~privateClusterConfig]
and all Kubernetes resources will be replaced:
...
├─ kubernetes:yaml:ConfigFile argocdsecret
+- │ └─ kubernetes:core/v1:Secret infra/ops-playground replace [diff: ~data,metadata,provider]
├─ kubernetes:yaml:ConfigFile letsencrypt_staging
+- │ └─ kubernetes:<http://cert-manager.io/v1:ClusterIssuer|cert-manager.io/v1:ClusterIssuer> infra/letsencrypt-staging replace [diff: ~metadata,provider]
├─ kubernetes:yaml:ConfigFile letsencrypt_prod
+- │ └─ kubernetes:<http://cert-manager.io/v1:ClusterIssuer|cert-manager.io/v1:ClusterIssuer> infra/letsencrypt-prod replace [diff: ~metadata,provider]
+- ├─ kubernetes:core/v1:Namespace m2 replace [diff: ~metadata,provider]
├─ kubernetes:<http://helm.sh/v2:Chart|helm.sh/v2:Chart> cert-manager
...
Still when running Pulumi, only the privateClusterConfig gets updated and the Kubernetes resources are not "touched":
...
~ ├─ gcp:container:Cluster staging-k8s updated [diff: ~privateClusterConfig]
...
Resources:
~ 1 updated
117 unchanged
Does anyone have a tip on how to fix it?green-school-95910
10/07/2020, 11:47 AMprivateClusterConfig
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.red-area-47037
10/07/2020, 12:02 PMprivateClusterConfig: { enablePrivateEndpoint: false, enablePrivateNodes: true, masterGlobalAccessConfig: {enabled: false}, masterIpv4CidrBlock: config.clusterMasterIpv4CidrBlock },
green-school-95910
10/07/2020, 2:01 PMmasterGlobalAccessConfig
or if it can just ignore root attributes (privateClusterConfig
in this case)