Calico delegate breaks after multus cniVersion bumped to 1.1.0

[mihivagyok]

We're in the process of bringing up a new Openshift Version 4.23, and noticed, that Calico is emitting cniVersion 0.3.1 config while OpenShift upgraded the multus to 1.1.0. This causes multus to crash.

Expected Behavior

Calico emits CNI version 1.1.0 and multus can load primary CNI confuguration (calico)

Current Behavior

Multus crashes as it expects CNI version 1.1.0

2026-06-08T11:58:30Z [error] failed to create the configuration manager for the primary CNI plugin: failed to load the primary CNI configuration as a multus delegate with error 'delegate cni version is 0.3.1 while top level cni version is 1.1.0'

See the following code for reference:
https://github.com/openshift/cluster-network-operator/blob/6dc18040e7c214f6a1db25b6f5ef4642c6c6a186/bindata/network/multus/multus.yaml#L88

Possible Solution

Upgrade the supported CNI version to 1.1.0 in calico.

Currently, calico implicitly can support 1.0.0 but it is not exposed, so end user cannot set it.
https://calicousers.slack.com/archives/CPTH1KS00/p1780922229217789?thread_ts=1780921516.630419&cid=CPTH1KS00

Steps to Reproduce (for bugs)

1. Try installing Openshift 4.23 with Calico

Context

Openshift support is in danger as calico does not work with the next releases.

Your Environment

• Calico version: v3.30.7
• Calico dataplan: iptables, BGP
• Orchestrator version (e.g. kubernetes, openshift, etc.): Openshift
• Operating System and version: RHCOS
• Link to your project (optional): -

[fasaxc]

Looks like that openshift version isn't public yet; is there somewhere we can get a build to test with?

[TwoDCube]

@fasaxc https://amd64.ocp.releases.ci.openshift.org/releasestream/5-dev-preview/release/5.0.0-ec.3 should be publicly available to everyone with the standard OpenShift pull secret and it has the same issue