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
---
feat: add etags for cluster and node pool update operations
Clients may now optionally specify the previously read etag for a cluster or node pool during update requests. The etag is regenerated every time the object is updated. If an etag is provided, it will be checked against the current etag, and the request will be rejected on mismatch. This is particularly useful for allowing two clients to concurrently update a repeated field without overwriting each other.
PiperOrigin-RevId: 500787735
Clients may now optionally specify the previously read etag for a cluster or node pool during update requests. The etag is regenerated every time the object is updated. If an etag is provided, it will be checked against the current etag, and the request will be rejected on mismatch. This is particularly useful for allowing two clients to concurrently update a repeated field without overwriting each other.
PiperOrigin-RevId: 498249600
`CLUSTER_SCOPE` option now available in DNSScope
---
feat: add WindowsNodeConfig field to v1alpha1, v1beta1, v1
---
feat: add EphemeralStorageLocalSsdConfig and LocalNvmeSsdBlockConfig APIs to v1alpha1, v1beta1, v1
PiperOrigin-RevId: 497252854
Clients can now configure dual stack clusters by specifying a stack type of IPV4_IPV6 during cluster creation, or with an update command. When used with a cluster creation command that creates a new subnet, the ipv6_access_type field can be used to specify whether the subnet has internal or external IPv6 access. When used with a cluster update command, the subnet must already be dual stack.
PiperOrigin-RevId: 495981345
Clients can now configure dual stack clusters by specifying a stack type of IPV4_IPV6 during cluster creation, or with an update command. When used with a cluster creation command that creates a new subnet, the ipv6_access_type field can be used to specify whether the subnet has internal or external IPv6 access. When used with a cluster update command, the subnet must already be dual stack.
PiperOrigin-RevId: 495438580
chore: disallow "transport=rest" for services where numeric enums are not confirmed to be supported (except in PHP and Java)
PiperOrigin-RevId: 493113566
Use a compact placement policy to specify that nodes within the node pool should be placed in closer physical proximity to each other within a zone. Having nodes closer to each other can reduce network latency between nodes, which can be useful for tightly-coupled batch workloads.
PiperOrigin-RevId: 488490422
---
feat: GKE cluster's control plan/node-pool network isolation
Users now can change the network isolation for your public cluster's control plane.
By default, when a new public cluster is created, GKE assigns a public IP address (external endpoint) to the control plane and provisions
public nodes. New APIs allows to change cluster network isolation of the control plane and/or node-pool from the internet
---
feat: add nodeconfig resource_labels api
---
feat: add API to enable GKE Gateway controller
PiperOrigin-RevId: 486164478
---
feat: GKE cluster's control plan/node-pool network isolation
Users now can change the network isolation for your public cluster's control plane.
By default, when a new public cluster is created, GKE assigns a public IP address (external endpoint) to the control plane and provisions
public nodes. New APIs allows to change cluster network isolation of the control plane and/or node-pool from the internet
---
feat: add nodeconfig resource_labels api
---
feat: add API to enable GKE Gateway controller
PiperOrigin-RevId: 486164143
