diff --git a/charts/enterprise/metallb/Chart.yaml b/charts/enterprise/metallb/Chart.yaml index 73f8bbb29d4..773a0ccc09c 100644 --- a/charts/enterprise/metallb/Chart.yaml +++ b/charts/enterprise/metallb/Chart.yaml @@ -25,7 +25,7 @@ sources: - https://github.com/metallb/metallb - https://metallb.universe.tf type: application -version: 4.0.10 +version: 4.0.11 annotations: truecharts.org/catagories: | - core diff --git a/charts/enterprise/metallb/docs/img/metallb_guide_addresspool_basic.png b/charts/enterprise/metallb/docs/img/metallb_guide_addresspool_basic.png new file mode 100644 index 00000000000..a36b48caaae Binary files /dev/null and b/charts/enterprise/metallb/docs/img/metallb_guide_addresspool_basic.png differ diff --git a/charts/enterprise/metallb/docs/img/metallb_guide_disableLB.png b/charts/enterprise/metallb/docs/img/metallb_guide_disableLB.png new file mode 100644 index 00000000000..7f2dd7ca9c0 Binary files /dev/null and b/charts/enterprise/metallb/docs/img/metallb_guide_disableLB.png differ diff --git a/charts/enterprise/metallb/docs/img/metallb_guide_l2advertisement.png b/charts/enterprise/metallb/docs/img/metallb_guide_l2advertisement.png new file mode 100644 index 00000000000..bea76543fa5 Binary files /dev/null and b/charts/enterprise/metallb/docs/img/metallb_guide_l2advertisement.png differ diff --git a/charts/enterprise/metallb/docs/img/metallb_guide_specifyIP.png b/charts/enterprise/metallb/docs/img/metallb_guide_specifyIP.png new file mode 100644 index 00000000000..033fde0dd38 Binary files /dev/null and b/charts/enterprise/metallb/docs/img/metallb_guide_specifyIP.png differ diff --git a/charts/enterprise/metallb/docs/setup-guide.md b/charts/enterprise/metallb/docs/setup-guide.md new file mode 100644 index 00000000000..aa48740a912 --- /dev/null +++ b/charts/enterprise/metallb/docs/setup-guide.md @@ -0,0 +1,79 @@ +# MetalLB Basic Setup + +The guide walks through a basic configuration of MetalLB for a single address pool on a layer 2 network. This will allow assigning different IP addresses by app. + +## 1. Install MetalLB without any config changes + +:::caution + +The MetalLB chart must be installed initially without any config changes. Once it is installed, proceed to Step 2 and edit the config. + +::: + +## 2. Configure Address Pool & L2 Advertisement + +![metallb-addpoolbasic](img/metallb_guide_addresspool_basic.png) + +Create a new entry under `Configure IP Address Pools Object` + +- **Name**: Enter a general name for this IP range. Something like _apps_ or _charts_ for this field is fine. +- **Auto Assign**: if you want MetalLB Services to auto-assign IPs from the configured address pool without needing to specify per app. Recommendation is to keep this checked. You can still specify an IP for apps as needed (see step 4). + +Create a single entry under `Configure Address Pools` + +- **Address Pool Entry:** Specify an IP range for MetalLB to assign IPs that is **OUTSIDE** your current DHCP range on your LAN. For example, if your DHCP range is `192.168.1.100-192.168.1.255`, then your entry can be any range below `192.168.1.100`. This entry can also be specified in CIDR format. + +_For users with VLANs or multiple subnets, you may create create additional address pool objects as needed._ + +![metallb-l2advertisement](img/metallb_guide_l2advertisement.png) + +Create a new entry under `Configure L2 Advertisements`. + +- **Name**: Enter a basic name for your layer 2 advertisement. +- **Address Pool Entry:** This should match the **name** of the address pool created above (not the IP range itself). + +_For users with VLANs or multiple subnets, you may reference multiple address pool objects under a single L2 Advertisement entry as needed._ + +## 3. Disable SCALE's Default Loadbalancer + +With MetalLB installed and configured, you must now disable SCALE's default loadbalancer. + +In the SCALE UI, under **Apps** > **Settings** > **Advanced Settings** + +![metallb-disable](img/metallb_guide_disableLB.png) + +Uncheck `Enable Integrated Loadbalancer`. + +**This will trigger a restart of Kubernetes and all apps**. After roughly 5-10 minutes, your apps will redeploy using the MetalLB-assigned addresses. + +## 4. Optional: Specify IP Address per App or Service + +![metallb-specifyIP](img/metallb_guide_specifyIP.png) + +With MetalLB installed, you may optionally specify IP addresses for your apps. + +For each app, under **Networking and Services**, select `LoadBalancer` Service Type for the Main Service. + +In the **LoadBalancer IP** field, specify an IP address that is within the MetalLB address pool that you configured. + +With the Main Service assigned, you do not need to specify an IP address for other services under the same app, unless you specifically want a different IP address for that service. + +:::info + +By default all services under a single app will be assigned the same IP address. + +::: + +You may need to stop & restart the app for the IP address to take affect. + +From your SCALE shell, run the command `k3s kubectl get svc -A` to verify the IP addresses assigned for each of your apps. The IPs will be listed under the `EXTERNAL-IP` column. + +If you have an IP conflict with a previously assigned address it will show as ``. You may need to do a system reboot as well to properly resolve the conflict. + +:::caution + +Known Issue: On the SCALE Installed Applications page, the **Open** buttons on each app card will still open a URL to your app using your SCALE Host IP, rather than the MetalLB-Assigned IP. This may be resolved in the future. + +::: + +For details on other configuration options, please reference the [MetaLB documentation](https://metallb.universe.tf/configuration/)