Delete metallb chart (and related docs)

changelog.d/0-release-notes/drop-metallb-chart

@@ -0,0 +1,2 @@
+Remove the old `metallb` wrapper chart. This hasn't been published or updated
+for quite some time. Even the Docker images weren't available anymore.

docs/src/how-to/install/infrastructure-configuration.md

@@ -330,82 +330,6 @@ As of 2020-08-10, the documentation sections below are partially out of date and
 - Add password in `secrets/wire-server`’s secrets file under
   `brig.secrets.smtpPassword`
 
-## Load balancer on bare metal servers
-
-**Assumptions**:
-
-- You installed kubernetes on bare metal servers or virtual machines
-  that can bind to a public IP address.
-- **If you are using AWS or another cloud provider, see**[Creating a
-  cloudprovider-based load
-  balancer]()**instead**
-
-**Provides**:
-
-- Allows using a provided Load balancer for incoming traffic
-- SSL termination is done on the ingress controller
-- You can access your wire-server backend with given DNS names, over
-  SSL and from anywhere in the internet
-
-**You need**:
-
-- A kubernetes node with a *public* IP address (or internal, if you do
-  not plan to expose the Wire backend over the Internet but we will
-  assume you are using a public IP address)
-- DNS records for the different exposed addresses (the ingress depends
-  on the usage of virtual hosts), namely:
-  - `nginz-https.<domain>`
-  - `nginz-ssl.<domain>`
-  - `assets.<domain>`
-  - `webapp.<domain>`
-  - `account.<domain>`
-  - `teams.<domain>`
-- A wildcard certificate for the different hosts (`*.<domain>`) - we
-  assume you want to do SSL termination on the ingress controller
-
-**Caveats**:
-
-- Note that there can be only a *single* load balancer, otherwise your
-  cluster might become
-  [unstable](https://metallb.universe.tf/installation/)
-
-**How to configure**:
-
-```default
-cp values/metallb/demo-values.example.yaml values/metallb/demo-values.yaml
-cp values/nginx-ingress-services/demo-values.example.yaml values/nginx-ingress-services/demo-values.yaml
-cp values/nginx-ingress-services/demo-secrets.example.yaml values/nginx-ingress-services/demo-secrets.yaml
-```
-
-- Adapt `values/metallb/demo-values.yaml` to provide a list of public
-  IP address CIDRs that your kubernetes nodes can bind to.
-- Adapt `values/nginx-ingress-services/demo-values.yaml` with correct URLs
-- Put your TLS cert and key into
-  `values/nginx-ingress-services/demo-secrets.yaml`.
-
-Install `metallb` (for more information see the
-[docs](https://metallb.universe.tf)):
-
-```sh
-helm upgrade --install --namespace metallb-system metallb wire/metallb \
-    -f values/metallb/demo-values.yaml \
-    --wait --timeout 1800
-```
-
-Install `ingress-nginx-controller` (`nginx-ingress` controller) and
-`nginx-ingress-services`:
-
-::
-: helm upgrade –install –namespace demo demo-ingress-nginx-controller wire/ingress-nginx-controller
-
-: –wait
-
-helm upgrade –install –namespace demo demo-nginx-ingress-services wire/nginx-ingress-services
-
-: -f values/nginx-ingress-services/demo-values.yaml -f values/nginx-ingress-services/demo-secrets.yaml –wait
-
-Now, create DNS records for the URLs configured above.
-
 ## Load Balancer on cloud-provider
 
 ### AWS