This repository was archived by the owner on Nov 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
feat: add etags for cluster and node pool update operations #325
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…llow clusters to be created as dual stack or toggled between IPV4 and dual stack 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 Source-Link: googleapis/googleapis@9d1290e Source-Link: https://github.com/googleapis/googleapis-gen/commit/31ed74bbd1990351a87bda1a4570ba08374281b7 Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMzFlZDc0YmJkMTk5MDM1MWE4N2JkYTFhNDU3MGJhMDgzNzQyODFiNyJ9
No region tags are edited in this PR.This comment is generated by snippet-bot.
|
--- feat: add EphemeralStorageLocalSsdConfig and LocalNvmeSsdBlockConfig APIs to v1alpha1, v1beta1, v1 PiperOrigin-RevId: 497251971 Source-Link: googleapis/googleapis@32fa620 Source-Link: https://github.com/googleapis/googleapis-gen/commit/487ef77445b24f0c00952ca302149bf4d241b908 Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNDg3ZWY3NzQ0NWIyNGYwYzAwOTUyY2EzMDIxNDliZjRkMjQxYjkwOCJ9
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 Source-Link: googleapis/googleapis@9a294bf Source-Link: https://github.com/googleapis/googleapis-gen/commit/f0f0e1ffc3e28e203e7c233af4936688c9b2b07f Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZjBmMGUxZmZjM2UyOGUyMDNlN2MyMzNhZjQ5MzY2ODhjOWIyYjA3ZiJ9
parthea
approved these changes
Jan 5, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
api: container
Issues related to the googleapis/python-container API.
owl-bot-copy
size: l
Pull request size is large.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Source-Link: googleapis/googleapis@9a294bf
Source-Link: https://github.com/googleapis/googleapis-gen/commit/f0f0e1ffc3e28e203e7c233af4936688c9b2b07f
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZjBmMGUxZmZjM2UyOGUyMDNlN2MyMzNhZjQ5MzY2ODhjOWIyYjA3ZiJ9
BEGIN_COMMIT_OVERRIDE
feat: add etags for cluster and node pool update operations
feat: Release GKE CloudDNS Cluster Scope
feat: CLUSTER_SCOPE option now available in DNSScope
feat: add WindowsNodeConfig field
feat: add EphemeralStorageLocalSsdConfig and LocalNvmeSsdBlockConfig APIs
feat: Add support for specifying stack type for clusters
END_COMMIT_OVERRIDE
feat: Add support for specifying stack type for clusters. This will allow clusters to be created as dual stack or toggled between IPV4 and dual stack.
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.