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 egctl has any way to delete all objects using just one command， right now I can put all Easegress objects(including HTTPServer、GlobalFilter、NacosServiceRegistry、HTTPPipeline etc) in a file and use just one command egctl object create -f file to create. But for any reason if I change one of these objects especially for local debug，it is very hard for me to apply these new changes(I need to

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

What we need

As we know, the current version of openelb supports both layer2 and bgp modes. This means that either the host's network can span network segments and there must be a switch that supports the bgp protocol, or the host is in a layer 2 network environment, only in this way can users install and use openelb. Therefore, if the swtich in the multiple network segments connecting the ho

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