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

CI runs are hard to analyze.

We could benefit from to a file named after the test:

• all the frr information we dump to the standard output
• the config (and eventually the crds)
• the service definition
• the last logs of the speakers
• the last logs of the controller

And in general any information that could be useful for debugging
An even better option would be to have a folder nam

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

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

I understand from the README and #98 that query parameters are filtered to prevent unwanted overrides of ClickHouse parameters.

However, this also filters parameters starting with param_ which are used to replace placeholders in parametrized queries[^1].
For example SELECT * FROM {table:Identifier} with param_table=some_table.

Is there any security reasons to disallow these parameters

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