crc-nad-dynamic-plugin-config

CRC NAD Console Plugin Deployment

Deploy the nad-console-plugin — a pre-built OpenShift Console Dynamic Plugin that sets the KUBEVIRT_DYNAMIC flag when the NetworkAttachmentDefinition CRD exists, causing the built-in networking-console-plugin to show the NAD nav item natively.

Background

The networking-console-plugin (built into OCP 4.21+) already has a full NAD UI (list, create, details) but gates it behind two flags:

• NET_ATTACH_DEF — always true (hardcoded in networking-console-plugin)
• KUBEVIRT_DYNAMIC — normally set by the KubeVirt plugin, absent in CRC

This plugin sets KUBEVIRT_DYNAMIC=true via a console.flag/model extension (7 lines of JSON, no custom JS code) whenever the NetworkAttachmentDefinition CRD is present in the cluster.

Prerequisites

• CRC cluster is running (crc status shows Running)
• oc is logged in as kubeadmin
• Helm v3 is available — use ~/.local/bin/helm (v3.21.0)
  • Verify: ~/.local/bin/helm version
• The nad-console-plugin project is at ~/app/playground/nad-console-plugin/
• Pre-built image: quay.io/rhtevan/nad-console-plugin:latest

Step 1: Verify the NAD CRD Is Present

The plugin only activates its flag when this CRD exists. Confirm it's in the cluster:

oc get crd network-attachment-definitions.k8s.cni.cncf.io

Expected: The CRD is present (it's part of CRC's default Multus CNI setup).

Step 2: Deploy with Helm

~/.local/bin/helm upgrade -i nad-console-plugin \
  ~/app/playground/nad-console-plugin/charts/openshift-console-plugin \
  -n nad-console-plugin \
  --create-namespace \
  --set plugin.image=quay.io/rhtevan/nad-console-plugin:latest \
  --set plugin.name=nad-console-plugin \
  --set plugin.imagePullPolicy=Always

imagePullPolicy=Always ensures Kubernetes always pulls the latest image rather than using a cached version.

Step 3: Verify Pods Are Running

oc get pods -n nad-console-plugin

Expected: At least one pod in Running state serving the plugin.