packages: Update cni and cni-plugin packages #2842
Merged
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.
Issue number:
Closes: #1745
Description of changes:
This updates the
cni
andcni-plugin
packages in Bottlerocket.Most of the time, the CNI plugins that are used are actually pulled down via EKS. There are some CNIs, and perhaps metal and vmware variants, where they need to use the locally installed CNI binaries. This gets those local binaries up to date with the binaries that end up getting pulled from EKS.
The
flannel
CNI plugin was deprecated and has since been removed. Thedummy
plugin has been introduced and can be used when chained with other CNIs for local routing.Testing done:
Testing in progress:
aws-k8s-1.24
for basic functionalityaws-k8s-*
variant and verify a more complex CNI like Cilium is functionalvmware-k8s-1.24
with ciliumTerms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.