feat: Add fabric-router image and production deployment - #269
Merged
Conversation
Add a fabric-router container image (FRR plus tcpdump, mtr, telnet, dig, and curl for troubleshooting) and wire it into the containerlab lab and the CI publish workflow. Introduce config/fabric/ as a production Kustomize component for the underlay eBGP DaemonSet that galactic-router depends on. It is a single flat DaemonSet scheduled on nodes labeled galactic.datumapis.com/node=edge or =control; unlike every other config/ component it has no generic frr.conf default (BGP peering is site-specific), so it is not part of the root config/kustomization.yaml and must be applied separately once the deployer supplies a fabric-config ConfigMap. Convert the containerlab lab's fabric resources from raw manifests and per-site node-affinity patches to kustomize overlays that build on config/fabric/, patching in only the lab-local image override and, for iad (which needs two differently-configured fabric pods on one cluster), a narrower per-role affinity plus a renamed DaemonSet. Bake the two static FRR config files (daemons, vtysh.conf) into the image instead of shipping them through ConfigMaps, since they never vary by site.
quay.io/frrouting/frr:10.2.0 is Alpine-based, not Debian-based, so apt-get isn't available and the image build was failing. Switches to apk with the Alpine equivalents (mtr, busybox-extras for telnet, bind-tools for dnsutils). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ecv
approved these changes
Jul 30, 2026
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
galactic-routerneeds a working underlay eBGP session before it can start, but there was no container image or Kustomize manifest for that FRR-based fabric role — the only thing running it was the containerlab lab's own raw manifests, hand-copied per site.This adds
containers/fabric-router/Dockerfile(upstream FRR plustcpdump,mtr,telnet,dig,curlfor troubleshooting, and the two static FRR config files baked in since they never vary by site) and a newconfig/fabric/production Kustomize component: a single flat DaemonSet scheduled on nodes labeledgalactic.datumapis.com/node=edgeor=control. Unlike every otherconfig/component, it has no genericfrr.confdefault — BGP peering is site-specific — so it's intentionally left out of the rootconfig/kustomization.yamland must be applied separately once the deployer supplies afabric-configConfigMap.The containerlab lab's fabric resources are converted from raw manifests and per-site node-affinity patches into kustomize overlays that build on
config/fabric/, patching in only the lab-local image override and (foriad, which needs two differently-configured fabric pods on one cluster) a narrower per-role affinity plus a renamed DaemonSet.Test plan
kubectl kustomizevalidated forconfig/fabricand all four lab overlays (dfw, iad, sjc, iad-control), confirming correct image, affinity, and ConfigMap wiringtask deploy/task testrun against the containerlab lab (not run in this environment — no Docker available)