Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The announcement lists supported CPU node families, including Axion, and Cloud TPU v6e. Check versions, hardware, and preview configuration separately in the intended location.
- The setup guide lists 1.37.1-gke.3020000 as the minimum. Rapid release notes mark that specific patch deprecated. Check currently available versions before creating a cluster.
- Internal IPv6 subnets can reach Google APIs and Artifact Registry over IPv6. Public IPv4-only destinations require DNS64 and NAT64.
- Existing IPv4 and dual-stack clusters need a separate single-stack cluster and a blue-green migration. Use supported Gateway API classes for Layer 7 ingress.
Check the location, worker type, and version
Google lists single-stack IPv6 as Preview for specified CPU families, including Axion, and Cloud TPU v6e. Check the versions offered in the location, then confirm the required machine capacity, quota, and cluster options. The TPU availability list establishes hardware locations.
The setup guide requires GKE 1.37.1-gke.3020000 or later. The November 10 Rapid notes mark that exact patch deprecated. Query your location with gcloud container get-server-config --location=COMPUTE_LOCATION and inspect validVersions for the selected release channel. Verify the feature configuration separately.
Verify VPC, DNS, and control-plane connectivity
Google documents new Standard and Autopilot clusters. They require VPC-native networking, Dataplane V2, a custom-mode VPC, Cloud DNS, and single-stack IPv6 worker nodes. Nodes and Pods reach the control plane via Private Service Connect using an INTERNAL IPv6 subnetwork.
Choose INTERNAL or EXTERNAL IPv6 for the node subnet. Review the VPC's internal IPv6 setup, control-plane connectivity, and worker egress separately. The control plane still requires its INTERNAL subnet when the node subnet uses EXTERNAL IPv6.
Test public IPv4 and IPv6 egress and application ingress
An INTERNAL IPv6 node subnet can reach Google APIs and Artifact Registry over IPv6. For public IPv4-only names, configure DNS64 and regional NAT64. Check for hardcoded IPv4 addresses because IP literals bypass DNS64 synthesis.
INTERNAL ULA addresses cannot directly reach public IPv6 endpoints outside Google. Cloud NAT does not offer NAT66. For public IPv6 connectivity, check the EXTERNAL subnet, VPC firewall policy, and ingress design.
Use a supported Gateway API class for Layer 7 ingress. Check the client and backend address types supported by the class. GKE Ingress is unsupported. Test the chosen entry point from IPv4 and IPv6 clients and verify the results against the IPv6 backend.
Use a blue-green migration for existing workloads
Create the new single-stack IPv6 cluster alongside the existing IPv4 or dual-stack cluster. Start with representative services and test image pulls, Google APIs, IPv4-only third-party names, and metadata DNS before shifting traffic.
Keep the old cluster available for rollback. Record expected resolution, connectivity, and errors, then use the same checks on both clusters. For an existing cluster's data-plane upgrade, see the Dataplane V2 in-place migration guide.
Sources
Frequently Asked Questions
Can I migrate by adding an IPv6-only node pool to an existing dual-stack cluster?
Google documents a separate single-stack IPv6 cluster. Deploy and validate it alongside the existing cluster, then shift workloads gradually.
Should I use the minimum GKE version shown in the setup guide?
Check current versions for your location and release channel first. The setup guide defines the minimum, and the Rapid notes mark that specific patch deprecated.
Can an IPv6 Pod on a private subnet pull from an IPv4-only registry?
For an external IPv4-only hostname, use DNS64 and NAT64, then validate name resolution and pulls from a Pod. Check for literal IPv4 addresses in registry configuration.