bitnami · miguelaeh · Apr 29, 2020 · Mar 5, 2020 · Mar 5, 2020 · Mar 5, 2020
diff --git a/bitnami/metallb/.helmignore b/bitnami/metallb/.helmignore
@@ -0,0 +1,22 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/
diff --git a/bitnami/metallb/Chart.yaml b/bitnami/metallb/Chart.yaml
@@ -0,0 +1,23 @@
+apiVersion: v1
+name: metallb
+description: The Metal LB for Kubernetes
+appVersion: 0.8.3
+keywords:
+  - "load-balancer"
+  - "balancer"
+  - "lb"
+  - "bgp"
+  - "arp"
+  - "vrrp"
+  - "vip"
+home: https://metallb.universe.tf
+icon: https://metallb.universe.tf/images/logo.png
+sources:
+  - https://github.com/metallb/metallb
+  - https://github.com/bitnami/bitnami-docker-metallb
+version: 0.1.3
+maintainers:
+  - name: cellebyte
+    url: https://github.com/Cellebyte
+  - name: Bitnami
+    email: containers@bitnami.com
diff --git a/bitnami/metallb/README.md b/bitnami/metallb/README.md
@@ -0,0 +1,141 @@
+# metallb
+
+[MetalLB](https://metallb.universe.tf/faq/) is an open source, rock solid LoadBalancer. It handles the `ServiceType: Loadbalancer`.
+
+## TL;DR;
+
+```console
+$ helm repo add bitnami https://charts.bitnami.com/bitnami
+$ helm install my-release bitnami/metallb
+```
+
+## 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](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
+
+Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This Helm chart has been tested on top of [Bitnami Kubernetes Production Runtime](https://kubeprod.io/) (BKPR). Deploy BKPR to get automated TLS certificates, logging and monitoring for your applications.
+
+## Prerequisites
+
+- Kubernetes 1.12+
+- Helm 2.11+ or Helm 3.0-beta3+
+- 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 repo add bitnami https://charts.bitnami.com/bitnami
+$ helm install my-release bitnami/metallb
+```
+
+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`
+
+## Uninstalling the Chart
+
+To uninstall/delete the `my-release` helm release:
+
+```console
+$ helm uninstall my-release
+```
+
+The command removes all the Kubernetes components associated with the chart and deletes the release.
+
+## Parameters
+
+The following tables lists the configurable parameters of the metallb chart and their default values.
+
+| Parameter                                          | Description                                                                                            | Default                                                 |
+|----------------------------------------------------|--------------------------------------------------------------------------------------------------------|---------------------------------------------------------|
+| `global.imageRegistry`                             | Global Docker image registry                                                                           | `nil`                                                   |
+| `global.imagePullSecrets`                          | Global Docker registry secret names as an array                                                        | `[]` (does not add image pull secrets to deployed pods) |
+| `controller.image.registry`                        | MetalLB Controller image registry                                                                      | `docker.io`                                             |
+| `controller.image.repository`                      | MetalLB Controller image name                                                                          | `metallb/controller`                                    |
+| `controller.image.tag`                             | MetalLB Controller image tag                                                                           | `{TAG_NAME}`                                            |
+| `controller.pullPolicy`                            | MetalLB Controller image pull policy                                                                   | `IfNotPresent`                                          |
+| `controller.image.pullSecrets`                     | Specify docker-registry secret names as an array                                                       | `[]` (does not add image pull secrets to deployed pods) |
+| `controller.resources.limits`                      | Specify resource limits which the container is not allowed to succeed.                                 | `{}` (does not add resource limits to deployed pods)    |
+| `controller.resources.requests`                    | Specify resource requests which the container needs to spawn.                                          | `{}` (does not add resource limits to deployed pods)    |
+| `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.serviceAccount.create`                 | create a serviceAccount for the controller pod                                                         | `true`                                                  |
+| `controller.serviceAccount.name`                   | use the serviceAccount with the specified name                                                         | ""                                                      |
+| `speaker.image.registry`                           | MetalLB Speaker image registry                                                                         | `docker.io`                                             |
+| `speaker.image.repository`                         | MetalLB Speaker image name                                                                             | `metallb/speaker`                                       |
+| `speaker.image.tag`                                | MetalLB Speaker image tag                                                                              | `{TAG_NAME}`                                            |
+| `speaker.pullPolicy`                               | MetalLB Speaker image pull policy                                                                      | `IfNotPresent`                                          |
+| `speaker.image.pullSecrets`                        | Specify docker-registry secret names as an array                                                       | `[]` (does not add image pull secrets to deployed pods) |
+| `speaker.resources.limits`                         | Specify resource limits which the container is not allowed to succeed.                                 | `{}` (does not add resource limits to deployed pods)    |
+| `speaker.resources.requests`                       | Specify resource requests which the container needs to spawn.                                          | `{}` (does not add resource limits to deployed pods)    |
+| `speaker.nodeSelector`                             | Node labels for speaker pod assignment                                                                 | `{}`                                                    |
+| `speaker.tolerations`                              | Tolerations for speaker pod assignment                                                                 | `[]`                                                    |
+| `speaker.affinity`                                 | Affinity for speaker pod assignment                                                                    | `{}`                                                    |
+| `speaker.podAnnotations`                           | Speaker Pod annotations                                                                                | `{}`                                                    |
+| `speaker.serviceAccount.create`                    | create a serviceAccount for the speaker pod                                                            | `true`                                                  |
+| `speaker.serviceAccount.name`                      | use the serviceAccount with the specified name                                                         | ""                                                      |
+| `nameOverride`                                     | String to partially override metallb.fullname template with a string (will prepend the release name)   | `nil`                                                   |
+| `fullnameOverride`                                 | String to fully override metallb.fullname template with a string                                       | `nil`                                                   |
+| `livenessProbe.enabled`                            | Enable/disable the Liveness probe                                                                      | `true`                                                  |
+| `livenessProbe.initialDelaySeconds`                | Delay before liveness probe is initiated                                                               | `60`                                                    |
+| `livenessProbe.periodSeconds`                      | How often to perform the probe                                                                         | `10`                                                    |
+| `livenessProbe.timeoutSeconds`                     | When the probe times out                                                                               | `5`                                                     |
+| `livenessProbe.successThreshold`                   | Minimum consecutive successes for the probe to be considered successful after having failed.           | `1`                                                     |
+| `livenessProbe.failureThreshold`                   | Minimum consecutive failures for the probe to be considered failed after having succeeded.             | `6`                                                     |
+| `existingConfigMap`                                | Specify an existing configMapName to use. (this mutually exclusive with existingConfigMap)             | `metallb-config`                                        |
+| `configInline`                                     | Specify the config for metallb as a new configMap inline.                                              | `{}` (does not create configMap)                        |
+| `rbac.create`                                      | Specify if an rbac authorization should be created with the necessarry Rolebindings.                   | `true`                                                  |
+| `prometheus.serviceMonitor.enabled`                | Specify if a servicemonitor will be deployed for prometheus-operator.                                  | `true`                                                  |
+| `prometheus.serviceMonitor.jobLabel`               | Specify the jobLabel to use for the prometheus-operator                                                | `metallb`                                               |
+| `prometheus.serviceMonitor.interval`               | Specify the scrape interval if not specified use defaul prometheus scrapeIntervall                     | `""`                                                    |
+| `prometheus.serviceMonitor.metricRelabelings`      | Specify additional relabeling of metrics.                                                              | `[]`                                                    |
+| `prometheus.serviceMonitor.relabelings`            | Specify general relabeling.                                                                            | `[]`                                                    |
+| `prometheus.serviceMonitor.prometheusRule.enabled` | Enable prometheus alertmanager basic alerts.                                                           | `true`                                                  |
+
+Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
+
+```console
+$ helm install my-release \
+  --set livenessProbe.successThreshold=5 \
+    bitnami/metallb
+```
+The above command sets the `livenessProbe.successThreshold` to `5`.
+
+## Configuration and installation details
+
+### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
+
+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/).
+
+### Example Layer 2 configuration
+
+```yaml
+configInline:
+  # The address-pools section lists the IP addresses that MetalLB is
+  # allowed to allocate, along with settings for how to advertise
+  # those addresses over BGP once assigned. You can have as many
+  # address pools as you want.
+  address-pools:
+  - # A name for the address pool. Services can request allocation
+    # from a specific address pool using this name, by listing this
+    # name under the 'metallb.universe.tf/address-pool' annotation.
+    name: generic-cluster-pool
+    # Protocol can be used to select how the announcement is done.
+    # Supported values are bgp and layer2.
+    protocol: layer2
+    # 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:
+    - 10.27.50.30-10.27.50.35
+```
diff --git a/bitnami/metallb/templates/NOTES.txt b/bitnami/metallb/templates/NOTES.txt
@@ -0,0 +1,11 @@
+
+MetalLB is now running in the cluster.
+{{- if .Values.configInline }}
+LoadBalancer Services in your cluster are now available on the IPs you
+defined in MetalLB's configuration. To see IP assignments,
+try `kubectl get services`.
+{{- else }}
+WARNING: you specified a ConfigMap that isn't managed by
+Helm. LoadBalancer services will not function until you add that
+ConfigMap to your cluster yourself.
+{{- end }}