fix(docs): update metallb loadbalancerIP behavior (#8139)
**Description** In metallb setup guide, corrected description to specifying loadbalancer IP address for all services ⚒️ Related to #8133 **⚙️ Type of change** - [ ] ⚙️ Feature/App addition - [ ] 🪛 Bugfix - [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 🔃 Refactor of current code **🧪 How Has This Been Tested?** <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration --> **📃 Notes:** <!-- Please enter any other relevant information here --> **✔️ Checklist:** - [ ] ⚖️ My code follows the style guidelines of this project - [ ] 👀 I have performed a self-review of my own code - [ ] #️⃣ I have commented my code, particularly in hard-to-understand areas - [ ] 📄 I have made corresponding changes to the documentation - [ ] ⚠️ My changes generate no new warnings - [ ] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [ ] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
This commit is contained in:
parent
1f327ed3f4
commit
b99e307a76
|
@ -22,7 +22,7 @@ sources:
|
|||
- https://github.com/metallb/metallb
|
||||
- https://metallb.universe.tf
|
||||
type: application
|
||||
version: 8.0.18
|
||||
version: 8.0.19
|
||||
annotations:
|
||||
truecharts.org/catagories: |
|
||||
- core
|
||||
|
|
|
@ -58,21 +58,15 @@ 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.
|
||||
|
||||
:::
|
||||
In the **LoadBalancer IP** field, specify an IP address that is within the MetalLB address pool that you configured. Apply the same IP address to the **LoadBalancer IP** field on other services within the app.
|
||||
|
||||
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 `<pending>`. You may need to do a system reboot as well to properly resolve the conflict.
|
||||
If you have an IP conflict with a previously assigned address it will show as `<pending>`.
|
||||
|
||||
**You may need to do a system reboot as well to properly resolve the conflict.**
|
||||
|
||||
:::caution
|
||||
|
||||
|
|
Loading…
Reference in New Issue