millions-judge-24978
01/28/2020, 11:33 PM0.18.19
release inadvertently?breezy-hamburger-69619
01/29/2020, 2:13 AMmillions-judge-24978
01/29/2020, 2:58 PMplan
I meanbreezy-hamburger-69619
01/29/2020, 3:46 PMmillions-judge-24978
01/29/2020, 3:49 PMkubeconfig
is updating unexpectedly, causing a diff to internal providers and subsequently other resources
├─ 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]
I’m still trying to understand more so I can open a useful issue~tags
and that seemed to somehow make the other diffs disappearbreezy-hamburger-69619
01/31/2020, 1:13 AMpulumi refresh
before the update?millions-judge-24978
01/31/2020, 1:15 AM0.18.18
. I tried a refresh
halfway though doing the targeted applies thinking that might fix the rest of the clusters faster. It seemed to have no effect.breezy-hamburger-69619
01/31/2020, 1:16 AMmillions-judge-24978
01/31/2020, 1:16 AM