feat: Add support for updating additional pod IPv4 ranges for Standar…

…d and Autopilot clusters

Users can append more pod ranges by name to an existing cluster at the cluster level. When users or Node Auto-provisioning create new node pools, GKE will select the most available pod range and assign it to the node pool. These pod ranges can be removed once no node pool is using it.

PiperOrigin-RevId: 522620935

google/container/v1/cluster_service.proto

@@ -1502,6 +1502,13 @@ message IPAllocationPolicy {
   // Output only. [Output only] The services IPv6 CIDR block for the cluster.
   string services_ipv6_cidr_block = 23
       [(google.api.field_behavior) = OUTPUT_ONLY];
+
+  // Output only. [Output only] The additional pod ranges that are added to the
+  // cluster. These pod ranges can be used by new node pools to allocate pod IPs
+  // automatically. Once the range is removed it will not show up in
+  // IPAllocationPolicy.
+  AdditionalPodRangesConfig additional_pod_ranges_config = 24
+      [(google.api.field_behavior) = OUTPUT_ONLY];
 }
 
 // A Google Kubernetes Engine cluster.
@@ -2062,8 +2069,21 @@ message ClusterUpdate {
   // If a stack type is provided and does not match the current stack type of
   // the cluster, update will attempt to change the stack type to the new type.
   StackType desired_stack_type = 119;
+
+  // The additional pod ranges to be added to the cluster. These pod ranges
+  // can be used by node pools to allocate pod IPs.
+  AdditionalPodRangesConfig additional_pod_ranges_config = 120;
+
+  // The additional pod ranges that are to be removed from the cluster.
+  // The pod ranges specified here must have been specified earlier in the
+  // 'additional_pod_ranges_config' argument.
+  AdditionalPodRangesConfig removed_additional_pod_ranges_config = 121;
 }
 
+// AdditionalPodRangesConfig is the configuration for additional pod secondary
+// ranges supporting the ClusterUpdate message.
+message AdditionalPodRangesConfig {}
+
 // This operation resource represents operations that may have happened or are
 // happening on the cluster. All fields are output only.
 message Operation {