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

I didn't see in source code any traces of endpoints for health checks. It usually used by liveness and readiness checks in k8s.
Is this decision made on purpose or this part not implemented yet?

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

We want to monitor the application with AppDynamics, per AppDynamics, in order to monitor it in linux container, it has to be rabbitmq.client v6+, right now the Steeltoe.Messaging.RabbitMQ is v5.1.2.

Change the refrenced package of RabbitMQ.Client from 5.1.2 to 6.2.2

Add a prometheus exporter! Example outputs:

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