GCPMachinePool lacks Alias IP support
kind/buglifecycle/rotten
/kind bug
**What steps did you take and what happened:**
1. Trying to use the CAPI GCP controller to spin up a kubernetes cluster with native routing enabled.
2. Using this unmerged fork: https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1506
**What did you expect to happen:**
1. Expected the GCPMachinePool CRD to support spec.AliasIPs to allow assigning secondary subnets to Managed Instance Groups in the backend as aliasIPs for native routing.
2. But it seems that the GCPMachinePool spec have aliasIps commented out https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/81fd414960c28f46a4a6c8af83eb0033174874fa/exp/api/v1beta1/gcpmachinepool_types.go#L51
3. The CRD does not have support to add in AliasIPs so there is no way to have a GCPMachinePool resource accept it in spec.
4. AliasIPRanges is currently passed along as an emptyslice to `instance.NetworkInterfaces` as well [here](https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/81fd414960c28f46a4a6c8af83eb0033174874fa/cloud/scope/machinepool.go#L345-L346).
**Anything else you would like to add:**
Can you please add GCPMachinePool to have support to allocate AliasIPs to underlying MIGs.
**Environment:**
- Cluster-api version: This fork https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1506
- Minikube/KIND version: v1.26.15 and above
- Kubernetes version: (use `kubectl version`):
- OS (e.g. from `/etc/os-release`): Ubuntu-20-04
关闭于 2026-04-24 4 条评论