No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

My code is a mess so I can’t send you a snippet, but look up `ManagedClusterAgentPoolProfileArgs`

There’s an `OrchestratorVersion` in there you have to set

afaict, though, you can’t modify `maxSurge` settings via Pulumi, which is causing me no end of headaches

ah thank you. Missed the orchestrator_version. Was looking for kubernetes_version like in the cluster

thanks for the info with maxSurge. Hopefully it works with the default for me.

if you are also dealing with this stuff right now, do you use the auto_upgrade_profile option?

No, I’m a bit scared of letting azure do these updates for me atm. I want to get there but I want to prove out the upgrade process a bit first tho

Which is why I’m trying to get it working smoothly in Pulumi so we aren’t doing it through the portal

we have also automated this stuff, so I tried this parameter in pulumi just to update the node_images and not the kubernetes_versions