KID-G commented on code in PR #1527:
URL: https://github.com/apache/apisix-website/pull/1527#discussion_r1131924597


##########
blog/en/blog/2023/03/10/release-apache-apisix-3.2.0.md:
##########
@@ -0,0 +1,230 @@
+---
+title: "Release Apache APISIX 3.2.0"
+authors:
+  - name: "Zexuan Luo"
+    title: "Author"
+    url: "https://github.com/spacewander";
+    image_url: "https://github.com/spacewander.png";
+  - name: "Yilia"
+    title: "Technical Writer"
+    url: "https://github.com/Yilialinn";
+    image_url: "https://avatars.githubusercontent.com/u/114121331?v=4";
+keywords: 
+- Apache APISIX
+- LTS
+description: As the first LTS version since the 3.0 version, APISIX 3.2.0 is 
officially released!
+tags: [Community]
+---
+
+> As the first LTS version since the 3.0 version, APISIX 3.2.0 is officially 
released! This release is a significant milestone for the 3.x era to replace 
the 2.x era.
+
+<!--truncate-->
+
+A new series of patch versions will be released based on the 3.2.0 version. As 
usual, many features and plugins are added to optimize the experience of using 
APISIX.
+
+## New feature: service discovery on Layer 4
+
+Only a few gateways support service discovery, and APISIX is one of them. In 
version 3.2.0, APISIX implemented the service discovery on Layer 4. In this 
way, you can also enjoy the convenience of service discovery when using APISIX 
as a TCP/UDP proxy. Like the service discovery on Layer 7, we need to configure 
the address of the service discovery server in `config.yaml` if we want to use 
service discovery:
+
+```
+discovery:
+  nacos:
+    host:
+      - "http://192.168.33.1:8848";
+```
+
+Then configure `discovery_type` and `service_name` on the specific upstream:
+
+```
+$ curl http://127.0.0.1:9180/apisix/admin/stream_routes/1 -H 'X-API-KEY: 
edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
+{
+    "remote_addr": "127.0.0.1",
+    "upstream": {
+        "scheme": "tcp",
+        "discovery_type": "nacos",
+        "service_name": "APISIX-NACOS",
+        "type": "roundrobin"
+    }
+}'
+```
+
+In this way, when accessing stream_routes, the upstream node will obtain it 
from the APISIX-NACOS service of Nacos.
+
+## New plugin: RESTful request to graphQL

Review Comment:
   ```suggestion
   ## New plugin: RESTful request to GraphQL
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to