You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In reference to this issue which does not allow updating the default node pool, what is the recommended approach for getting around this, in order to update the VM size?
I have tried the following:
Updating the VM size directly in defaultNodePool and setting temporaryNameForRotation resulted in the linked issue.
Create a new node pool resource, but cannot set this as default. Its also not legal to delete the defaultNodePool block so this does not work.
Since defaultNodePool seems to be a list property, I tried to add a new pool, but defining multiple pools within this block is not legal.
The text was updated successfully, but these errors were encountered:
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!
Hello!
In reference to this issue which does not allow updating the default node pool, what is the recommended approach for getting around this, in order to update the VM size?
I have tried the following:
The text was updated successfully, but these errors were encountered: