hscloud/cluster/kube/k0.calico.yaml

# This is the current Calico configuration in k0.hswaw.net.
# Unfortunately, we do not have Calico configured to use CRDs, and instead to
# keep its resources separately from Kubernetes. Thus, this configuration
# cannot be managed by Kubernetes/jsonnet. Instead, it must be applied manially:
#
#     calicoctl apply -f k0.calico.yaml

apiVersion: projectcalico.org/v3
kind: BGPConfiguration
metadata:
  name: default
spec:
  logSeverityScreen: Info
  nodeToNodeMeshEnabled: true
  asNumber: 65003

---

# metallb peer, must be compatible with the metallbc definition in k0.libsonnet.
apiVersion: projectcalico.org/v3
kind: BGPPeer
metadata:
  name: metallb
spec:
  peerIP: 127.0.0.1
  asNumber: 65002

---

# ToR switch peering, must be compatible with the configuration on dcsw01.hswaw.net.
apiVersion: projectcalico.org/v3
kind: BGPPeer
metadata:
  name: dcsw01
spec:
  peerIP: 185.236.240.33
  asNumber: 65001

---

# IP pool that's used by metallb. We mark it as disabled so that Calico doesn't
# allocate Service IPs from it, just allow metallb routes from that pool to
# pass through eBGP (otherwise Calico BIRD filter will filter them out).
# Keep in sync with k0.libsonnet.
apiVersion: projectcalico.org/v3
kind: IPPool
metadata:
  name: public-v4-1
spec:
  cidr: 185.236.240.48/28
  disabled: true
---

# IP pool that's used by metallb. We mark it as disabled so that Calico doesn't
# allocate Service IPs from it, just allow metallb routes from that pool to
# pass through eBGP (otherwise Calico BIRD filter will filter them out).
# Keep in sync with k0.libsonnet.
apiVersion: projectcalico.org/v3
kind: IPPool
metadata:
  name: public-v4-2
spec:
  cidr: 185.236.240.112/28
  disabled: true

---

# IP pool for the service network.
apiVersion: projectcalico.org/v3
kind: IPPool
metadata:
  name: default-ipv4-ippool
spec:
  blockSize: 26
  cidr: 10.10.24.0/21
  ipipMode: CrossSubnet
  natOutgoing: true