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

I used to trigger a VPC native cluster with:
```        ipAllocationPolicy: {
          useIpAliases: true, //  creates the cluster with Alias IP addresses
          createSubnetwork: true, // enables ip aliasing
        },```
but this config was removed.  I used an explicit network/subnetwork passed to my cluster, but it does not trigger creation of a VPC native cluster.  What could I be missing there <@UDEJ1F5SQ>?

This old config is still referenced by the gcp docs <https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips>

Same here <https://github.com/terraform-providers/terraform-provider-google/blob/master/website/docs/r/container_cluster.html.markdown>

I’m fundamentally mimicking the guide <https://github.com/pulumi/kubernetes-guides/blob/master/gcp/03-cluster-configuration/index.ts>

I’m trying with the `ipAllocationPolicy` block defined now:
```        ipAllocationPolicy: {
          // use_ip_aliases defaults to true if the ip_allocation_policy block is defined
        },```
Found that in a terraform issue

That appears to work, not done creating yet but it does say alias IP enabled in the console

And did the `location` setting work for you?

yes, that triggered VPC native (ip aliasing enabled)

`location` still doesn’t work for zone only.  I’m going to circle back to it once I have some other issues ironed out