millions-judge-2497801/28/2020, 11:33 PM
breezy-hamburger-6961901/29/2020, 2:13 AM
millions-judge-2497801/29/2020, 2:58 PM
breezy-hamburger-6961901/29/2020, 3:46 PM
millions-judge-2497801/29/2020, 3:49 PM
is updating unexpectedly, causing a diff to internal providers and subsequently other resources
I’m still trying to understand more so I can open a useful issue
├─ infrastructure:k8s-cluster-v2 cluster-us2 │ └─ eks:index:Cluster cluster-us2 ~ │ ├─ aws:ec2:SecurityGroup cluster-us2-eksClusterSecurityGroup update [diff: ~tags] ~ │ ├─ aws:eks:Cluster cluster-us2-eksCluster update [diff: ~tags] ~ │ ├─ aws:ec2:SecurityGroup cluster-us2-nodeSecurityGroup update [diff: ~tags] ~ │ ├─ pulumi-nodejs:dynamic:Resource cluster-us2-vpc-cni update [diff: ~__provider,kubeconfig] +- │ ├─ pulumi:providers:kubernetes cluster-us2-eks-k8s replace [diff: ~kubeconfig] +- │ ├─ kubernetes:core:ConfigMap cluster-us2-nodeAccess replace [diff: ~metadata,provider] +- │ ├─ aws:ec2:LaunchConfiguration cluster-us2-nodeLaunchConfiguration replace [diff: ~userData] ~ │ ├─ aws:cloudformation:Stack cluster-us2-nodes update [diff: ~tags,templateBody] +- │ └─ pulumi:providers:kubernetes cluster-us2-provider replace [diff: ~kubeconfig]
and that seemed to somehow make the other diffs disappear
breezy-hamburger-6961901/31/2020, 1:13 AM
before the update?
millions-judge-2497801/31/2020, 1:15 AM
. I tried a
halfway though doing the targeted applies thinking that might fix the rest of the clusters faster. It seemed to have no effect.
breezy-hamburger-6961901/31/2020, 1:16 AM
millions-judge-2497801/31/2020, 1:16 AM