Skip to content

[release-v1.43] Add cni-plugins init container to calico-node DaemonSet#4935

Open
caseydavenport wants to merge 1 commit into
tigera:release-v1.43from
caseydavenport:casey-cni-plugins-v1.43
Open

[release-v1.43] Add cni-plugins init container to calico-node DaemonSet#4935
caseydavenport wants to merge 1 commit into
tigera:release-v1.43from
caseydavenport:casey-cni-plugins-v1.43

Conversation

@caseydavenport

Copy link
Copy Markdown
Member

Backport of #4819 to release-v1.43.

Pairs with the new third-party-cni-plugins image. After the mono-image consolidation, calico/calico no longer ships the upstream CNI plugin binaries baked into /opt/cni/bin, so on platforms that don't pre-populate the host CNI bin dir, install-cni finds nothing to copy and pods depending on host-local, portmap, loopback, tuning, or flannel break.

This adds a cni-plugins init container ahead of install-cni that copies the binaries into a shared emptyDir, which install-cni mounts at /opt/cni/bin. CNI.InstallMode defaults to All; set it to CalicoOnly on hosts that already provide the upstream plugins to skip the init container.

Note: the init container image still needs promoting to quay.io before default installs can pull it.

NONE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants