# Bitnami Secure Images Helm chart for MetalLB MetalLB is a load-balancer implementation for bare metal Kubernetes clusters, using standard routing protocols. [Overview of MetalLB](https://metallb.universe.tf/) Trademarks: 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. ## TL;DR ```console helm install my-release oci://registry-1.docker.io/bitnamicharts/metallb ``` ## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? - Hardened secure images of popular open source software with Near-Zero Vulnerabilities - Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores - Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM) - Software supply chain provenance attestation through in-toto - First class support for the internet’s favorite Helm charts Each image comes with valuable security metadata. You can view the metadata in [our public catalog here](https://app-catalog.vmware.com/bitnami/apps). Note: Some data is only available with [commercial subscriptions to BSI](https://bitnami.com/).   If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy). ## Introduction Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads. This chart bootstraps a [MetalLB Controller](https://metallb.universe.tf/community/) Controller Deployment and a [MetalLB Speaker](https://metallb.universe.tf/community/) Daemonset on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. ## Prerequisites - Kubernetes 1.23+ - Helm 3.8.0+ - Virtual IPs for Layer 2 or Route Reflector for BGP setup. ## Installing the Chart To install the chart with the release name `my-release`: ```console helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/metallb ``` > 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`. These commands deploy metallb on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation. > **Tip**: List all releases using `helm list` ## Configuration and installation details ### Resource requests and limits Bitnami 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. To 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/). ### Prometheus metrics This chart can be integrated with Prometheus by setting `*.metrics.enabled` (under the `controller`, `speaker` and `speaker.frr` sections) to true. This will expose the MetalLB native Prometheus port in both the containers and services. The services will also have the necessary annotations to be automatically scraped by Prometheus. #### Prometheus requirements It is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster. #### Integration with Prometheus Operator The chart can deploy `ServiceMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `*.metrics.serviceMonitor.enabled=true` (under the `controller`, `speaker` and `speaker.frr` sections). Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error: ```text no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1" ``` Install the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator. ### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html) It 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. Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. To configure [MetalLB](https://metallb.universe.tf) please look into the configuration section [MetalLB Configuration](https://metallb.universe.tf/configuration/). ### Backup and restore To 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/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-backup-restore-deployments-velero-index.html). ### Example IP addresses to assing to the LoadBalancer configuration ```yaml # The address-pools lists the IP addresses that MetalLB is # allowed to allocate. You can have as many # address pools as you want. apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: # A name for the address pool. Services can request allocation # from a specific address pool using this name. name: first-pool namespace: metallb-system spec: # A list of IP address ranges over which MetalLB has # authority. You can list multiple ranges in a single pool, they # will all share the same settings. Each range can be either a # CIDR prefix, or an explicit start-end range of IPs. addresses: - 192.168.10.0/24 - 192.168.9.1-192.168.9.5 - fc00:f853:0ccd:e799::/124 ``` ## Parameters ### Global parameters | Name | Description | Value | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `global.imageRegistry` | Global Docker image registry | `""` | | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` | | `global.security.allowInsecureImages` | Allows skipping image verification | `false` | | `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` | ### Common parameters | Name | Description | Value | | ------------------------ | --------------------------------------------------------------------------------------- | -------------- | | `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `""` | | `nameOverride` | String to partially override metallb.fullname include (will maintain the release name) | `""` | | `fullnameOverride` | String to fully override metallb.fullname template | `""` | | `commonLabels` | Add labels to all the deployed resources | `{}` | | `commonAnnotations` | Add annotations to all the deployed resources | `{}` | | `extraDeploy` | Array of extra objects to deploy with the release | `[]` | | `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` | | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s) | `["sleep"]` | | `diagnosticMode.args` | Args to override all containers in the the deployment(s)/statefulset(s) | `["infinity"]` | | `installCRDs` | Flag to install metallb CRDs | `true` | ### MetalLB parameters | Name | Description | Value | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `rbac.create` | Specifies whether to install and use RBAC rules | `true` | | `psp.create` | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false` | | `networkPolicy.enabled` | Enable creation of NetworkPolicy resources | `true` | | `networkPolicy.allowExternal` | The Policy model to apply | `true` | | `networkPolicy.allowExternalEgress` | Allow the pod to access any range of port and all destinations. | `true` | | `networkPolicy.kubeAPIServerPorts` | List of possible endpoints to kube-apiserver (limit to your cluster settings to increase security) | `[]` | | `networkPolicy.extraIngress` | Add extra ingress rules to the NetworkPolicy | `[]` | | `networkPolicy.extraEgress` | Add extra ingress rules to the NetworkPolicy | `[]` | | `networkPolicy.ingressNSMatchLabels` | Labels to match to allow traffic from other namespaces | `{}` | | `networkPolicy.ingressNSPodMatchLabels` | Pod labels to match to allow traffic from other namespaces | `{}` | | `prometheusRule.enabled` | Prometheus Operator alertmanager alerts are created | `false` | ### Controller parameters | Name | Description | Value | | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | | `controller.image.registry` | MetalLB Controller image registry | `REGISTRY_NAME` | | `controller.image.repository` | MetalLB Controller image repository | `REPOSITORY_NAME/metallb-controller` | | `controller.image.digest` | MetalLB Controller image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | | `controller.image.pullPolicy` | MetalLB Controller image pull policy | `IfNotPresent` | | `controller.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` | | `controller.updateStrategy.type` | MetalLB controller deployment strategy type. | `RollingUpdate` | | `controller.automountServiceAccountToken` | Mount Service Account token in pod | `true` | | `controller.hostAliases` | Deployment pod host aliases | `[]` | | `controller.rbac.create` | create specifies whether to install and use RBAC rules. | `true` | | `controller.psp.create` | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `true` | | `controller.priorityClassName` | MetalLB controller pods' priorityClassName | `""` | | `controller.runtimeClassName` | Name of the runtime class to be used by MetalLB controller pod(s) | `""` | | `controller.schedulerName` | Name of the k8s scheduler (other than default) | `""` | | `controller.terminationGracePeriodSeconds` | In seconds, time the given to the MetalLB controller pod needs to terminate gracefully | `0` | | `controller.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` | | `controller.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if controller.resources is set (controller.resources is recommended for production). | `nano` | | `controller.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | | `controller.nodeSelector` | Node labels for controller pod assignment | `{}` | | `controller.tolerations` | Tolerations for controller pod assignment | `[]` | | `controller.affinity` | Affinity for controller pod assignment | `{}` | | `controller.podAnnotations` | Controller Pod annotations | `{}` | | `controller.podLabels` | Controller Pod labels | `{}` | | `controller.podAffinityPreset` | Controller Pod affinitypreset. Allowed values: soft, hard | `""` | | `controller.podAntiAffinityPreset` | Controller Pod anti affinitypreset. Allowed values: soft, hard | `soft` | | `controller.nodeAffinityPreset.type` | Controller Pod Node affinity preset. Allowed values: soft, hard | `""` | | `controller.nodeAffinityPreset.key` | Controller Pod Node affinity label key to match | `""` | | `controller.nodeAffinityPreset.values` | Controller Pod Node affinity label values to match | `[]` | | `controller.podSecurityContext.enabled` | Enabled MetalLB Controller pods' Security Context | `true` | | `controller.podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` | | `controller.podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` | | `controller.podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` | | `controller.podSecurityContext.fsGroup` | Set MetalLB Controller pod's Security Context fsGroup | `1001` | | `controller.containerSecurityContext.enabled` | Enabled MetalLB Controller containers' Security Context | `true` | | `controller.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `controller.containerSecurityContext.runAsUser` | Set containers' Security Context runAsUser | `1001` | | `controller.containerSecurityContext.runAsGroup` | Set containers' Security Context runAsGroup | `1001` | | `controller.containerSecurityContext.runAsNonRoot` | Set MetalLB Controller container's Security Context runAsNonRoot | `true` | | `controller.containerSecurityContext.allowPrivilegeEscalation` | Enables privilege Escalation context for the pod. | `false` | | `controller.containerSecurityContext.readOnlyRootFilesystem` | Allows the pod to mount the RootFS as ReadOnly | `true` | | `controller.containerSecurityContext.capabilities.drop` | Drop capabilities for the securityContext | `[]` | | `controller.containerSecurityContext.seccompProfile.type` | Set container's Security Context seccomp profile | `RuntimeDefault` | | `controller.command` | Override default container command (useful when using custom images) | `[]` | | `controller.args` | Override default container args (useful when using custom images) | `[]` | | `controller.lifecycleHooks` | for the MetalLB Controller container(s) to automate configuration before or after startup | `{}` | | `controller.extraEnvVars` | Extra environment variable to pass to the running container. | `[]` | | `controller.extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars for MetalLB controller nodes | `""` | | `controller.extraEnvVarsSecret` | Name of existing Secret containing extra env vars for MetalLB controller nodes | `""` | | `controller.extraVolumes` | Optionally specify extra list of additional volumes for the MetalLB controller pod(s) | `[]` | | `controller.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the MetalLB controller container(s) | `[]` | | `controller.sidecars` | Add additional sidecar containers to the MetalLB Controller pod(s) | `[]` | | `controller.initContainers` | Add additional init containers to the MetalLB Controller pod(s) | `[]` | | `controller.pdb.create` | Enable/disable a Pod Disruption Budget creation | `true` | | `controller.pdb.minAvailable` | Minimum number/percentage of pods that should remain scheduled | `""` | | `controller.pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable. Defaults to `1` if both `controller.pdb.minAvailable` and `controller.pdb.maxUnavailable` are empty. | `""` | | `controller.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` | | `controller.serviceAccount.name` | Name of the service account to use. If not set and create is true, a name is generated using the fullname template. | `""` | | `controller.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `false` | | `controller.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` | | `controller.revisionHistoryLimit` | Configure the revisionHistoryLimit of the Controller deployment | `3` | | `controller.containerPorts.metrics` | Configures the ports the MetalLB Controller listens on for metrics | `7472` | | `controller.livenessProbe.enabled` | Enable livenessProbe | `true` | | `controller.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `10` | | `controller.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` | | `controller.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `1` | | `controller.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `3` | | `controller.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` | | `controller.readinessProbe.enabled` | Enable readinessProbe | `true` | | `controller.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `10` | | `controller.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` | | `controller.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` | | `controller.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `3` | | `controller.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` | | `controller.startupProbe.enabled` | Enable startupProbe | `false` | | `controller.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `10` | | `controller.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` | | `controller.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `1` | | `controller.startupProbe.failureThreshold` | Failure threshold for startupProbe | `3` | | `controller.startupProbe.successThreshold` | Success threshold for startupProbe | `1` | | `controller.customStartupProbe` | Custom liveness probe for the Web component | `{}` | | `controller.customLivenessProbe` | Custom liveness probe for the Web component | `{}` | | `controller.customReadinessProbe` | Custom readiness probe for the Web component | `{}` | | `controller.logLevel` | Sets the controller log level. Does not work if the args are overridden | `info` | | `controller.tlsMinVersion` | Sets the minimum TLS version for the controller | `""` | | `controller.tlsCipherSuites` | Comma separated list of TLS cipher suites for the controller | `""` | | `controller.webhookMode` | Controller webhook mode | `enabled` | | `controller.extraArgs` | Add extra arguments to the default arguments for the controller | `[]` | ### MetalLB controller Prometheus metrics export | Name | Description | Value | | ----------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------ | | `controller.metrics.enabled` | Enable the export of Prometheus metrics | `false` | | `controller.metrics.service.port` | Prometheus metrics service port | `7472` | | `controller.metrics.service.annotations` | Annotations for the Prometheus Exporter service service | `{}` | | `controller.metrics.serviceMonitor.enabled` | Specify if a servicemonitor will be deployed for prometheus-operator | `false` | | `controller.metrics.serviceMonitor.namespace` | Namespace which Prometheus is running in | `""` | | `controller.metrics.serviceMonitor.jobLabel` | Specify the jobLabel to use for the prometheus-operator | `app.kubernetes.io/name` | | `controller.metrics.serviceMonitor.interval` | Scrape interval. If not set, the Prometheus default scrape interval is used | `""` | | `controller.metrics.serviceMonitor.scrapeTimeout` | Timeout after which the scrape is ended | `""` | | `controller.metrics.serviceMonitor.metricRelabelings` | Specify additional relabeling of metrics | `[]` | | `controller.metrics.serviceMonitor.relabelings` | Specify general relabeling | `[]` | | `controller.metrics.serviceMonitor.selector` | ServiceMonitor selector labels | `{}` | | `controller.metrics.serviceMonitor.labels` | Extra labels for the ServiceMonitor | `{}` | | `controller.metrics.serviceMonitor.honorLabels` | honorLabels chooses the metric's labels on collisions with target labels | `false` | ### Speaker parameters | Name | Description | Value | | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | `speaker.enabled` | Whether to enable BGP speakers or not | `true` | | `speaker.image.registry` | MetalLB Speaker image registry | `REGISTRY_NAME` | | `speaker.image.repository` | MetalLB Speaker image repository | `REPOSITORY_NAME/metallb-speaker` | | `speaker.image.digest` | MetalLB Speaker image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | | `speaker.image.pullPolicy` | MetalLB Speaker image pull policy | `IfNotPresent` | | `speaker.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` | | `speaker.updateStrategy.type` | Speaker daemonset strategy type | `RollingUpdate` | | `speaker.rbac.create` | create specifies whether to install and use RBAC rules. | `true` | | `speaker.automountServiceAccountToken` | Mount Service Account token in pod | `true` | | `speaker.networkPolicy.enabled` | Enable creation of NetworkPolicy resources | `true` | | `speaker.networkPolicy.allowExternal` | The Policy model to apply | `true` | | `speaker.networkPolicy.allowExternalEgress` | Allow the pod to access any range of port and all destinations. | `true` | | `speaker.networkPolicy.kubeAPIServerPorts` | List of possible endpoints to kube-apiserver (limit to your cluster settings to increase security) | `[]` | | `speaker.networkPolicy.extraIngress` | Add extra ingress rules to the NetworkPolicy | `[]` | | `speaker.networkPolicy.extraEgress` | Add extra ingress rules to the NetworkPolicy | `[]` | | `speaker.networkPolicy.ingressNSMatchLabels` | Labels to match to allow traffic from other namespaces | `{}` | | `speaker.networkPolicy.ingressNSPodMatchLabels` | Pod labels to match to allow traffic from other namespaces | `{}` | | `speaker.hostAliases` | Deployment pod host aliases | `[]` | | `speaker.psp.create` | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `true` | | `speaker.priorityClassName` | Speaker pods' priorityClassName | `""` | | `speaker.runtimeClassName` | Name of the runtime class to be used by Speaker pod(s) | `""` | | `speaker.terminationGracePeriodSeconds` | In seconds, time the given to the Speaker pod needs to terminate gracefully | `2` | | `speaker.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if speaker.resources is set (speaker.resources is recommended for production). | `nano` | | `speaker.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | | `speaker.nodeSelector` | Node labels for speaker pod assignment | `{}` | | `speaker.tolerations` | Tolerations for speaker pod assignment | `[]` | | `speaker.affinity` | Affinity for speaker pod assignment | `{}` | | `speaker.nodeAffinityPreset.type` | Node affinity preset type. Ignored if `speaker.affinity` is set. Allowed values: `soft` or `hard` | `""` | | `speaker.nodeAffinityPreset.key` | Node label key to match. Ignored if `speaker.affinity` is set | `""` | | `speaker.nodeAffinityPreset.values` | Node label values to match. Ignored if `speaker.affinity` is set | `[]` | | `speaker.podAffinityPreset` | Pod affinity preset. Ignored if `speaker.affinity` is set. Allowed values: `soft` or `hard` | `""` | | `speaker.podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `speaker.affinity` is set. Allowed values: `soft` or `hard` | `soft` | | `speaker.podAnnotations` | Speaker Pod annotations | `{}` | | `speaker.podLabels` | Speaker Pod labels | `{}` | | `speaker.podSecurityContext.enabled` | Enabled Speaker pods' Security Context | `true` | | `speaker.podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` | | `speaker.podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` | | `speaker.podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` | | `speaker.podSecurityContext.fsGroup` | Set Speaker pod's Security Context fsGroup | `0` | | `speaker.containerSecurityContext.enabled` | Enabled Speaker containers' Security Context | `true` | | `speaker.containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` | | `speaker.containerSecurityContext.runAsUser` | Set containers' Security Context runAsUser | `0` | | `speaker.containerSecurityContext.runAsGroup` | Set containers' Security Context runAsGroup | `0` | | `speaker.containerSecurityContext.allowPrivilegeEscalation` | Enables privilege Escalation context for the pod. | `false` | | `speaker.containerSecurityContext.readOnlyRootFilesystem` | Allows the pod to mount the RootFS as ReadOnly | `true` | | `speaker.containerSecurityContext.capabilities.drop` | Drop capabilities for the securityContext. You need to comment out this block if you would like to use `tcpdump` for debugging purposes. | `[]` | | `speaker.containerSecurityContext.capabilities.add` | Add capabilities for the securityContext | `[]` | | `speaker.containerSecurityContext.seccompProfile.type` | Set container's Security Context seccomp profile | `RuntimeDefault` | | `speaker.command` | Override default container command (useful when using custom images) | `[]` | | `speaker.args` | Override default container args (useful when using custom images) | `[]` | | `speaker.lifecycleHooks` | for the Speaker container(s) to automate configuration before or after startup | `{}` | | `speaker.sidecars` | Add additional sidecar containers to the Speaker pod(s) | `[]` | | `speaker.initContainers` | Add additional init containers to the Speaker pod(s) | `[]` | | `speaker.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` | | `speaker.serviceAccount.name` | Name of the service account to use. If not set and create is true, a name is generated using the fullname template. | `""` | | `speaker.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `false` | | `speaker.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` | | `speaker.secretName` | References a Secret name for the member secret outside of the helm chart | `""` | | `speaker.secretKey` | References a Secret key the member secret outside of the helm chart | `""` | | `speaker.secretValue` | Custom value for `speaker.secretKey` | `""` | | `speaker.extraEnvVars` | Extra environment variable to pass to the running container. | `[]` | | `speaker.extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars for Speaker nodes | `""` | | `speaker.extraEnvVarsSecret` | Name of existing Secret containing extra env vars for Speaker nodes | `""` | | `speaker.extraVolumes` | Optionally specify extra list of additional volumes for the Speaker pod(s) | `[]` | | `speaker.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Speaker container(s) | `[]` | | `speaker.containerPorts.metrics` | HTTP Metrics Endpoint | `7472` | | `speaker.livenessProbe.enabled` | Enable livenessProbe | `true` | | `speaker.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `10` | | `speaker.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` | | `speaker.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `1` | | `speaker.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `3` | | `speaker.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` | | `speaker.readinessProbe.enabled` | Enable readinessProbe | `true` | | `speaker.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `10` | | `speaker.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` | | `speaker.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` | | `speaker.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `3` | | `speaker.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` | | `speaker.startupProbe.enabled` | Enable startupProbe | `false` | | `speaker.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `10` | | `speaker.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` | | `speaker.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `1` | | `speaker.startupProbe.failureThreshold` | Failure threshold for startupProbe | `3` | | `speaker.startupProbe.successThreshold` | Success threshold for startupProbe | `1` | | `speaker.customStartupProbe` | Custom liveness probe for the Web component | `{}` | | `speaker.customLivenessProbe` | Custom liveness probe for the Web component | `{}` | | `speaker.customReadinessProbe` | Custom readiness probe for the Web component | `{}` | | `speaker.logLevel` | Sets the speaker log level. Does not work if the args are overridden | `info` | ### FRR Speaker | Name | Description | Value | | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | `speaker.frr.enabled` | Whether to enable FRR mode | `false` | | `speaker.frr.image.registry` | MetalLB Speaker image registry | `REGISTRY_NAME` | | `speaker.frr.image.repository` | MetalLB Speaker image repository | `REPOSITORY_NAME/metallb-speaker` | | `speaker.frr.image.digest` | MetalLB Speaker image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | | `speaker.frr.image.pullPolicy` | MetalLB Speaker image pull policy | `IfNotPresent` | | `speaker.frr.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` | | `speaker.frr.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if speaker.resources is set (speaker.resources is recommended for production). | `micro` | | `speaker.frr.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` | | `speaker.frr.containerSecurityContext.enabled` | Enabled Speaker containers' Security Context | `true` | | `speaker.frr.containerSecurityContext.capabilities.add` | Add capabilities for the securityContext | `[]` | | `speaker.frr.containerSecurityContext.runAsUser` | Set containers' Security Context runAsUser | `0` | | `speaker.frr.containerSecurityContext.runAsGroup` | Set containers' Security Context runAsGroup | `0` | | `speaker.frr.containerPorts.metrics` | HTTP Metrics Endpoint | `7473` | ### FRR Speaker Prometheus metrics export | Name | Description | Value | | ------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------ | | `speaker.frr.metrics.service.port` | Prometheus metrics service port | `7473` | | `speaker.frr.metrics.service.annotations` | Annotations for the Prometheus Exporter service service | `{}` | | `speaker.frr.metrics.serviceMonitor.enabled` | Enable support for Prometheus Operator | `false` | | `speaker.frr.metrics.serviceMonitor.namespace` | Namespace which Prometheus is running in | `""` | | `speaker.frr.metrics.serviceMonitor.jobLabel` | Job label for scrape target | `app.kubernetes.io/name` | | `speaker.frr.metrics.serviceMonitor.interval` | Scrape interval. If not set, the Prometheus default scrape interval is used | `""` | | `speaker.frr.metrics.serviceMonitor.scrapeTimeout` | Timeout after which the scrape is ended | `""` | | `speaker.frr.metrics.serviceMonitor.metricRelabelings` | Specify additional relabeling of metrics | `[]` | | `speaker.frr.metrics.serviceMonitor.relabelings` | Specify general relabeling | `[]` | | `speaker.frr.metrics.serviceMonitor.selector` | ServiceMonitor selector labels | `{}` | | `speaker.frr.metrics.serviceMonitor.labels` | Extra labels for the ServiceMonitor | `{}` | | `speaker.frr.metrics.serviceMonitor.honorLabels` | honorLabels chooses the metric's labels on collisions with target labels | `false` | | `speaker.frr.livenessProbe.enabled` | Enable livenessProbe | `true` | | `speaker.frr.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `10` | | `speaker.frr.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` | | `speaker.frr.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `1` | | `speaker.frr.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `3` | | `speaker.frr.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` | | `speaker.frr.readinessProbe.enabled` | Enable readinessProbe | `true` | | `speaker.frr.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `10` | | `speaker.frr.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `10` | | `speaker.frr.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` | | `speaker.frr.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `3` | | `speaker.frr.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` | | `speaker.frr.startupProbe.enabled` | Enable startupProbe | `true` | | `speaker.frr.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `10` | | `speaker.frr.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` | | `speaker.frr.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `1` | | `speaker.frr.startupProbe.failureThreshold` | Failure threshold for startupProbe | `3` | | `speaker.frr.startupProbe.successThreshold` | Success threshold for startupProbe | `1` | | `speaker.frr.customStartupProbe` | Custom liveness probe for the Web component | `{}` | | `speaker.frr.customLivenessProbe` | Custom liveness probe for the Web component | `{}` | | `speaker.frr.customReadinessProbe` | Custom readiness probe for the Web component | `{}` | ### Speaker Prometheus metrics export | Name | Description | Value | | -------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------ | | `speaker.metrics.enabled` | Enable the export of Prometheus metrics | `false` | | `speaker.metrics.service.port` | Prometheus metrics service port | `7472` | | `speaker.metrics.service.annotations` | Annotations for the Prometheus Exporter service service | `{}` | | `speaker.metrics.serviceMonitor.enabled` | Enable support for Prometheus Operator | `false` | | `speaker.metrics.serviceMonitor.namespace` | Namespace which Prometheus is running in | `""` | | `speaker.metrics.serviceMonitor.jobLabel` | Job label for scrape target | `app.kubernetes.io/name` | | `speaker.metrics.serviceMonitor.interval` | Scrape interval. If not set, the Prometheus default scrape interval is used | `""` | | `speaker.metrics.serviceMonitor.scrapeTimeout` | Timeout after which the scrape is ended | `""` | | `speaker.metrics.serviceMonitor.metricRelabelings` | Specify additional relabeling of metrics | `[]` | | `speaker.metrics.serviceMonitor.relabelings` | Specify general relabeling | `[]` | | `speaker.metrics.serviceMonitor.selector` | ServiceMonitor selector labels | `{}` | | `speaker.metrics.serviceMonitor.labels` | Extra labels for the ServiceMonitor | `{}` | | `speaker.metrics.serviceMonitor.honorLabels` | honorLabels chooses the metric's labels on collisions with target labels | `false` | ```console helm install my-release \ --set readinessProbe.successThreshold=5 \ oci://REGISTRY_NAME/REPOSITORY_NAME/metallb ``` > 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`. The above command sets the `readinessProbe.successThreshold` to `5`. ## Troubleshooting Find more information about how to deal with common errors related to Bitnami's Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues). ## Upgrading ### To 6.4.0 This version introduces image verification for security purposes. To disable it, set `global.security.allowInsecureImages` to `true`. More details at [GitHub issue](https://github.com/bitnami/charts/issues/30850). ### To 6.0.0 This major release includes the changes and features available in MetalLB from version 0.14.x. This new version includes some breaking changes like AddressPool removal or the several changes about the `webhook-server-cert secret`. For more details about MetaLB changes please visit [the release notes](https://metallb.universe.tf/release-notes/). ### To 5.0.0 This major bump changes the following security defaults: - `resourcesPreset` is changed from `none` to the minimum size working in our test suites (NOTE: `resourcesPreset` is not meant for production usage, but `resources` adapted to your use case). - `global.compatibility.openshift.adaptSecurityContext` is changed from `disabled` to `auto`. This could potentially break any customization or init scripts used in your deployment. If this is the case, change the default values to the previous ones. ### To 4.0.0 This major release includes the changes and features available in MetalLB from version 0.13.0. Those changes include the deprecation of configmaps for configuring the service and using CRDs instead. If you are upgrading from a previous version, you can follow the official documentation on [how to migrate the configuration from a configMap to CRDs](https://metallb.universe.tf/#backward-compatibility). ### To 3.0.0 This major release renames several values in this chart and adds missing features, in order to be aligned with the rest of the assets in the Bitnami charts repository. Affected values: - `.prometheus` has been renamed as `.metrics`. - To enable the Prometheus serviceMonitors, it is necessary to enable both `.metrics.enabled` and `.metrics.serviceMonitor.enabled`. - Added the values section `.metrics.service`. - `.securityContext` has been split as `.podSecurityContext` and `.containerSecurityContext` - `controller.containerPort` has been renamed as `controller.containerPorts`. - `speaker.daemonset.hostPorts.metrics` renamed as `speaker.containerPorts.metrics` - `speaker.daemonset.terminationGracePeriodSeconds` renamed as speaker.terminationGracePeriodSeconds ### To 2.0.0 #### What changes were introduced in 2.0.0? - The `.Values.prometheus` section was moved into the components `.Values.controller.prometheus` and `.Values.speaker.prometheus` - The `prometheus.prometheusRule` which is used to toggle the deployment of the metallb alerts is moved under the root of the `.Values.prometheusRule` - A globel `.Values.psp.create` and `.Values.rbac.create` was introduced together with the option of toggeling for each component. (global option overwrites component options) - `Values.controller.rbac.create` and `Values.controller.psp.create` - `Values.speaker.rbac.create` and `Values.speaker.psp.create` #### Considerations when upgrading to 2.0.0 - Check if you used the `prometheus` section in you deployment. - If you do so, place the configuration you made into the sections `controller.prometheus` and `speaker.prometheus`. - `prometheusRule` should stay under the root of your values. ### To 1.0.0 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL. #### What changes were introduced in 1.0.0? - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field. - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts #### Considerations when upgrading to 1.0.0 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3 #### Useful links - - - ## License Copyright © 2025 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.