Skip to content

update unbounded cni to v0.7.0#50

Merged
bcho merged 1 commit intomainfrom
update-unbounded-cni
Mar 11, 2026
Merged

update unbounded cni to v0.7.0#50
bcho merged 1 commit intomainfrom
update-unbounded-cni

Conversation

@anson627
Copy link
Contributor

This pull request updates the Unbounded CNI deployment manifests from version 0.5.3 to 0.7.0 and removes the FRR (Free Range Routing) sidecar and related configuration from the node DaemonSet. The changes simplify the deployment by eliminating FRR-specific containers, configuration files, and associated Prometheus metrics, while also updating image references and asset folder naming.

Major changes include:

Removal of FRR Support from Node Deployment

  • Removed FRR and FRR-exporter containers, their volume mounts, and associated volumes from the node/03-daemonset.yaml manifest, eliminating all FRR-specific configuration and metrics from the node deployment. [1] [2] [3] [4]
  • Deleted the FRR ConfigMap (00-frr-configmap.yaml), removing all FRR daemon and config file definitions from the deployment assets.

Image and Version Updates

  • Updated all container image references in the controller and node manifests from version v0.5.3 to v0.7.0 to use the latest Unbounded CNI images. [1] [2] [3]
  • Changed the asset folder name and reference from unbounded-cni-0.5.3 to unbounded-cni to reflect the new version and simplify future updates.

Prometheus and Configuration Adjustments

  • Removed FRR-specific Prometheus annotations from the node DaemonSet, so only the main node metrics are scraped.
  • Removed the frrVtyshPath configuration parameter from the main ConfigMap, since FRR is no longer used.

These changes streamline the deployment by removing FRR dependencies and updating the manifests to the latest Unbounded CNI version.

@bcho bcho merged commit 164a90e into main Mar 11, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants