multus dynamic networks controller

The Multus Dynamic Networks Controller is a Kubernetes controller and is not run directly with docker run. It is deployed inside a Kubernetes cluster alongside Multus CNI, typically using the upstream deployment manifests. The DHI image replaces the default upstream image in the deployment.

Prerequisites

Before deploying the Multus Dynamic Networks Controller, ensure the following:

• A running Kubernetes cluster (v1.22 or later recommended)
• Multus CNI is installed and configured in the cluster
• At least one additional CNI plugin is available (for example, macvlan, bridge, or SR-IOV)
• NetworkAttachmentDefinition CRDs are installed (these are provided by Multus CNI)

Deploy with kubectl using the DHI image

1. Download the upstream deployment manifest:

curl -O https://raw.githubusercontent.com/k8snetworkplumbingwg/multus-dynamic-networks-controller/main/manifests/dynamic-networks-controller.yaml

1. Update the image reference in the manifest to use the DHI image:

sed -i 's|ghcr.io/k8snetworkplumbingwg/multus-dynamic-networks-controller:.*|registry.ghost-prod.alphabravo.io/ghost-base/multus-dynamic-networks-controller:0|' dynamic-networks-controller.yaml

1. Apply the manifest:

kubectl apply -f dynamic-networks-controller.yaml

Verify the deployment

kubectl get pods -n kube-system -l app=dynamic-networks-controller

Expected output:

NAME                                          READY   STATUS    RESTARTS   AGE
dynamic-networks-controller-<hash>            1/1     Running   0          60s

Run the container

To display help information:

docker run --rm registry.ghost-prod.alphabravo.io/ghost-base/multus-dynamic-networks-controller:0 --help

Common use cases

Hot-plug an additional network interface to a running pod

Once the controller is running, you can dynamically attach a new network interface to a running pod by updating its k8s.v1.cni.cncf.io/networks annotation.

1. First, ensure a NetworkAttachmentDefinition exists:

apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
  name: macvlan-conf
spec:
  config: '{
    "cniVersion": "0.3.1",
    "type": "macvlan",
    "master": "eth0",
    "mode": "bridge",
    "ipam": {
      "type": "host-local",
      "subnet": "10.10.0.0/16"
    }
  }'

1. Annotate a running pod to attach the network:

kubectl annotate pod <pod-name> k8s.v1.cni.cncf.io/networks='macvlan-conf' --overwrite

1. Remove the annotation to detach the interface:

kubectl annotate pod <pod-name> k8s.v1.cni.cncf.io/networks='' --overwrite

Using the -dev image variant

The -dev variant of the image (registry.ghost-prod.alphabravo.io/ghost-base/multus-dynamic-networks-controller:0-dev) includes a shell and common utilities, making it useful for debugging and troubleshooting. The dev image runs as root and includes bash, ca-certificates, coreutils, and findutils.

To inspect the controller binary or debug a running container, use Docker Debug with the runtime image:

docker debug <container-id>

To run the dev image locally and inspect its contents:

docker run --rm -it --entrypoint bash \
  registry.ghost-prod.alphabravo.io/ghost-base/multus-dynamic-networks-controller:0-dev

Non-hardened images vs. Ghost hardened images

Image variants

Ghost hardened images come in different variants depending on their intended use.

Available image tags for virt-controller:

Tag selection guidance:

• Use registry.ghost-prod.alphabravo.io/ghost-base/virt-controller:<version> for standard production deployments
• Use major version tags (like :<major>) for automatic minor updates (not recommended for production)

Runtime variants are designed to run your application in production. These images are intended to be used either directly or as the FROM image in the final stage of a multi-stage build. These images typically:

• Run as the nonroot user
• Do not include a shell or a package manager
• Contain only the minimal set of libraries needed to run the app

Build-time variants typically include dev in the variant name and are intended for use in the first stage of a multi-stage Dockerfile. These images typically:

• Run as the root user
• Include a shell and package manager
• Are used to build or compile applications

FIPS variants include fips in the variant name and tag. These variants use cryptographic modules that have been validated under FIPS 140, a U.S. government standard for secure cryptographic operations.

Runtime requirements specific to FIPS:

• FIPS mode restricts cryptographic operations to FIPS-validated algorithms
• Usage of non-compliant operations (like MD5) will fail
• Larger image size due to FIPS-validated cryptographic libraries

Migrate to a Ghost hardened image

To migrate your application to a Ghost hardened image, you must update your Dockerfile. At minimum, you must update the base image in your existing Dockerfile to a Ghost hardened image. This and a few other common changes are listed in the following table of migration notes:

The following steps outline the general migration process.

1. Find hardened images for your app.

   A hardened image may have several variants. Inspect the image tags and find the image variant that meets your needs.

2. Update the base image in your Dockerfile.

   Update the base image in your application's Dockerfile to the hardened image you found in the previous step. For framework images, this is typically going to be an image tagged as dev because it has the tools needed to install packages and dependencies.

3. For multi-stage Dockerfiles, update the runtime image in your Dockerfile.

   To ensure that your final image is as minimal as possible, you should use a multi-stage build. All stages in your Dockerfile should use a hardened image. While intermediary stages will typically use images tagged as dev, your final runtime stage should use a non-dev image variant.

4. Install additional packages

   Ghost hardened images contain minimal packages in order to reduce the potential attack surface. You may need to install additional packages in your Dockerfile. Inspect the image variants to identify which packages are already installed.

   Only images tagged as dev typically have package managers. You should use a multi-stage Dockerfile to install the packages. Install the packages in the build stage that uses a dev image. Then, if needed, copy any necessary artifacts to the runtime stage that uses a non-dev image.

   For Debian-based images, you can use apt-get to install packages.

Troubleshooting migration

General debugging

The hardened images intended for runtime don't contain a shell nor any tools for debugging. The recommended method for debugging applications built with Ghost hardened images is to use Docker Debug to attach to these containers. Docker Debug provides a shell, common debugging tools, and lets you install other tools in an ephemeral, writable layer that only exists during the debugging session.

Permissions

By default image variants intended for runtime, run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. You may need to copy files to different directories or change permissions so your application running as the nonroot user can access them.

Privileged ports

Non-dev hardened images run as a nonroot user by default. As a result, applications in these images can't bind to privileged ports (below 1024) when running in Kubernetes or in Docker Engine versions older than 20.10.

No shell

By default, image variants intended for runtime don't contain a shell. Use dev images in build stages to run shell commands and then copy any necessary artifacts into the runtime stage. In addition, use Docker Debug to debug containers with no shell.

Entry point

Ghost hardened images may have different entry points than images such as Docker Official Images. Use docker inspect to inspect entry points for Ghost hardened images and update your Dockerfile if necessary.