Any idea why a nodepool is trying to be replaced a...
# generalc
cool-egg-852
08/07/2019, 4:01 PMAny idea why a nodepool is trying to be replaced and the only thing the diff shows different is the provider?
cool-egg-852
08/07/2019, 4:02 PMIt looks like it’s moving from an unversioned to versioned provider urn
cool-egg-852
08/07/2019, 4:03 PMprovider: urn:pulumi:development::kubernetes::pulumi:providers:gcp::default::d677eab5-3f94-408d-92df-515c212c488b => urn:pulumi:development::kubernetes::pulumi:providers:gcp::default_0_18_15::output<string>cool-egg-852
08/07/2019, 5:24 PMSeems like other resources are having the same issue, but they are just updating. No matter what, why is the provider causing any changes like this.
cool-egg-852
08/07/2019, 5:24 PMCurrently I have a deployment stuck because the provider is changed, and it’s waiting for the replicaset to be ready, though nothing is changed there
cool-egg-852
08/07/2019, 5:25 PMIt also says it’s replaced the NodePools, though it hasn’t removed the old ones yet.
w
white-balloon-205
08/07/2019, 6:51 PM
I would not expect the change to the provider to be the root cause of the replacement. cc @microscopic-florist-22719 in case he has troubleshooting thoughts.
c
cool-egg-852
08/07/2019, 7:10 PMIt’s the only thing that is output in the diff. I didn’t change any of the code related to that resource either
cool-egg-852
08/08/2019, 8:24 PMJust bumping this one.
m
microscopic-florist-22719
08/08/2019, 10:55 PM
The provider change does seem like it is probably the issue. Can you DM me the full logs?