This message was deleted.

I can create a cluster with a fixed list of

AgentPoolProfiles

no problem. but if I want to add another pool after the cluster has been created, I need to use the

AgentPool

resource and provide it with the cluster name, resource group name, etc.

I think @sparse-park-68967 might have some context around this

You should be able to create a new system nodepool separate from the cluster’s agent profile one. You can name it something that clearly marks it as a new system nodepool. Eventually you should be able to just delete the original nodepool and have everything safely migrate over to the new nodepool. You might have to update the references in the nodepool profile to match the new nodepool in the cluster and do a pulumi refresh. Note I haven’t tried the latter with azure nextgen - this is what I had to do with the old provider. I have been meaning to look into the process for azure-nextgen but haven’t gotten around to it. I will take a look later today and update here. But adding the system nodepool should be entirely safe.

Thanks for taking the time to look into it. subsequent system pools are working fine, as long as i manually delete the default pool afterwards. is there a way to see if the ComponentResource is being created? that way it can easily know not to create an

AgentPool

for the first system pool without the user of my component having to know the internals (I want them to specify a list of pools, with a requirement that there is a minimum of 1 system pool) i have a similar problem when deleting the cluster after adding a new system pool and deleting the original.

pulumi destroy

fails because it tries to delete the only remaining system pool before deleting the cluster.