Bump Kubernetes to v1.16.13 #68
Merged
Conversation
This file contains 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
Due to some versioning issues, the version that is currently use for `runc` has been rebuilt, which causes a new checksum. Info: > NOTE: For those who are confused by the massive version jump (rc10 > to rc91), this was done to avoid issues with SemVer and lexical > comparisons -- there haven't been 90 other release candidates. Please > also note that runc 1.0.0-rc90 is identical to 1.0.0-rc10. See #2399 > for more details. See more here: opencontainers/runc#2399
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When I upgraded one of my clusters that were utilizing
flannelto 1.16.7 which is the latest KTRW, I hit this issue:kubernetes/kubernetes#92035
We use a temporary fix on our worker nodes. This real fix has been backported to a later 1.16 version, so I'd be great with this bump. I'd love this "fixed" for the cluster before I proceed to bumping to 1.17.
I figured we could create the patch release
v1.2.1with this commit included. If you agree, do you think that the other commit sincev1.2.0(98aac40) should be included too?