apisix

Improved or typo fixed.

add new diagram before https://github.com/apache/apisix/blob/master/docs/en/latest/architecture-design/apisix.md#plugin-loading-process

Solution

Issue description

Delete route in apisix dashboard is not work.

once deleted is dose not work, but twice I got this error.

Expected behavior

When I delete the route, the list of this route should not be in the list.

How to Reproduce

just start the dashboard and delet

Issue description

Hi, when I create a new Issue or PR, it's too complex for me to fulfill the contents :)

I find a better example here https://github.com/facebook/docusaurus/issues/new/choose, could we have some ideas from it?

![image](https://user-images.githubuserconten

We tried to build dashboard docker image for ARM in #197 but failed. Since I could build dashboard docker image on m1 so there's nothing to do with the building process itself.

And since it stuck at yarn build, a large chance is free Github Actions machine is lack of memory since we also deploy QEMU to simulate arm environment, as [ref](https://stackoverflow.com/questions/59868448/rpc-error

We already have service monitor for ingress controller (#76), shall we make it available also for main chart?

Actual Behaviour

We have a download page here[1], it supports the latest version of source codes, we could provide more ways to download package 😄

[1] https://apisix.apache.org/downloads

Solution

We support RPM/Docker/Helm ways to get package, we could generate or add their links on the download page.

Issue description

Currently, we have an implicit 60s timeout when running the Go plugin. The common way in Go is to use a Context that will time out after the 60s.

Therefore, we should find a way to introduce Context into plugin runner.

If you are interested in this issue, please discuss your design here before submitting any code. Thanks.

Environment

• APISIX Go Plugin Runn

The log of the Java plug-in is written to the error.log of apisix, which is unreasonable. Because the plug-in itself will generate many logs, the plug-in log is mixed with the apisix log

advice：
The Java plug-in log is printed separately and controlled by the Java plug-in itself