Revert "Have a constant to indicate Kubernetes pre-releases"#7818
Open
twz123 wants to merge 1 commit into
Open
Revert "Have a constant to indicate Kubernetes pre-releases"#7818twz123 wants to merge 1 commit into
twz123 wants to merge 1 commit into
Conversation
This reverts commit 0422dcb. As of Kubernetes 1.33, this is no longer necessary. The plus suffix is no longer appended. Not sure if this was entirely intentional, but it was a side effect of the implementation of KEP-4330. See: https://www.kubernetes.dev/resources/keps/4330/ Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
twz123
force-pushed
the
no-prerelease-marker
branch
from
bd981c2 to
3b90987
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This reverts PR #4229. As of Kubernetes 1.33, this is no longer necessary. The plus suffix is no longer appended. Not sure if this was entirely intentional, but it was a side effect of the implementation of KEP-4330.
Type of change
How Has This Been Tested?
Checklist