load-balancer

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
In some situation, like XiaoDu watch, which is sensitive to power consumption, may need to close the TCP-KeepAlive heartbeat message or increase the interval to send TCP-KeepAlive heartbeat message.
Mod_tcp_keepalive can help handle situ

Right now e2e tests handle metallb as a black box, going to inspect only the content of the external FRR containers.
However, there are some parameters (i.e. password, timers) that are not sent on the wire and thus not available for inspection on the other peer.

We unit tests the various segments, but we don't really know if a value we set in config ends up rendered correctly.
It would be nic

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

Expected Behaviour

Correct build status to be shown

Current Behaviour

Add events and logs in key places during service processing, such as allocate and release EIP, GoBGP synchronization Nexthop, Layer2 mode selection Node

The contents of IConfiguration could be very large in some cases, resulting in less than ideal response times for calls to /refresh.

It would be nice if there was a way to prevent the contents from being returned. The toggle should live in IRefreshOptions and the default behavior should be to return contents. If the switch is turned off, a single item should be returned that indicates returni

Add a prometheus exporter! Example outputs:

• Layer 2
• Layer 3
• TCP LoadBalancer
• IPVS LoadBalancer (once @yastij implements it ;)
• Control Pane HA