update(aws-k8s-cni): move from 1.3.0 -> 1.4.1 #134
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
metral
force-pushed
the
metral/update-aws-cni
branch
from
dcc0b5a
to
e8d9b72
Compare
|
This was tested on an existing cluster using |
metral
force-pushed
the
metral/update-aws-cni
branch
from
e8d9b72
to
1c1dca3
Compare
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.
Based on: https://git.io/fj8fD
This bumps the version of CNI used (v1.3.0 was 6+ months old).
We should look to bump to v1.5.0 when possible, as it includes a fix that aims to improve ENI Pod IP + CNI management, and failure + retry logic - both seem like welcomed additions, in the face of a week with an uptick in service timeouts. (Update: being tracked in #135)