Configure MetalLB BGP service network
This commit is contained in:
+10
-5
@@ -34,17 +34,22 @@ on every node.
|
||||
|
||||
## MetalLB pool
|
||||
|
||||
This dedicated service range is advertised to the MikroTik at
|
||||
`10.10.10.1` with BGP by the two workers; it is not an L2 or DHCP pool.
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| Range | `EDIT ME — e.g. 192.168.1.240-192.168.1.250` |
|
||||
| Configured in | [`apps/metallb/templates/ipaddresspool.yaml`](../apps/metallb/templates/ipaddresspool.yaml) |
|
||||
| Range | `10.10.60.10-10.10.60.250` |
|
||||
| Router / ASN | MikroTik RB5009 `10.10.10.1` / `64512` |
|
||||
| Worker ASN | `64520` |
|
||||
| Configured in | [`apps/metallb/templates/`](../apps/metallb/templates/) |
|
||||
|
||||
## Allocated addresses (from the MetalLB pool)
|
||||
|
||||
| Address | What | Namespace | Port(s) | URL | Source |
|
||||
|---|---|---|---|---|---|
|
||||
| `EDIT ME` | Argo CD UI/API (`argocd-server`) | `argocd` | 443 | `https://EDIT ME` | Patched to `LoadBalancer` by hand — see [`docs/05-metallb.md`](05-metallb.md) |
|
||||
| `EDIT ME` | Demo app | `demo` | 80 | `http://EDIT ME` | [`apps/demo/service.yaml`](../apps/demo/service.yaml) |
|
||||
| `10.10.60.10` | Argo CD UI/API (`argocd-server`) | `argocd` | 443 | `https://10.10.60.10` | Patched to `LoadBalancer` by hand — see [`docs/05-metallb.md`](05-metallb.md) |
|
||||
| `10.10.60.11` | Demo app | `demo` | 80 | `http://10.10.60.11` | [`apps/demo/service.yaml`](../apps/demo/service.yaml) |
|
||||
|
||||
Add a row here every time you add a new app with a `LoadBalancer` Service
|
||||
(see [`docs/08-adding-new-apps.md`](08-adding-new-apps.md)). Leave the URL
|
||||
@@ -57,4 +62,4 @@ Addresses from the range above that aren't spoken for yet. Update this
|
||||
alongside the table above so it's obvious at a glance what's safe to hand
|
||||
to the next app.
|
||||
|
||||
- `EDIT ME`
|
||||
- `10.10.60.12-10.10.60.250`
|
||||
|
||||
Reference in New Issue
Block a user