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

One place to start would be here: <https://www.pulumi.com/docs/using-pulumi/adopting-pulumi/import/>

The next place would be looking at the API docs for the specific resources you want to import; they’ll provide more details. For example, GKE is here: <https://www.pulumi.com/registry/packages/gcp/api-docs/container/cluster/>

There’s an “Import” section at the bottom that provides some example usage of `pulumi import` with that specific resource.

Hope this helps!

Hi Scott, I looked at the pulumi import but it’s all taking about aws

The docs for `pulumi import` use AWS resources as examples, true. However, the concepts behind _how_ to use the `pulumi import` command are there, and when you review the second link I posted you can see specific examples of how to use `pulumi import` with GCP resources, like GKE (look in the “Import” section at the bottom of the second link).

Note that when you import an autopilot cluster, the definition will contain more details than pulumi will actually allow when you run `pulumi preview`. I’ve managed to import one by running the import command in the GKE cluster docs and then cutting things out of the definition until `pulumi preview`  no longer complained. Bit of a messy process

<@U05CTH3GRB4> Good point about Autopilot; if that’s enabled, a lot of other settings can’t be specified and will produce an error.

And another note on autopilot clusters - I don’t think it’s currently possible to create them using pulumi (not enirely sure but I didn’t succeed) . Can import them and then manage them, though.

Hmm…that should be possible, unless there’s something of which I’m not aware.

<@UJBNC99MF> Sorry, missed the response - it’s been a few days but from memory, creating the bare minimum cluster definition and adding the autopilot directive to it complains that it requires a node pool max setting, but setting it complains that you can’t change that setting on autopilot clusters.

Interesting! Have you filed an issue on that behavior? (If you haven’t and you can, that would be very helpful.)

<@U05CTH3GRB4> so is there a way that I can achieve it? Probably using pulumi import and then use these variables to create a new cluster?

<@U05DK0B4YBY> That’s what I did - created an autopilot cluster, imported it and then removed a lot of stuff from the resultant output until pulumi preview worked, as per my previous comment.

<@U05CTH3GRB4> Great! When you run pulumi import, Did VPC was imported successfully with NAT and subnet?

I’ll defer to <@U05CTH3GRB4> for his experience, but I suspect that importing a cluster did not also import associated resources like networks and subnets. You’ll most likely need to import those separately.

Ah! Ok <@UJBNC99MF> Any guidance / tutorial links for that particularly fir GCP?

You can use the same `pulumi import` command to import _any_ supported resource, including GCP Networks and GCP Subnets. At the bottom of each page for a supported resource, you’ll find an example `pulumi import` command. (By “page for a supported resource,” I’m referring to the API documentation pages like <https://www.pulumi.com/registry/packages/gcp/api-docs/compute/network/|this one>)