Configure MetalLB BGP service network
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# BGPAdvertisement tells MetalLB to announce allocated Service addresses as
|
||||
# routes to the MikroTik peer defined in bgppeer.yaml. Unlike Layer 2 mode,
|
||||
# the workers do not need an interface inside 10.10.60.0/24: the router learns
|
||||
# that each allocated address is reachable through the Kubernetes nodes.
|
||||
#
|
||||
# `aggregationLength: 32` advertises only addresses that a Service actually
|
||||
# owns, as individual IPv4 host routes. Advertising the whole /24 would make
|
||||
# the router send every address in the pool toward the cluster, including
|
||||
# unallocated ones.
|
||||
#
|
||||
# Sync wave 1 defers this custom resource until the MetalLB chart's CRDs and
|
||||
# controllers from wave 0 are available.
|
||||
apiVersion: metallb.io/v1beta1
|
||||
kind: BGPAdvertisement
|
||||
metadata:
|
||||
name: default
|
||||
namespace: metallb-system
|
||||
annotations:
|
||||
argocd.argoproj.io/sync-wave: "1"
|
||||
spec:
|
||||
ipAddressPools:
|
||||
- default-pool
|
||||
aggregationLength: 32
|
||||
Reference in New Issue
Block a user