You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: update containerlab deploy for galactic-router
- Replace galactic-agent with galactic-router container image
- Replace BGPInstance/BGPPeer CRDs with BGPRouter/BGPPeer/BGPAdvertisement
- Replace infra cluster with dfw cluster (three-region: dfw, iad, sjc)
- Replace infra route reflector with iad-worker-rr node
- Remove cosmos operator deployment from containerlab
- Update NAD configs to use galacticRouter instead of gobgp
- Add BGP CRD patches to fix ASN maximum for kubebuilder v0.18.0
- Update all documentation, Taskfile, and scripts accordingly
Copy file name to clipboardExpand all lines: AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,8 +50,8 @@ Summary:
50
50
51
51
## Deployments
52
52
53
-
-**`deploy/galactic-router/`** — Kustomize manifests for the router DaemonSet, RBAC, and ServiceAccount. Apply with `kubectl apply -k deploy/galactic-router/`.
54
-
-**`deploy/containerlab/`** — ContainerLab topology (`gvpc.clab.yaml`) for three Kind clusters (iad, sjc, infra) wired over an IPv6 SRv6 transit mesh. FRR runs as a hostNetwork DaemonSet on each worker for eBGP underlay; `galactic-router` (tenant role) handles EVPN path distribution over iBGP. See `deploy/containerlab/README.md` and `deploy/containerlab/Taskfile.yaml` for bring-up commands.
53
+
-**`deploy/galactic-router/`** — Production manifests for the router DaemonSet, RBAC, and ServiceAccount. Apply with `kubectl apply -f deploy/galactic-router/`.
54
+
-**`deploy/containerlab/`** — ContainerLab topology (`gvpc.clab.yaml`) for three Kind clusters (dfw, iad, sjc) wired over an IPv6 SRv6 transit mesh. FRR runs as a hostNetwork DaemonSet on each worker for eBGP underlay; `galactic-router` (tenant role) handles EVPN path distribution over iBGP. See `deploy/containerlab/README.md` and `deploy/containerlab/Taskfile.yaml` for bring-up commands.
|`sjc-worker`| ext-container | Kind worker; runs FRR PE + galactic-router PE |
32
34
|`tr1`–`tr4`| linux (FRR) | iBGP full mesh, AS 65100 |
33
35
34
36
### BGP design
35
37
36
38
```
37
-
AS 65000 (iad-underlay / FRR) ──eBGP unnumbered── tr1 (AS 65100)
38
-
AS 65000 (sjc-underlay / FRR) ──eBGP unnumbered── tr2 (AS 65100)
39
-
AS 65000 (infra-control-plane / FRR) ──eBGP unnumbered── tr3 (AS 65100)
40
-
41
-
AS 65000 (iad-overlay / GoBGP) ──iBGP── infra-control-plane (AS 65000 RR)
42
-
AS 65000 (sjc-overlay / GoBGP) ──iBGP── infra-control-plane (AS 65000 RR)
39
+
AS 65000 (dfw-underlay / FRR) ──eBGP unnumbered── tr1 (AS 65100)
40
+
AS 65000 (iad-underlay / FRR) ──eBGP unnumbered── tr3:eth5 (AS 65100)
41
+
AS 65000 (iad-rr-underlay / FRR) ──eBGP unnumbered── tr3:eth4 (AS 65100)
42
+
AS 65000 (sjc-underlay / FRR) ──eBGP unnumbered── tr2 (AS 65100)
43
+
44
+
AS 65000 (dfw-overlay / galactic-router) ──iBGP── iad-rr (AS 65000 RR)
45
+
AS 65000 (iad-overlay / galactic-router) ──iBGP── iad-rr (AS 65000 RR)
46
+
AS 65000 (sjc-overlay / galactic-router) ──iBGP── iad-rr (AS 65000 RR)
43
47
```
44
48
45
-
- All clusters use a single AS (65000) for both the FRR underlay and the GoBGP overlay.
49
+
- All clusters use a single AS (65000) for both the FRR underlay and the galactic-router overlay.
46
50
- The transit mesh carries IPv6 unicast (SRv6 locator prefixes and loopbacks) via iBGP within AS 65100.
47
51
- FRR PE nodes originate their SRv6 forwarding prefix (`2001:db8:ffXX::/48`) and SRv6 SID block (`fc00:0:X::/48`) toward the transit layer via eBGP unnumbered.
48
52
-`allowas-in 1` is configured on all cluster FRR instances so each site accepts prefixes that carry AS 65000 in the path — necessary because the transit reflects routes from one AS 65000 site to another.
49
-
-GoBGP instances on iad/sjc workers peer with infra-control-plane over iBGP (AS 65000) for `l3vpn-ipv4-unicast` (type-5 VPN routes). GoBGP runs with `port = -1`; FRR owns TCP/179.
53
+
-galactic-router instances on dfw/iad/sjc workers peer with iad-worker-rr over iBGP (AS 65000) for `l2vpn-evpn`routes. GoBGP runs with outbound-only mode (`listenPort=-1`); all BGP sessions are initiated outbound.
0 commit comments