[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",35095401,"digest","sha256:f7f9fba1a0b68f7bd001deafa194aa91e6296f272f64e79d877d36bbbc6cadc7","full_size",7947,"id",916960337,"images",[],"last_updated","2025-06-14T06:04:44.301935Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-2abed0c33357c7d4485f20c1bcafe9e2b86225c5ca72c495dc8d09fbae04e029","repository",19482526,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Networking","slug","networking","content_types",[78,32],"helm","date_registered","2023-03-14T13:21:54.985869Z","description","Bitnami Helm chart for Multus CNI","is_private","2025-08-14T18:51:41.58733Z","last_modified","2026-03-16T14:24:43.272993Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","multus-cni","namespace","bitnamicharts","pull_count",630695,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Multus CNI\n\nMultus is a CNI plugin for Kubernetes clusters. Written in Go, features adding multiple network interfaces to pods.\n\n[Overview of Multus CNI](https://github.com/k8snetworkplumbingwg/multus-cni)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/multus-cni\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [Multus CNI](https://github.com/bitnami/containers/tree/main/bitnami/multus-cni) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n- ReadWriteMany volumes for deployment scaling\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/multus-cni\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys Multus CNI on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Host configuration\n\nOnce installed, the helm chart will modify configuration files in the host nodes of the Kubernetes cluster. Ensure that the cluster allows root and privileged deployments.\n\nOnce the multus-cni configuration is installed, check the [upstream Kubernetes documentation](https://kubernetes.io/docs/concepts/cluster-administration/networking/) on how to modify the network settings of the cluster.\n\n> **Important**: Double check that the host CNI binary and configuration directories are properly configured, or the deployment will fail. This is done using the `hostCNINetDir` and `hostCNIBinDir` values.\n\n### Image\n\nThe `image` parameter allows specifying which image will be pulled for the chart.\n\n#### Private registry\n\nIf you configure the `image` value to one in a private registry, you will need to [specify an image pull secret](https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod).\n\n1. Manually create image pull secret(s) in the namespace. See [this YAML example reference](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config). Consult your image registry's documentation about getting the appropriate secret.\n2. Note that the `imagePullSecrets` configuration value cannot currently be passed to helm using the `--set` parameter, so you must supply these using a `values.yaml` file, such as:\n\n ```yaml\n imagePullSecrets:\n - name: SECRET_NAME\n ```\n\n3. Install the chart\n\n### Setting Pod's affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | -------------------------------------------------------------------------------------------------------------- | -------------- |\n| `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `\"\"` |\n| `nameOverride` | String to partially override multus-cni.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override multus-cni.fullname template | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `commonAnnotations` | Common annotations to add to all Multus CNI resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `commonLabels` | Common labels to add to all Multus CNI resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release (evaluated as a template). | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployment | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment | `[\"infinity\"]` |\n\n### Multus CNI parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |\n| `image.registry` | Multus CNI image registry | `REGISTRY_NAME` |\n| `image.repository` | Multus CNI Image name | `REPOSITORY_NAME/multus-cni` |\n| `image.digest` | Multus CNI image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | Multus CNI image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `image.debug` | Specify if debug logs should be enabled | `false` |\n| `hostCNIBinDir` | CNI binary dir in the host machine to mount | `/opt/cni/bin` |\n| `hostCNINetDir` | CNI net.d dir in the host machine to mount | `/etc/cni/net.d` |\n| `CNIMountPath` | Path inside the container to mount the CNI dirs | `/bitnami/multus-cni/host` |\n| `command` | Override default container command (useful when using custom images) | `[]` |\n| `args` | Override default container args (useful when using custom images) | `[]` |\n| `updateStrategy.type` | Update strategy - only really applicable for deployments with RWO PVs attached | `RollingUpdate` |\n| `priorityClassName` | Multus CNI pods' priorityClassName | `\"\"` |\n| `schedulerName` | Name of the k8s scheduler (other than default) | `\"\"` |\n| `runtimeClassName` | Name of the runtime class to be used by pod(s) | `\"\"` |\n| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `true` |\n| `hostAliases` | Add deployment host aliases | `[]` |\n| `extraEnvVars` | Extra environment variables | `[]` |\n| `extraEnvVarsCM` | ConfigMap containing extra env vars | `\"\"` |\n| `extraEnvVarsSecret` | Secret containing extra env vars (in case of sensitive data) | `\"\"` |\n| `extraVolumes` | Array of extra volumes to be added to the deployment (evaluated as template). Requires setting `extraVolumeMounts` | `[]` |\n| `extraVolumeMounts` | Array of extra volume mounts to be added to the container (evaluated as template). Normally used with `extraVolumes`. | `[]` |\n| `initContainers` | Add additional init containers to the pod (evaluated as a template) | `[]` |\n| `sidecars` | Attach additional containers to the pod (evaluated as a template) | `[]` |\n| `tolerations` | Tolerations for pod assignment | `[]` |\n| `networkPolicy.enabled` | Specifies whether a NetworkPolicy should be created | `true` |\n| `networkPolicy.kubeAPIServerPorts` | List of possible endpoints to kube-apiserver (limit to your cluster settings to increase security) | `[]` |\n| `networkPolicy.allowExternal` | Don't require server label for connections | `true` |\n| `networkPolicy.allowExternalEgress` | Allow the pod to access any range of port and all destinations. | `true` |\n| `networkPolicy.extraIngress` | Add extra ingress rules to the NetworkPolicy | `[]` |\n| `networkPolicy.extraEgress` | Add extra ingress rules to the NetworkPolicy | `[]` |\n| `podAffinityPreset` | Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `\"\"` |\n| `podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |\n| `nodeAffinityPreset.type` | Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `\"\"` |\n| `nodeAffinityPreset.key` | Node label key to match Ignored if `affinity` is set. | `\"\"` |\n| `nodeAffinityPreset.values` | Node label values to match. Ignored if `affinity` is set. | `[]` |\n| `affinity` | Affinity for pod assignment \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-multus-cni-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",3380195,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/multus-cni:sha256-2abed0c33357c7d4485f20c1bcafe9e2b86225c5ca72c495dc8d09fbae04e029