Community Weekly Meeting (December 22, 2021)

[juzhiyuan]

Hi, here is the schedule for the coming Weekly Meeting.

Schedule

• Date: on Wednesday, December 22, at 20:00 ~ 21:30 (UTC +8)
• Meeting Link: https://meeting.tencent.com/dm/VLjTH3CU3QVi
• Topics: Please leave your comment below :)

Note

• If you have any questions, please comment below or contact juzhiyuan@apache.org
• Kindly let me know if you need Google Meet or Zoom as communication tools.

Previous Meeting

• Community Weekly Meeting (December 15, 2021) #5786

[juzhiyuan]

For tomorrow's meeting, I just created a doc here: https://docs.qq.com/doc/DTktRakxqaUFFWndz

This doc is in Chinese, please let me know if you prefer using English :)

[juzhiyuan]

Meeting Summary

Doc: Chinese Version
Video: https://www.bilibili.com/video/BV1Ga411r7n9/

Dashboard V3 Proposal

1. Want the list page to display the resource ID since not all operations occur in the Dashboard interface (command line, etc.).
   a. Solution: We could support displaying the ID in Web support to facilitate direct operation.

2. when configuring the plug-in, some plug-ins only support the use of CodeMirror configuration JSON, I hope that the UI can support, through the form to configure. In addition, also hope that each field has a relevant description, otherwise the configuration of a plug-in, you need to use the Dashboard, go through the documentation at the same time.
   a. Solution: Due to historical reasons (schema to UI incompatibility issues), only commonly used plug-ins currently support UI forms, more on the V3 consideration.

3. plug-in market list page is through a card to display the status of plug-ins, plug-ins contain 2 types of status: whether to configure? Is it enabled? currently displaying 2 types of status through the same button on the card, which is not clear to the user.
   a. solution: temporarily change "disabled" to "configured", a better way to put in V3 to consider.

4. apache/apisix - Nacos 2.x has incompatible modifications with 1.x and encounters problems when using gRPC bug: using nacos for service discovery, no support for spring cloud programs? #5815
   a. Solution: feat(nacos): support grpc java #5894

5. Q: Separate the plugin logic from APISIX, APISIX only does pure core logic, so that when upgrading to a new version usually only the plugin is updated.
   a. Solution: Good idea, but the changes are too big, and some plugins are dependent on apisix-core, so the plugins and apisix-core are still one and the same. Apache APISIX provides native forwarding capabilities based on OpenResty, while observability, speed limit and flow limit are extended by the plug-in, which is actually a whole.

6. support LDP for login authentication
   a. Solution: Consider in V3.

7. some forms have incomplete field hint information
   a. Solution: Check which fields are not complete? Fix them.

8. want the Dashboard interface to support Proto configuration
   a. Solution: Support https://apisix.apache.org/docs/apisix/plugins/grpc-transcode/#proto in the interface

9. You want Dashboard to support API versioning and version rollback.
   a. Solution: Consider version rollback capability in V3, and rethink the design of the API versioning product.

KCP

A discussion of Apache APISIX support for the KCP protocol, see #5811

Free Talk

🥳