-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AKS: after a pulumi refresh it wants to replace the cluster #393
Comments
Hi @0x53A Please can you get the details view that shows what needs to change and post it here (minus any secrets!) Paul |
oops, I had created a second Windows NodePool in the Portal manually (because Pulumi / TerraForm don't yet support that) and promptly forgot about it. Sorry about that, I'll go home. Is there a way to tell the diff engine to ignore this? (for reference, these are the blockers for windows node pool support afaik: hashicorp/terraform-provider-azurerm#3971 |
Yes - you can use |
Neat, I added the flag, but now I get these errors:
I'd guess that it has filled in unset values (like Thank you. |
I created an AKS cluster. Then I ran
pulumi refresh
.Now on the next
pulumi up
it wants to replace the whole cluster:but when I look at the diff, there aren't any actual changes. In the output, both agentPoolProfiles are exactly the same.
This is the agentPoolProfiles in my script
this is the diff output:
The text was updated successfully, but these errors were encountered: