2 * Copyright 2019 Intel Corporation, Inc
4 * Licensed under the Apache License, Version 2.0 (the "License");
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
8 * http://www.apache.org/licenses/LICENSE-2.0
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an "AS IS" BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
18 NOTE - A configMap of available IPs is to be applied in order for services
19 to get external IP address assigned. Please Update values.yaml with
20 IP addresses before deploying
30 The chart can be installed as follows:
33 $ helm install --name metallb metallb
36 The command deploys MetalLB on the Kubernetes cluster. This chart does
37 not provide a default configuration; MetalLB will not act on your
38 Kubernetes Services until you provide
39 one. The [configuration](#configuration) section lists various ways to
40 provide this configuration.
42 Uninstalling the Chart
43 ----------------------
45 To uninstall/delete the `metallb` deployment:
51 The command removes all the Kubernetes components associated with the
52 chart, but will not remove the release metadata from `helm` — this will prevent
53 you, for example, if you later try to create a release also named `metallb`). To
54 fully delete the release and release history, simply [include the `--purge`
58 $ helm delete --purge metallb
64 See `values.yaml` for configuration notes. Specify each parameter
65 using the `--set key=value[,key=value]` argument to `helm
66 install`. For example,
69 $ helm install --name metallb \
70 --set rbac.create=false \
74 The above command disables the use of RBAC rules.
76 Alternatively, a YAML file that specifies the values for the above
77 parameters can be provided while installing the chart. For example,
80 $ helm install --name metallb -f values.yaml metallb
83 By default, this chart does not install a configuration for MetalLB, and simply
84 warns you that you must follow [the configuration instructions on MetalLB's
85 website][metallb-config] to create an appropriate ConfigMap.
87 **Please note:** By default, this chart expects a ConfigMap named
88 'metallb-config' within the same namespace as the chart is
89 deployed. _This is different than the MetalLB documentation_, which
90 asks you to create a ConfigMap in the `metallb-system` namespace, with
93 For simple setups that only use MetalLB's [ARP mode][metallb-arpndp-concepts],
94 you can specify a single IP range using the `arpAddresses` parameter to have the
95 chart install a working configuration for you:
98 $ helm install --name metallb \
99 --set arpAddresses=192.168.16.240/30 \
103 If you have a more complex configuration and want Helm to manage it for you, you
104 can provide it in the `config` parameter. The configuration format is
105 [documented on MetalLB's website][metallb-config].
111 - peer-address: 10.0.0.1
120 $ helm install --name metallb -f values.yaml metallb
123 [helm-home]: https://helm.sh
124 [helm-usage]: https://docs.helm.sh/using_helm/
125 [k8s-home]: https://kubernetes.io
126 [metallb-arpndp-concepts]: https://metallb.universe.tf/concepts/arp-ndp/
127 [metallb-config]: https://metallb.universe.tf/configuration/
128 [metallb-home]: https://metallb.universe.tf