MetalLB tells the router that it can route traffic to the service IP via a set of nodes on which the pod runs. Since all the nodes carry the same routing cost, the router selects the route by hashing the network connection details (such as source and destination IPs and the network protocol). This means that all packets belonging to a certain connection are routed to the same node, which is exactly what we need. The network setup I have is pretty straightforward. A switch sits between the router and the Kubernetes nodes. MetalLB gives out the addresses from this set. MetalLB deployment to Kubernetes starts a control pod and as many speaker pods as there are worker nodes. In order to set up MetalLB, I applied this ConfigMap: apiVersion: v1 kind: ConfigMap metadata: namespace: metallb-system name: config data: config: | peers: - peer-address: 192.168.1.1 peer-asn: 64512 my-asn: 64512 address-pools: - name: default protocol: bgp addresses: - 192.168.1.224/27 MetalLB installation is simple and well explained in the documentation, so I’ll focus on the configuration. The peer-address field has the address of the router. I chose both peer-asn (the router) and my-asn (the cluster) number to be the same, indicating that both ends of the route are in the same Autonomous System. The number 64512 is the first “private” ASN, meaning it doesn’t belong to any real AS - it can be compared to a private IP address. The default address pool has the Service addresses that MetalLB can give out as the addresses field. Then the following commands set up BGP configuration and start up the BGP service in the router: configure set protocols bgp 64512 parameters router-id 192.168.1.1 set protocols bgp 64512 neighbor 192.168.1.201 remote-as 64512 set protocols bgp 64512 neighbor 192.168.1.202 remote-as 64512 set protocols bgp 64512 neighbor 192.168.1.203 remote-as 64512 set protocols bgp 64512 neighbor 192.168.1.204 remote-as 64512 set protocols bgp 64512 maximum-paths ibgp 32 commit save exit To configure the EdgeRouter, one has to ssh into the device or open the CLI window from the GUI, because there is no BGP support in the GUI. The configure, commit, save, and exit commands are just the way how the EdgeRouter’s configuration mode is entered and the changes applied. The first real command sets the router-id to 192.168.1.1. The following four commands set each of the Kubernetes worker nodes to be a neighbor to the router. Note that interface names vary from manufacturer to manufacturer and device to device so you may need to do a little detective work if you're not sure (see below for our tip on using Speedtest).The maximum-paths value tells how many potential BGP routing targets there can be. Most of the time, you'll want to at least monitor the Internet interface. If you want to monitor more than one interface (say, both Internet and WiFi), add the device more than once, choosing a different interface each time. You should choose the interface that you'd like PeakHour to monitor. In addition, it might also have a WiFi interface for wireless devices to connect to. For example, your broadband router might have a WAN / Internet Port as well as a number of LAN (local) ports that you plug other devices into. SNMP allows you to choose which network interface to monitor. To add an SNMP device manually, click the Add SNMP Device. on the Search for Devices view, or if you select an existing SNMP target in Preferences and click Edit in Configuration Assistant.įor more information on SNMPv3 security, see this page:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |