Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Bringing routes to K8s Nodes: Introducing FRR-K8S

Federico Paolinelli
February 06, 2024
0
150

Bringing routes to K8s Nodes: Introducing FRR-K8S

In this talk I am going to present frr-k8s, a kubernetes wrapper of the popular FRRRouting project that was just released. I will describe:

- how the project can be used to deploy FRR on a kubernetes cluster in an effective way
- what features of FRR (specifically, BGP related) can be leveraged in order to simplify cluster networking
- how to use this project in combination of MetalLB (which is a spinoff of), to leverage a single FRR instance for multiple purposes
- what are some of the network related problems that can be solved with this new component
- a quick summary of the internals of the project

By using this new project, the listeners will be able to handle some of the networking they are probably already facing in a more scalable and maintainable way.

Federico Paolinelli

February 06, 2024
Tweet

More Decks by Federico Paolinelli

See All by Federico Paolinelli
Beyond table tests - Presentation about Go and unit tests
fedepaol
0
55
eBPF for the rest of us - Golab 2023
fedepaol
0
750
How to tame a maintainer
fedepaol
0
100
Reducing cognitive load - yet another idiomatic Go talk
fedepaol
0
330
It's all about reconciliation - Anatomy of a kubernetes controller
fedepaol
1
2.9k
First steps in contributing to Open Source
fedepaol
0
250
Rpc on Steroids with Go and grpc
fedepaol
0
430
Fast messaging with Nats and Go
fedepaol
0
1.1k
Athens, a new place of your depenendecies
fedepaol
0
69

Featured

See All Featured
How to Think Like a Performance Engineer
csswizardry
20
1.1k
Fireside Chat
paigeccino
34
3k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
38
1.8k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
8
860
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.1k
The Invisible Side of Design
smashingmag
298
50k
The World Runs on Bad Software
bkeepers
PRO
65
11k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
44
2.2k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
28
9.1k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
26
1.4k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
6.8k
Building Applications with DynamoDB
mza
90
6.1k

Transcript

  1. Bringing routes to Kubernetes nodes: Introducing FRR-K8s Federico Paolinelli -

    Red Hat

  2. Telco Network Team @ Red Hat Contributed to: - KubeVirt

    - SR-IOV Network Operator - OPA Gatekeeper - OVN-Kubernetes hachyderm.io/@fedepaol - CNI Plugins @fedepaol - MetalLB [email protected] About me

  3. Back to Fosdem 2023

  4. What is FRR?

  5. FRRouting (FRR) is a free and open source Internet routing

    protocol suite for Linux and Unix platforms. It implements BGP, OSPF, RIP, IS-IS, PIM, LDP, BFD, Babel, PBR, OpenFabric and VRRP, with alpha support for EIGRP and NHRP [...] FRR has its roots in the Quagga project. FRR

  6. What is MetalLB?

  7. MetalLB MetalLB is a load-balancer implementation for bare metal Kubernetes

    clusters, using standard routing protocols (github.com/metallb/metallb)

  8. 8 BGP Peer BGPAdv Service Code Data Go Template frr.conf

    frr-reload.py Current configuration Kubernetes API Speaker Pod BGP BGP BGP

  9. “Can I run MetalLB together with my FRR instance on

    the cluster nodes?” A Fosdem 2023 attendee

  10. Asymmetric Return Path Node eth0 Client

  11. Asymmetric Return Path Node eth0 Client

  12. Node VLan0 VLan1 eth0 Client0 Client1 Client Asymmetric Return Path

  13. Node VLan1 eth0 Client0 Client1 Client VLan0 Asymmetric Return Path

  14. Node VLan1 eth0 Client0 Client1 Client VLan0 Asymmetric Return Path

  15. Possible Alternatives

  16. Running two FRR instances Pros: • Nothing to do on

    MetalLB side! Cons: • Duplicate number of sessions (and resources) • Custom ports Node MetalLB Speaker

  17. Cascade two FRR instances Pros: • The user has control

    on the FRR config Cons: • Limits the flexibility on MetalLB • FRR was not able to peer with localhost (Issue 11366) • How about BFD? Node MetalLB Speaker

  18. Share the FRR instance with MetalLB Pros: • The extra

    configuration can scale • No waste of resources / sessions Cons: • Getting the right API is tricky • Not clear how to handle conflicts Node API MetalLB Speaker FRR Daemon User
  19. None

  20. FRR-K8s github.com/metallb/frr-k8s A Kubernetes based daemonset that exposes a subset

    of the FRR API in a Kubernetes compliant manner. The rationale behind the creation of this project is to allow multiple actors to share a single FRR instance running on kubernetes nodes.

  21. 21 FRRConfiguration Code Data Go Template frr.conf frr-reload.py Current configuration

    Kubernetes API FRR-K8s Pod BGP BGP BGP FRRConfiguration FRRConfiguration

  22. https://flic.kr/p/fUF8mY How to deploy it Standalone via: - Helm -

    Kustomize - All in one manifest With MetalLB when choosing FRR-K8s mode github.com/metallb/frr-k8s?tab=readme-ov-file#installing

  23. The API

  24. - What granularity of the API should we expose? -

    How do we merge configurations? - Can we intercept configuration conflicts? - The interaction with MetalLB must be smooth Challenges

  25. FRRConfiguration

  26. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  27. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  28. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  29. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  30. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  31. Configuring BGP apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 toAdvertise: allowed: mode: all toReceive: allowed: mode: all

  32. apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: advsome namespace: frr-k8s-system spec:

    bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 Advertising Prefixes

  33. Advertising Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: advsome namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  34. Advertising Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: advsome namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  35. Advertising Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: advsome namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  36. Receiving Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: recv namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toReceive: allowed: prefixes: - prefix: 192.169.1.0/24 le: 32g

  37. Receiving Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: recv namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toReceive: allowed: prefixes: - prefix: 192.169.1.0/24 le: 32g neighbors: - address: 172.18.0.5 asn: 64512 toReceive: allowed: prefixes: - prefix: 192.169.1.0/24 le: 32 - address: 172.18.0.6 asn: 64512 toReceive: allowed: mode: all

  38. Receiving Prefixes apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: recv namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toReceive: allowed: prefixes: - prefix: 192.169.1.0/24 le: 32g neighbors: - address: 172.18.0.5 asn: 64512 toReceive: allowed: prefixes: - prefix: 192.169.1.0/24 le: 32 - address: 172.18.0.6 asn: 64512 toReceive: allowed: mode: all

  39. Node Selector apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 nodeSelector: labelSelector: role: "worker"

  40. Node Selector apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.30.0.3 asn: 64512 port: 180 nodeSelector: labelSelector: role: "worker" nodeSelector: labelSelector: role: "worker"

  41. Raw Configuration apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: raw: rawConfig: |- router bgp 64512 neighbor 172.18.0.5 remote-as 4200000000 neighbor 172.18.0.5 timers 0 0 neighbor 172.18.0.5 port 180 address-family ipv4 unicast neighbor 172.18.0.5 activate neighbor 172.18.0.5 route-map 172.18.0.5-in in neighbor 172.18.0.5 route-map 172.18.0.5-out out exit-address-family

  42. Raw Configuration apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test namespace:

    frr-k8s-system spec: raw: rawConfig: |- router bgp 64512 neighbor 172.18.0.5 remote-as 4200000000 neighbor 172.18.0.5 timers 0 0 neighbor 172.18.0.5 port 180 address-family ipv4 unicast neighbor 172.18.0.5 activate neighbor 172.18.0.5 route-map 172.18.0.5-in in neighbor 172.18.0.5 route-map 172.18.0.5-out out exit-address-family raw: rawConfig: |- router bgp 64512 neighbor 172.18.0.5 remote-as 4200000000 neighbor 172.18.0.5 timers 0 0 neighbor 172.18.0.5 port 180

  43. Merging multiple configurations https://flic.kr/p/eDrXFX

  44. Node 1 FRR Daemon FRR Configuration Node 2 FRR Daemon

    FRR Configuration FRR Configuration Merging

  45. - A configuration must be self-contained - A configuration can

    only add to the existing configuration - A more permissive configuration can override a less permissive one Guiding principles

  46. Merging apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-1 namespace: frr-k8s-system

    spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-0 namespace: frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  47. Merging apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-1 namespace: frr-k8s-system

    spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-0 namespace: frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  48. Merging apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-1 namespace: frr-k8s-system

    spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-0 namespace: frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  49. Merging apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-1 namespace: frr-k8s-system

    spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: test-0 namespace: frr-k8s-system spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: prefixes: - 192.168.2.0/24 neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: all - address: 172.30.0.3 asn: 4200000000 prefixes: - 192.168.2.0/24 - 192.169.2.0/24

  50. Is it working? https://flic.kr/p/dBhgn6

  51. Exposing the Status apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRNodeState metadata: name: frr-k8s-worker

    spec: {} status: lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512

  52. Exposing the Status apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRNodeState metadata: name: frr-k8s-worker

    spec: {} status: lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512 lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512

  53. Exposing the Status apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRNodeState metadata: name: frr-k8s-worker

    spec: {} status: lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512 lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512

  54. Exposing the Status apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRNodeState metadata: name: frr-k8s-worker

    spec: {} status: lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512 lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512

  55. Exposing the Status apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRNodeState metadata: name: frr-k8s-worker

    spec: {} status: lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512 lastConversionResult: success lastReloadResult: success runningConfig: | Building configuration... Current configuration: ! frr version 8.4.2_git frr defaults traditional hostname frr-k8s-worker log file /etc/frr/frr.log informational ! router bgp 64512 neighbor 172.18.0.5 remote-as 64512

  56. With MetalLB

  57. BGPAdv Node MetalLB Speaker FRR Daemon BGP Peer Service FRRConfiguration

  58. BGPAdv Node MetalLB Speaker FRR Daemon BGP Peer Service FRRConfiguration

  59. BGPAdv Node MetalLB Speaker FRR Daemon BGP Peer Service FRRConfiguration

  60. BGPAdv Node MetalLB Speaker FRR Daemon BGP Peer Service FRRConfiguration

  61. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB

  62. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: hostname: worker0

  63. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: hostname: worker0

  64. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: hostname: worker0

  65. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: filtered prefixes: - 192.168.10.0/32 prefixes: - 192.168.10.0/32

  66. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: filtered prefixes: - 192.168.10.0/32 prefixes: - 192.168.10.0/32

  67. apiVersion: metallb.io/v1beta2 kind: BGPPeer metadata: annotations: name: peer namespace: metallb-system

    spec: myASN: 64512 peerASN: 64512 peerAddress: 172.18.0.5 apiVersion: frrk8s.metallb.io/v1beta1 kind: FRRConfiguration metadata: name: metallb-kind-worker spec: bgp: routers: - asn: 64512 neighbors: - address: 172.18.0.5 asn: 64512 nodeSelector: matchLabels: kubernetes.io/hostname: kind-worker With MetalLB neighbors: - address: 172.18.0.5 asn: 64512 toAdvertise: allowed: mode: filtered prefixes: - 192.168.10.0/32 prefixes: - 192.168.10.0/32

  68. Demo! https://flic.kr/p/dN6fVC

  69. 69 Node 1 Node 2 Node 3 The demo environment

  70. What’s Next? https://flic.kr/p/2iz4dgH

  71. Resources - The FRR-K8s readme - The MetalLB documentation -

    The #metallb channel on the kubernetes slack - FRR docs frrouting.org

  72. Thanks! Any questions? @fedepaol hachyderm.io/@fedepaol [email protected] Slides at: speakerdeck.com/fedepaol [email protected]