Have anyone successfully changed the system node vm type of a Pulumi-managed AKS cluster? The descri...

late-airplane-27955

12/20/2024, 4:18 PM

Have anyone successfully changed the system node vm type of a Pulumi-managed AKS cluster? The description briefly mentions:

If needing to change the initial agent pool profile property, you can either trigger the whole cluster to be re-created by using the replaceOnChanges resource option, or make the change directly in Azure then use
pulumi refresh
to update the stack’s stack to match.

I tried this now, but it doesn't work right. Anyone have done this and happend to note the steps they performed?

late-airplane-27955

12/20/2024, 4:21 PM

when doing a "refresh" pulumi doesn't replace the old system pool with the new, it takes whatever happened to be the first node pool (which in probably 99% of the cases is a user pool. So I'm getting this diff:

Copy code

~ agentPoolProfiles: [
          ~ [0]: {
                  - enableAutoScaling: true
                  - maxCount         : 3
                  - minCount         : 1
                  ~ mode             : "User" => "System"
                  ~ name             : "lin02" => "lin03"
                  + nodeTaints       : [
                  +     [0]: "CriticalAddonsOnly=true:NoSchedule"
                    ]
                  - scaleDownMode    : "Delete"
                  ~ vmSize           : "Standard_E2as_v5" => "Standard_F2s"
                }

I have no idea if that's expected or not

Open in Slack

Previous Next

Pulumi Community

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.