Configure MetalLB BGP service network

docs/04-app-of-apps.md

@@ -94,10 +94,9 @@ and `apps/longhorn.yaml`.
    ```sh
    kubectl -n demo get pods,svc
    ```
-   You'll notice the Service's `EXTERNAL-IP` column says `<pending>` —
-   that's expected. The demo app is a `LoadBalancer` Service, and nothing
-   hands those out real addresses on bare metal until MetalLB is
-   configured, which is exactly the next doc.
+   MetalLB is already configured for this cluster's BGP service network, so
+   the Service's `EXTERNAL-IP` should become `10.10.60.11`. The next doc
+   verifies the BGP sessions and explains how that route reaches the app.
 
 If `app-of-apps`, `demo`, `metallb`, and `longhorn` all show
 `Synced`/`Healthy`, the loop — Git → Argo CD → cluster — is already proven
@@ -116,8 +115,8 @@ end to end; you just can't see the demo app in a browser yet.
 - [ ] `app-of-apps` applied and shows `Synced`/`Healthy`
 - [ ] `demo`, `metallb`, and `longhorn` Applications appeared
       automatically, all `Synced`/`Healthy`
-- [ ] `kubectl -n demo get pods,svc` shows the demo app's Pod running
-      (Service `EXTERNAL-IP` still `<pending>` — expected for now)
+- [ ] `kubectl -n demo get pods,svc` shows the demo Pod running and
+      Service `EXTERNAL-IP` `10.10.60.11`
 
 Continue to [`docs/05-metallb.md`](05-metallb.md) to give the demo app —
 and Argo CD's own UI — a real address.