feat: add support for HostMaintenancePolicy
feat: add support for AdditionalPodNetworkConfig and AdditionalNodeNetworkConfig
feat: add enable_multi_networking to NetworkConfig
PiperOrigin-RevId: 550168784
--
feat: add a Pod IP Utilization API
Users can use `cluster describe` command to check the Pod IP ranges utilizations consumed by all the node pools within the same cluster. This percentage can be seen at cluster default Pod range, additional Pod ranges, and node pool level Pod ranges.
PiperOrigin-RevId: 547521835
A new optional field `InsecureKubeletReadonlyPortEnabled` is available in
`NodeKubeletConfig` and `AutoProvisioningNodePoolDefaults`.
Setting the field to `false` turns off the read-only port.
If un-set, the default for the GKE version is used.
---
feat: publicize tpu topology in beta API
---
feat: add a Pod IP Utilization API
Users can use `cluster describe` command to check the Pod IP ranges utilizations consumed by all the node pools within the same cluster. This percentage can be seen at cluster default Pod range, additional Pod ranges, and node pool level Pod ranges.
PiperOrigin-RevId: 545172252
---
feat: add SecurityPostureConfig API field to allow customers to enable GKE Security Posture capabilities for their clusters
---
feat: add workloadPolicyConfig API field to allow customer enable NET_ADMIN capability for their autopilot clusters
PiperOrigin-RevId: 539136563
---
feat: add SecurityPostureConfig API field to allow customers to enable GKE Security Posture capabilities for their clusters
---
feat: add workloadPolicyConfig API field to allow customer enable NET_ADMIN capability for their autopilot clusters
PiperOrigin-RevId: 538770734
---
feat: turn on public visibility for best effort provision
---
feat: add CheckAutopilotCompatibility API to get autopilot compatibility issues for a given standard cluster
PiperOrigin-RevId: 537987027
---
feat: turn on public visibility for best effort provision
---
feat: add CheckAutopilotCompatibility API to get autopilot compatibility issues for a given standard cluster
PiperOrigin-RevId: 537883922
If release channel is left unspecified on cluster creation and a version is specified, the cluster is now enrolled in the most mature release channel where the version is available (first checking STABLE, then REGULAR, and finally RAPID) instead of being enrolled in STATIC. This only affects clusters with node auto upgrades enabled and no explicit node version specified. To ensure new clusters are enrolled in static, explicitly specify that the cluster should not be enrolled in a channel.
PiperOrigin-RevId: 532773462
If release channel is left unspecified on cluster creation and a version is specified, the cluster is now enrolled in the most mature release channel where the version is available (first checking STABLE, then REGULAR, and finally RAPID) instead of being enrolled in STATIC. This only affects clusters with node auto upgrades enabled and no explicit node version specified. To ensure new clusters are enrolled in static, explicitly specify that the cluster should not be enrolled in a channel.
PiperOrigin-RevId: 532773421
docs: Operation.self_link and Operation.target_link given examples
feat: Cluster resizes will now have their own operation type (RESIZE_CLUSTER) instead of reusing REPAIR_CLUSTER; they will start using this in the near future
PiperOrigin-RevId: 526970355
docs: Operation.self_link and Operation.target_link given examples
feat: Cluster resizes will now have their own operation type (RESIZE_CLUSTER) instead of reusing REPAIR_CLUSTER; they will start using this in the near future
PiperOrigin-RevId: 526025502
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
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: 522620905
