[aws-vpc-cni] Add CNI config via a configmap #204
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
willejs
force-pushed
the
cni-add-configmap
branch
from
41ff883
to
0de7477
Compare
|
I am tracking the version release via this issue aws/amazon-vpc-cni-k8s#1084 |
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.
Description of changes:
This adds the ability to override the default cni config with your own file. This will enable you to utilize additional cni plugins such as the tuning plugin to set network namespaced sysctl values.
In this PR aws/amazon-vpc-cni-k8s#1069 and hopefully a subsequent release this feature will work.
I will add this to a comment against the flag once the release is cut and the docker container published, and before this is merged.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.