docs: [container] clarified release channel defaulting behavior for create cluster requests when release channel is unspecified #9441
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
…r requests when release channel is unspecified 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 Source-Link: googleapis/googleapis@633d3c1 Source-Link: https://github.com/googleapis/googleapis-gen/commit/f779f562476199d1f02156ac28f97ec9e37067eb Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImY3NzlmNTYyNDc2MTk5ZDFmMDIxNTZhYzI4Zjk3ZWM5ZTM3MDY3ZWIifQ==
No region tags are edited in this PR.This comment is generated by snippet-bot.
|
…r requests when release channel is unspecified 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 Source-Link: googleapis/googleapis@aeae5ea Source-Link: https://github.com/googleapis/googleapis-gen/commit/d4d433d4eaa8b4d780f83062bf1a81d04646ea41 Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImQ0ZDQzM2Q0ZWFhOGI0ZDc4MGY4MzA2MmJmMWE4MWQwNDY0NmVhNDEifQ==
mpeddada1
approved these changes
May 22, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
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
Source-Link: googleapis/googleapis@aeae5ea
Source-Link: https://github.com/googleapis/googleapis-gen/commit/d4d433d4eaa8b4d780f83062bf1a81d04646ea41
Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImQ0ZDQzM2Q0ZWFhOGI0ZDc4MGY4MzA2MmJmMWE4MWQwNDY0NmVhNDEifQ==
BEGIN_NESTED_COMMIT
docs: [container] clarified release channel defaulting behavior for create cluster requests when release channel is unspecified
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
Source-Link: googleapis/googleapis@633d3c1
Source-Link: https://github.com/googleapis/googleapis-gen/commit/f779f562476199d1f02156ac28f97ec9e37067eb
Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImY3NzlmNTYyNDc2MTk5ZDFmMDIxNTZhYzI4Zjk3ZWM5ZTM3MDY3ZWIifQ==
END_NESTED_COMMIT