liveBook · Manning

Bridge plugin

As explained in Acing the Certified Kubernetes Administrator Exam, Second Edition

A bridge plugin is a container-networking plugin that creates or configures a software bridge for connecting container network interfaces.

A bridge plugin creates or configures a software bridge that connects container network interfaces. Kubernetes uses the plugin through the CNI to support Flannel networking, so the executable must be available in /opt/cni/bin/ on each node. section 6.5

Configure and verify the plugin with these operational steps:

  • Download and extract the CNI plugins, then move the bridge executable to /opt/cni/bin/. section 6.5
  • Apply the Flannel manifest after installing the plugin on every node. section 6.5

Install the bridge executable

Inside each kind node, extract cni-plugins-linux-amd64-v1.7.1.tgz and run mv bridge /opt/cni/bin/. Then apply the Flannel manifest from the control-plane shell. section 6.5

How Acing the Certified Kubernetes Administrator Exam, Second Edition covers it

How deep it goes
Traces downloading, extracting, placing, and verifying the plugin, but does not explain bridge implementation internals.
Examples
Uses kind node shells, a CNI plugin archive, /opt/cni/bin/, Flannel objects, and kubectl readiness checks.
What it assumes
Assumes shell access, apt, wget, tar, file movement, and basic kubectl use for node and pod verification.
What you can do after
Operate/configure a bridge CNI plugin and verify Flannel networking readiness in a kind cluster.
How it connects
Connects CNI, Flannel, container networking, and encapsulated packets between Kubernetes nodes.

This explainer was generated by Manning's knowledge graph from the text of Acing the Certified Kubernetes Administrator Exam, Second Edition. The section links point to the parts of the book it draws on.