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 applied in order for services to
19 get external IP address assigned.Please Update values.yaml before deploying
29 The chart can be installed as follows:
32 $ helm install --name metallb metallb
35 The command deploys MetalLB on the Kubernetes cluster. This chart does
36 not provide a default configuration; MetalLB will not act on your
37 Kubernetes Services until you provide
38 one. The [configuration](#configuration) section lists various ways to
39 provide this configuration.
41 Uninstalling the Chart
42 ----------------------
44 To uninstall/delete the `metallb` deployment:
50 The command removes all the Kubernetes components associated with the
51 chart, but will not remove the release metadata from `helm` — this will prevent
52 you, for example, if you later try to create a release also named `metallb`). To
53 fully delete the release and release history, simply [include the `--purge`
57 $ helm delete --purge metallb
63 See `values.yaml` for configuration notes. Specify each parameter
64 using the `--set key=value[,key=value]` argument to `helm
65 install`. For example,
68 $ helm install --name metallb \
69 --set rbac.create=false \
73 The above command disables the use of RBAC rules.
75 Alternatively, a YAML file that specifies the values for the above
76 parameters can be provided while installing the chart. For example,
79 $ helm install --name metallb -f values.yaml metallb
82 By default, this chart does not install a configuration for MetalLB, and simply
83 warns you that you must follow [the configuration instructions on MetalLB's
84 website][metallb-config] to create an appropriate ConfigMap.
86 **Please note:** By default, this chart expects a ConfigMap named
87 'metallb-config' within the same namespace as the chart is
88 deployed. _This is different than the MetalLB documentation_, which
89 asks you to create a ConfigMap in the `metallb-system` namespace, with
92 For simple setups that only use MetalLB's [ARP mode][metallb-arpndp-concepts],
93 you can specify a single IP range using the `arpAddresses` parameter to have the
94 chart install a working configuration for you:
97 $ helm install --name metallb \
98 --set arpAddresses=192.168.16.240/30 \
102 If you have a more complex configuration and want Helm to manage it for you, you
103 can provide it in the `config` parameter. The configuration format is
104 [documented on MetalLB's website][metallb-config].
110 - peer-address: 10.0.0.1
119 $ helm install --name metallb -f values.yaml metallb
122 [helm-home]: https://helm.sh
123 [helm-usage]: https://docs.helm.sh/using_helm/
124 [k8s-home]: https://kubernetes.io
125 [metallb-arpndp-concepts]: https://metallb.universe.tf/concepts/arp-ndp/
126 [metallb-config]: https://metallb.universe.tf/configuration/
127 [metallb-home]: https://metallb.universe.tf