This is the details output when I do not try to import the existing ResourceGroup:

i'm not super familiar with Azure, but it looks like just the tags are diff?

there are no tags on any of the resources in azure and the pulumi app doesn't want to put any on either.

That's because you've flagged the resource as protected in Pulumi

const resourceGroup = new azure.core.ResourceGroup("rg-kubernetes",{
        name: "rg-kubernetes",
    },{
        //import: "/subscriptions/ad73ec2e-0337-4de5-983c-3944fcb68be8/resourceGroups/rg-kubernetes",
        protect: true, ignoreChanges: ["tags", "id"]
    }
);

is producing this

replacement

action...

Was the resource group previously created with Pulumi? AFAICT, it looks like it wasn’t, so Pulumi is planning to replace the existing one with one of the same name that it manages.

@gorgeous-egg-16927 This behaviour happens if I try to do include or exclude the

import

statement.

Hmm, I’m not really sure what’s going on. Any ideas @sparse-park-68967 ?

so the RG is currently imported in pulumi state along with the cluster? (sorry catching up here)

I guess I'm wondering why an

import

directive wants to replace the RG? Replacing an RG is a delete/recreate action afaik and deleting an RG will cause everything inside of it to get deleted too. Our control planes are in that RG, so if they get deleted, then all the clusters and everything in them gets deleted, I think.