Skip to content

Commit 852d55a

Browse files
feat: Add support for updating additional pod IPv4 ranges for Standard and Autopilot clusters (#6043)
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 Source-Link: googleapis/googleapis@2ddfcb8 Source-Link: googleapis/googleapis-gen@8c7eccd Copy-Tag: eyJwIjoiQ29udGFpbmVyLy5Pd2xCb3QueWFtbCIsImgiOiI4YzdlY2NkMDk3Yjc5ODlkNzJjYWU5NTVmYWY1ZWQ4ZTNmZGNiYzc1In0=
1 parent c9538ed commit 852d55a

4 files changed

Lines changed: 190 additions & 0 deletions

File tree

301 Bytes
Binary file not shown.

‎Container/src/V1/AdditionalPodRangesConfig.php‎

Lines changed: 34 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎Container/src/V1/ClusterUpdate.php‎

Lines changed: 100 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎Container/src/V1/IPAllocationPolicy.php‎

Lines changed: 56 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)