load-balancer

Is your feature request related to a problem? Please describe.
rovide a method to test/verify if the configuration is correct. before reload the config.
Like nginx -t

Describe the solution you'd like
Simple command.
After run, print the test/verification result.

Describe alternatives you've considered

Additional context

We did not use it, but it's possible to specify a custom as per peer basis using local-as

Currently, metallb rejects custom localAss if they are not all equal. Using that option, we could match the native behaviour.

Is your feature request related to a problem? Please describe.

This is the logic currently implemented in the main branch:

If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.

Describe the solution you'd like

I want to take the URL check when no header is

Detailed Description of the Problem

Hello

I wrote some script for disabled/enable frontend when related backend status goes DOWN OR UP.

BUT stat shows the frontend status is still OPEN even if I was disabled it.

echo "show stat" | sudo socat unix-connect:/run/haproxy-master.sock stdio

and follow is my tested HAproxy version

root@haproxy1:~# haproxy -v
HAProxy v

Expected Behaviour

Correct build status to be shown

Current Behaviour

What we need

In the case of using openelb as the Kubernetes load balancing implementation, the allocation of openelb external-ip-pool can only be viewed on the terminal interface by accessing Kubernetes resources with kubectl. However, more and more kubernetes users are using specific dashboards to operate and manage clusters or workloads, such as KubeSphere. Therefore, the current usage is n

Description

Currently we don't have any security mechanism for cache for too big payloads.

We should introduce some mechanism to secure that, detect payloads > MAX_SIZE and omit saving them in cache.
However, what would one consider appropriate threshold?

Perhaps the answer should be left to the user to decide.

Describe the bug

A clear and concise description of the bug.
when my asp.net core 3.1 app host in IIS, the url console is 127.0.0.1，so，when i have Multiple instances，the instances name will be the same,such as 127.0.0.1:svaname:port，eureka server think they are a single instance.
i print the console in source code：
![image](https://user-images.githubusercontent.com/6300834/101754289-8ad92

Add a prometheus exporter! Example outputs:

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