You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by ju...@apache.org on 2021/11/01 10:31:57 UTC
[apisix-website] branch master updated: docs: translate blogs on
10/2021 (#679)
This is an automated email from the ASF dual-hosted git repository.
juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 7285ebf docs: translate blogs on 10/2021 (#679)
7285ebf is described below
commit 7285ebf53469d55832722d1a3d928ea6c860f6c4
Author: 琚致远 <ju...@apache.org>
AuthorDate: Mon Nov 1 18:31:53 2021 +0800
docs: translate blogs on 10/2021 (#679)
---
website/blog/2021/10/01/openEuler.md | 23 ++-
website/blog/2021/10/09/apisix-ingress-techblog.md | 187 ++++++++++-----------
.../13/celebrating-300-contributors-of-apisix.md | 42 ++---
website/blog/2021/10/14/weekly-report-1014.md | 58 +++----
website/blog/2021/10/18/meetup.md | 61 ++++---
5 files changed, 184 insertions(+), 187 deletions(-)
diff --git a/website/blog/2021/10/01/openEuler.md b/website/blog/2021/10/01/openEuler.md
index b4a6a7c..11c2401 100644
--- a/website/blog/2021/10/01/openEuler.md
+++ b/website/blog/2021/10/01/openEuler.md
@@ -1,34 +1,33 @@
---
-title: "Apache APISIX 社区成员助力 openEuler 发布第一个社区创新版"
+title: Apache APISIX community members help openEuler release first community innovation version
keywords:
- Apache APISIX
- openEuler
- APISIX
- API Gateway
- OpenResty
-- 欧拉
-description: 来自 Apache APISIX 社区的罗泽轩和温铭在 openEuler 9 月 30 日发布的第一个社区创新版（ openEuler 21.09）中，为 OpenResty 迁移工作中做了非常多的贡献，让 OpenResty 可以在欧拉开源操作系统上平稳高效的运行。
+description: Zexuan Luo and Ming Wen from the Apache APISIX community did a lot of work in the first community innovation release of openEuler on September 30 (openEuler 21.09) to migrate OpenResty to run smoothly and efficiently on the Euler open source OS.
tags: [Events]
---
-> 来自 Apache APISIX 社区的[罗泽轩](https://github.com/spacewander)和[温铭](https://github.com/moonming)在 openEuler 9 月 30 日发布的第一个社区创新版（ [openEuler 21.09](https://openeuler.org/) ）中，为 [OpenResty](https://github.com/openresty/openresty) 迁移工作中做了非常多的贡献，让 OpenResty 可以在欧拉开源操作系统上平稳高效的运行。OpenResty 的稳定运行也意味着 [Apache APISIX](https://github.com/apache/apisix) 可以顺畅地运行在 openEuler 系统上，Apache APISIX 底层基于 OpenResty 做了一定开发。
+> [Zexuan Luo](https://github.com/spacewander) and [Ming Wen](https://github.com/moonming) from the Apache APISIX community have done a lot of work in the first community innovation release of openEuler on September 30 ([openEuler 21.09](https://openeuler.org/)), contributed a lot to the [OpenResty](https://github.com/openresty/openresty) migration effort, allowing OpenResty to run smoothly and efficiently on the Euler open source OS. The stable operation of OpenResty also means that [Ap [...]
<!--truncate-->
-让我们一起来认识下这两位社区成员吧！
+Let's get to know these two community members!
-[罗泽轩](https://github.com/spacewander)，Apache APISIX PMC，OpenResty 的核心开发者，git-extras 项目的 Maintainer，擅长 C、Golang 和 Lua，撰写过多篇技术干货，推荐阅读《 [为什么 Apache APISIX 选择 Nginx + Lua 这个技术栈？](https://apisix.apache.org/blog/2021/08/25/Why-Apache-APISIX-chose-Nginx-and-Lua)》《[差之毫厘：etcd 3 完美支持 HTTP 访问？](https://apisix.apache.org/blog/2021/06/30/etcd3-support-HTTP-access-perfectly)》。
+[Zexuan Luo](https://github.com/spacewander), Apache APISIX PMC, core developer of OpenResty, Maintainer of git-extras project, good at C, Golang and Lua, has written many technical articles, recommend reading [Why Why did Apache APISIX choose Nginx + Lua as the technology stack?] (https://apisix.apache.org/blog/2021/08/25/Why-Apache-APISIX-chose-Nginx-and-Lua), "[What's the difference: does etcd 3 support HTTP access perfectly?] (https://apisix.apache.org/blog/2021/06/30/etcd3-support-H [...]
<img src="https://static.apiseven.com/202108/1633068755509-66b85782-ecca-43cc-bbcc-5a7b11cee0f4.png" alt="罗泽轩" style={{width: "200px"}} />
-[温铭](https://github.com/moonming)，Apache Member，Apache APISIX PMC Chair，OpenResty 的核心开发者，前 360 开源技术委员会委员，十余年开发经验。著有极客时间专栏《[OpenResty 从入门到实战](https://time.geekbang.org/column/intro/186)》。
+[Ming Wen](https://github.com/moonming), Apache Member, Apache APISIX PMC Chair, core developer of OpenResty, former member of 360 Open Source Technical Committee, he has more than ten years development experience. He is the author of the Geek Time column "[OpenResty from Introduction to Practice](https://time.geekbang.org/column/intro/186)".
<img src="https://static.apiseven.com/202108/1633068755501-b52403ee-c43a-4da7-9ca7-46bc457da6fa.png" alt="温铭" style={{width: "300px"}} />
-Apache APISIX 从开源第一天就以社区方式成长，Apache APISIX 的小伙伴不仅仅在本社区活跃，还积极参与到其他社区的开源项目中，这正是开源精神的体现，开源不仅仅是开放源代码，更是开放的社区、开放的心态，社区间合作互助，大家一起贡献更好用的开源产品。
+Apache APISIX has been growing as a community since the first day of open source. Apache APISIX partners are not only active in this community, but also actively participate in open source projects in other communities, which is the embodiment of the open source spirit, open source is not only open source code, but also open community, open mind, cooperation and mutual assistance between communities, and we contribute together to better open source products.
-除了两位社区成员，还要多介绍一下 Apache APISIX。 openEuler 第一个社区创新版（21.09）极大丰富了云原生相关的基础设施，[Apache APISIX](https://github.com/apache/apisix)天然拥有云原生的优势，支持裸金属、虚拟机、Kubernetes、ARM64、公有云、混合云等多种部署模式，期待 Apache APISIX 在 openEuler 上应用于更多业务、更多场景。
+In addition to the two community members, I would like to introduce Apache APISIX. openEuler's first community innovation version (21.09) greatly enriches the cloud-native related infrastructure, [Apache APISIX](https://github.com/apache/apisix) naturally has the advantages of cloud-native, supporting Bare metal, virtual machine, Kubernetes, ARM64, public cloud, hybrid cloud and many other deployment modes. We expect Apache APISIX to be applied to more businesses and more scenarios on op [...]
-
+
-## 关于 OpenEuler
+## About OpenEuler
-[openEuler](https://openeuler.org/) 是一个开源、免费的 Linux 发行版平台，通过社区形式与全球开发者共同构建开放、多元和架构包容的软件生态体系。openEuler 21.09 是面向数字基础设施的开源操作系统的第一个社区创新版本，拓展了云计算、边缘计算、嵌入式等场景化的应用。
+[openEuler](https://openeuler.org/) is an open source, free Linux distribution platform that works with developers worldwide to build an open, diverse and architecturally inclusive software ecosystem through a community format. openEuler 21.09 is the first community innovation release of an open source operating system for digital infrastructure that It extends scenario-based applications such as cloud computing, edge computing, and embedded.
diff --git a/website/blog/2021/10/09/apisix-ingress-techblog.md b/website/blog/2021/10/09/apisix-ingress-techblog.md
index 3f2dd07..7c5b3a1 100644
--- a/website/blog/2021/10/09/apisix-ingress-techblog.md
+++ b/website/blog/2021/10/09/apisix-ingress-techblog.md
@@ -1,6 +1,6 @@
---
-title: "保姆级教程，从概念到实践帮你快速上手 Apache APISIX Ingress"
-author: "张晋涛"
+title: A thoughtful tutorial to get started with Apache APISIX Ingress from concept to practice
+author: Jintao Zhang
authorURL: "https://github.com/tao12345666333"
authorImageURL: "https://avatars.githubusercontent.com/u/3264292?v=4"
date: 2021-10-09
@@ -8,191 +8,190 @@ keywords:
- Apache APISIX
- Ingress
- Kubernetes
-- 自定义资源
-description: 本文从理论和实践两个角度，对 Apache APISIX Ingress 进行了详细的描述与讲解
+description: This article describes and explains Apache APISIX Ingress in detail from both theoretical and practical perspectives.
tags: [technology]
---
->作者张晋涛，Apache APISIX Committer、Kubernetes Ingress Nginx Reviewer，多个云原生开源项目的贡献者。
+> Jintao Zhang, Apache APISIX Committer, Kubernetes Ingress Nginx Reviewer, and contributor to several cloud-native open source projects.
<!--truncate-->
-## Apache APISIX Ingress 概览
+## Apache APISIX Ingress Overview
-### Apache APISIX Ingress 定义
+### Apache APISIX Ingress Definition
-在 K8s 生态中，Ingress 作为表示 K8s 流量入口的一种资源，想要让其生效，就需要有一个 Ingress Controller 去监听 K8s 中的 Ingress 资源，并对这些资源进行相应规则的解析和实际承载流量。在当下趋势中，像 Kubernetes Ingress Nginx 就是使用最广泛的 Ingress Controller 实现。
+In the K8s ecosystem, Ingress is a resource that represents the entry point for K8s traffic. To make it effective, an Ingress Controller is needed to listen to the Ingress resources in K8s and resolve the rules and actually carry the traffic for those resources. The most widely used Ingress Controller implementations in today's trends are Kubernetes Ingress Nginx.
-而 APISIX Ingress 则是另一种 Ingress Controller 的实现。跟 Kubernetes Ingress Nginx 的区别主要在于 APISIX Ingress 是以 Apache APISIX 作为实际承载业务流量的数据面。如下图所示，当用户请求到具体的某一个服务/API/网页时，通过外部代理将整个业务流量/用户请求传输到 K8s 集群，然后经过 APISIX Ingress 进行后续处理。
+APISIX Ingress is another implementation of the Ingress Controller. The main difference with Kubernetes Ingress Nginx is that APISIX Ingress uses Apache APISIX as the actual data plane that carries business traffic. As shown in the figure below, when a user requests a specific service/API/web page, the entire business traffic/user request is transferred to the K8s cluster through an external proxy and then processed by APISIX Ingress.
-
+
-从上图可以看到，APISIX Ingress 分成了两部分。一部分是 APISIX Ingress Controller，作为控制面它将完成配置管理与分发。另一部分 APISIX Proxy Pod 负责承载业务流量，它是通过 CRD(Custom Resource Definitions) 的方式实现的。Apache APISIX Ingress 除了支持自定义资源外，还支持原生的 K8s Ingress 资源。
+As you can see from the above diagram, APISIX Ingress is divided into two parts. One part is the APISIX Ingress Controller, which is the control plane that will do the configuration management and distribution. The other part is the APISIX Proxy Pod, which is responsible for carrying business traffic and is implemented by means of CRD (Custom Resource Definitions).
-### Apache APISIX 简述
+### Apache APISIX in a nutshell
-前边我们提到了 APISIX Ingress 是采用 Apache APISIX 作为实际承载业务流量的数据面，那么 Apache APISIX 项目又是做什么的呢？
+We mentioned earlier that APISIX Ingress uses Apache APISIX as the data surface that actually carries business traffic, so what does the Apache APISIX project do?
-
+
-Apache APISIX 是 Apache 基金会旗下的顶级开源项目，也是当前最活跃的开源网关项目。作为一个动态、实时、高性能的开源 API 网关，Apache APISIX 提供了负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。
+Apache APISIX is the top open source project of the Apache Foundation and is currently the most active open source gateway project. As a dynamic, real-time, high-performance open source API gateway, Apache APISIX provides rich traffic management features such as load balancing, dynamic upstream, grayscale publishing, service meltdown, authentication, observability, and more.
-Apache APISIX 可以帮助企业快速、安全地处理 API 和微服务流量，比如限流认证、日志安全功能，以及支持丰富的自定义插件。目前也与很多开源项目如 Apache SkyWalking、Prometheus 等之类的组件进行了相关集成。
+Apache APISIX helps enterprises handle API and microservice traffic quickly and securely with features such as flow-limiting authentication, logging security features, and support for rich custom plug-ins. There are also currently relevant integrations with many open source projects such as Apache SkyWalking, Prometheus and other such components.
## APISIX Ingress vs K8s Ingress Nginx
-因为本人同时参与到了 APISIX Ingress 与 K8s Ingress Nginx 两个项目的开发和维护，所以很多人也会问我，这两个项目做比较的话，到底该如何选择？或者说为什么有了 K8s Ingress Nginx 还要再做 APISIX Ingress。
+Since I am involved in the development and maintenance of both APISIX Ingress and K8s Ingress Nginx, many people ask me how to choose between these two projects. Or why do you want to do APISIX Ingress when you have K8s Ingress Nginx.
-### 配置层面
+### Configuration level
-在 APISIX Ingress 中，我们增加了一些丰富且灵活的配置，比如通过单个配置文件去实现灰度部署。但在 K8s Ingress Nginx 中去实现如上效果的话，最少也需要有两个 Ingress 资源文件才可以完成。
+In APISIX Ingress, we have added some rich and flexible configurations, such as grayscale deployment through a single configuration file. However, in K8s Ingress Nginx, you need at least two Ingress resource files to achieve the above effect.
-### 丰富度
+### Richness
-在丰富度上，由于 Apache APISIX 本身的自带功能丰富且允许多种插件扩展使用，所以使用 APISIX Ingress 就可以省去自己额外配置功能的繁琐步骤，可以将更多的时间投入到实际开发中。
+In terms of richness, because Apache APISIX is feature-rich and allows for multiple plugins, using APISIX Ingress eliminates the need to configure additional features yourself, allowing you to spend more time on actual development.
-### 架构分离
+### Architecture separation
-APISIX Ingress 采用了数据面与控制面的分离架构，所以用户可以选择将数据面部署在 K8s 集群内部/外部。但 K8s Ingress Nginx 是将控制面和数据面放在了同一个 Pod 中，如果 Pod 或控制面出现一点闪失，整个 Pod 就会挂掉，进而影响到业务流量。
+APISIX Ingress uses a separate architecture for the data plane and control plane, so users can choose to deploy the data plane inside/outside the K8s cluster. However, K8s Ingress Nginx puts the control plane and the data plane in the same Pod, so if something happens to the Pod or the control plane, the whole Pod will hang, which will affect business traffic.
-这种架构分离，给用户提供了比较方便的部署选择，同时在业务架构调整场景下，也方便进行相关数据的迁移与使用。
+This architectural separation gives users a more convenient deployment option and facilitates data migration and usage in business architecture adjustment scenarios.
-## APISIX Ingress 特性详解
+## APISIX Ingress Features Explained
-由于 Apache APISIX 是一个全动态的高性能网关，所以在 APISIX Ingress 自身就支持了全动态，包括路由、SSL 证书、上游以及插件等等。
+Since Apache APISIX is a fully dynamic, high-performance gateway, APISIX Ingress itself supports full dynamics, including routing, SSL certificates, upstream, plug-ins, and more.
-同时 APISIX Ingress 还具有以下特性：
+APISIX Ingress also has the following features.
-* 支持 CRD，更容易理解声明式配置；同时状态检查可保证快速掌握声明配置的同步状态
-* 支持高级路由匹配规则以及自定义资源，可与 Apache APISIX 官方 50 多个插件 & 客户自定义插件进行扩展使用
-* 支持 K8s 原生 Ingress 配置
-* 支持流量切分
-* 支持 gRPC plaintext 与 TCP 4 层代理
-* 服务自动注册发现，无惧扩缩容
-* 更灵活的负载均衡策略，自带健康检查功能
+* CRD support for easier understanding of declarative configurations; while state checking ensures quick access to the synchronized state of declarative configurations
+* Support for advanced route matching rules and custom resources, which can be extended with more than 50 official Apache APISIX plug-ins & customer-defined plug-ins
+* Support for K8s native Ingress configuration
+* Support for traffic slicing
+* Support for gRPC plaintext and TCP Layer 4 proxy
+* Automatic service registration and discovery, no fear of scaling up or down
+* More flexible load balancing policy with health check function
-以下我们将从 CRD 与自定义资源层面进行详细的介绍。
+The following is a detailed introduction to CRD and custom resources.
-### CRD 扩展
+### CRD Extensions
-在前面的介绍中我们提到了 CRD，那么 APISIX Ingress 是如何使用 CRD 扩展的？
+We mentioned CRD in the previous introduction, but how does APISIX Ingress use CRD extensions?
-
+
-从用户层面来看，当 Client 发起请求，到达 Apache APISIX 后，会直接把相应的业务流量传输到后端（如 Service Pod），从而完成转发过程。此过程不需要经过 Ingress Controller，这样做可以保证一旦有问题出现，或者是进行变更、扩缩容或者迁移处理等，都不会影响到用户和业务流量。
+At the user level, when a request is made by a Client and arrives at Apache APISIX, the corresponding service traffic is directly transferred to the backend (e.g., Service Pod), thus completing the forwarding process. This process does not need to go through the Ingress Controller, which can ensure that if there are problems, or changes, expansion and contraction or migration processing, it will not affect the users and business traffic.
-同时在配置端，用户通过 kubectl apply，可将自定义 CRD 配置应用到 K8s 集群。Ingress Controller 会持续 watch 这些资源变更，来将相应配置应用到 Apache APISIX。
+On the configuration side, users can apply custom CRD configurations to K8s clusters via kubectl apply, and Ingress Controller will continuously watch these resource changes to apply the corresponding configurations to Apache APISIX.
-### 自定义资源
+### Custom resources
-APISIX Ingress 目前已经支持的自定义资源主要是以下 5 类，涉及到路由、上游、消费者、证书相关和集群公共配置的相关类别。
+APISIX Ingress currently supports the following 5 categories of custom resources related to routing, upstream, consumer, certificate related and cluster public configuration.
-#### APISIX Route（路由）
+#### APISIX Route
-自定义资源 APISIX Route 中 `spec` 属性的顶级配置是 `http`。但其实 `spec` 是同时支持两种配置的，一种是下图示例的 `spec.http`，主要用于 7 层代理；另一种是 `spec.stream`，用于 4 层代理。在配置文件中，我们首先为其自定义了一项规则，即 match 下的相关参数。
+The top-level configuration for the `spec` attribute in the custom resource APISIX Route is `http`. But actually `spec` supports both configurations, `spec.http` as in the example below, which is mainly used for Layer 7 proxies, and `spec.stream`, which is used for Layer 4 proxies. In the configuration file, we first customize a rule for it, namely the relevant parameter under match.
-如上图后端配置示例使用了同一个 Service，实际使用中大家根据场景进行调整即可。需要注意的是，`weight` 属性是用来配置相关 Service 权重。通过以上配置，从而实现一套完整的路由自定义资源。
+As the above back-end configuration example uses the same Service, you can adjust it according to the scenario in actual use. Note that the `weight` attribute is used to configure the relevant service weight. With the above configuration, a complete set of routing customization resources can be implemented.
-#### APISIX Upstream（上游）
+#### APISIX Upstream (Upstream)
-在配置 APISIX Upstream 时，需要注意 `name` 的内容要与 K8s 集群的 Service 保持一致，这样可以保证后续 APISIX Ingress Controller 准确匹配其相应流量。
+When configuring APISIX Upstream, you need to pay attention to the content of `name` to be consistent with the Service of K8s cluster, so as to ensure that the subsequent APISIX Ingress Controller can accurately match its corresponding traffic.
-在配置文件中，`spec.loadbalancer` 主要负责负载均衡策略的设置，有多种策略模式可供选择。`spec.schem`e 则是协议类型的配置，目前只支持 HTTP 和 gRPC 协议。`spec.healthCheck` 主要是对健康检查功能进行设置，比如设置其活跃状态、生效协议与路径和最终反馈等参数配置。
+In the configuration file, `spec.loadbalancer` is mainly responsible for setting the load balancing policy, and there are various policy modes to choose from. `spec.schem`e is for the protocol type configuration, currently only HTTP and gRPC protocols are supported. `spec.healthCheck` is mainly for setting the health check function, such as setting its active status, effective protocol and path and final feedback and other parameters configuration.
-#### APISIX Consumer（消费者）
+#### APISIX Consumer
-在 APISIX Consumer 配置中，主要是增加了认证相关的功能，比如 `spec.authParameter`，目前该配置参数支持 `BasicAuth` 与 `KeyAuth` 这两种比较常见的认证类型。
+The APISIX Consumer configuration mainly adds authentication-related features, such as `spec.authParameter`, which currently supports `BasicAuth` and `KeyAuth`, the two more common types of authentication.
-通过 `value` 可直接去配置相关的 `username` 和 `password`，或者直接使用 `secret` 进行配置，相比前者的明文配置会更安全一些。
+You can configure the associated `username` and `password` directly with `value`, or directly with `secret`, which is more secure than the plaintext configuration of the former.
-#### APISIX TLS（证书）
+#### APISIX TLS (certificate)
-APISIX TLS 主要是为了进行证书的管理。如示例所示，用户可以通过 `hosts` 来配置多个域名，`secret` 下的参数就是对应的配置证书。
+APISIX TLS is mainly for certificate management. As the example shows, users can configure multiple domains via `hosts`, and the parameters under `secret` are the corresponding configuration certificates.
-同时 APISIX TLS 还配有 `spec.client`，用于进行 mTLS 双向认证的配置。
+Apache APISIX TLS also comes with `spec.client` for configuring mTLS two-way authentication.
-#### APISIX Config 相关
+#### APISIX Config
-关于自定义资源支持的 Config 类型我们会从两个方面进行描述。
+The Config types supported by custom resources are described in two ways.
-一种是 APISIX Cluster Config，它主要用于一些通用配置。目前支持在 K8s 或者 Apache APISIX 中全局使用 Prometheus 插件/全局配置 SkyWalking，后续开发中也会去增加一些其他的通用配置。
+One type is APISIX Cluster Config, which is mainly used for some generic configurations. Currently it supports global use of Prometheus plug-in/global configuration SkyWalking in K8s or Apache APISIX, and we will add some other generic configurations in subsequent development.
-另一种就是我们现在正在 PR 中的 [APISIX Plugin Config](https://github.com/apache/apisix-ingress-controller/pull/689)。大家如果感兴趣的话，也可以点击链接来一起参与讨论。Plugin Config 主要是将通用的插件配置统一集合在一起，比如一些同样的配置，用户就可以通过 APISIX Plugin Config 同时应用在多个路由当中，省去了额外多项独立配置的繁琐步骤。
+Another one is the [APISIX Plugin Config](https://github.com/apache/apisix-ingress-controller/pull/689) that we are currently working on in PR. If you are interested, you can also click the link to join the discussion. Plugin Config is mainly a unified collection of common plug-in configurations, for example, some of the same configuration, users can use APISIX Plugin Config to apply to multiple routes at the same time, eliminating the tedious steps of multiple independent configurations.
-## APISIX Ingress 上手实践
+## APISIX Ingress Hands-On Practice
-目前大家可以通过 [Helm Charts](https://github.com/apache/apisix-helm-chart) 的方式来进行 APISIX Ingress 的部署。通过一条命令，就可以同时把 Apache APISIX 以及 APISIX Ingress，包括 Apache APISIX 所需要用到的 etcd 全部部署好，步骤非常简单。
+Currently, you can deploy APISIX Ingress via [Helm Charts](https://github.com/apache/apisix-helm-chart). You can deploy both Apache APISIX and APISIX Ingress, including the etcd required for Apache APISIX, with a single command, which is very simple.
-
+
-### 实践场景一：流量切分
+### Practice Scenario 1: Traffic Segmentation
-通过使用 APISIX Ingress 可以实现按比例进行流量切分的效果，具体操作如下：
+By using APISIX Ingress, you can achieve the effect of proportional traffic slicing, as follows.
-#### 步骤一：配置 APISIX Upstream
+#### Step 1: Configure APISIX Upstream
-
+
-#### 步骤二：配置 APISIX Route
+#### Step 2: Configure APISIX Route
-通过在 `backends` 中去配置 `subset` 和 `weight`，来实现用户请求流量进入时的分流。如下图示例就是 90% 的流量会进入到 v1 中，10% 的流量进入到 v2 中。
+Configure `subset` and `weight` in `backends` to split the incoming user request traffic. The example below shows that 90% of the traffic will go to v1 and 10% of the traffic will go to v2.
-
+
-通过以上两步，就可以十分方便地按比例进行流量切分，实现类似灰度发布等场景需求。
-更多具体操作细节也可参考：[Apache APISIX Ingress Controller 中的流量切分](https://www.apiseven.com/zh/blog/traffic-split-in-apache-apisix-ingress-controller)。
+With the above two steps, it is very easy to slice and dice traffic proportionally to achieve scenarios like grayscale publishing.
+For more details, please refer to: [Traffic Segmentation in Apache APISIX Ingress Controller](https://www.apiseven.com/zh/blog/traffic-split-in-apache-apisix-ingress-controller).
-### 实践场景二：配置认证
+### Practice Scenario 2: Configuring Authentication
-如果想在 APISIX Ingress 中为某些路由配置 Basic Auth，可以参考如下操作：
+If you want to configure Basic Auth for certain routes in APISIX Ingress, you can refer to the following actions.
-#### 步骤一：创建 APISIX Consumer 资源
+#### Step 1: Create APISIX Consumer resource
-如前文所提到的，可以在 APISIX Consumer 配置中增加 `basicAuth`，并为其指定用户名和密码。
+As mentioned earlier, you can add `basicAuth` to the APISIX Consumer configuration and specify a username and password for it.
-
+
-#### 步骤二：配置 APISIX Route，增加认证相关参数
+#### Step 2: Configure the APISIX Route and add authentication-related parameters
-在自定义资源 APISIX Route 中，通过在后端添加 `authenticatio`n，将其开启并指定认证类型即可。
+In the custom resource APISIX Route, simply turn it on and specify the authentication type by adding `authenticatio`n to the backend.
-
+
-通过以上步骤，就可以实现使用 Consumer 去完成相关配置认证。
+With the above steps, it is possible to use Consumer to complete the relevant configuration authentication.
-### 实践场景三：K8s 资源扩展
+### Practice Scenario 3: K8s Resource Extensions
-正如我们在开头提到过的，APISIX Ingress 不仅支持自定义资源，还同时支持 K8s 原生的 Ingress 资源。
+As we mentioned at the beginning, APISIX Ingress supports not only custom resources, but also K8s native Ingress resources.
-
+
-如上图是 K8s Ingress 资源。通常情况下如果想要在资源上做 rewrite，可以通过增加 annotation 配置属性。这样当用户携带 `httpbin.org` 请求时，就可以通过路径 /sample 将它重定向到 /ip。
+The image above shows the K8s Ingress resource. Normally if you want to do rewrite on a resource, you can add annotation configuration attributes. This way when the user carries the `httpbin.org` request, it can be redirected to /ip via the path /sample.
-当上述需求使用 APISIX Ingress 时，只需在 Ingress 增加一个 `kubernetes.io/ingress.class: apisix`，去指定 APISIX Ingress Controller 去监听这个资源，同时通过配置 `k8s.apisix.apache.org/rewrite-target: "/ip"`，就可以完成重定向到 /ip 路径。
+When the above requirement uses APISIX Ingress, simply add a `kubernetes.io/ingress.class: apisix` to Ingress to specify the APISIX Ingress Controller to listen to this resource, and configure `k8s.apisix.apache.org/rewrite-target: "/ip"` to complete the redirection to the /ip path.
-
+
-以上示例只是目前 APISIX Ingress 对于原生 K8s Ingress 支持的一种方式，更多示例大家可以查看[具体文档](https://apisix.apache.org/docs/ingress-controller/practices/proxy-the-httpbin-service-with-ingress)进行参考使用。
+The above example is just one of the ways APISIX Ingress currently supports native K8s Ingress, for more examples you can check the [specific documentation](https://apisix.apache.org/docs/ingress-controller/practices/proxy-the-httpbin-service-with-ingress) for reference and use.
-## 未来规划
+## Future Plans
-之后 APISIX Ingress 将会继续在功能与生态上进行更新，目前阶段已经完成了 [APISIX Ingress 与 Cert-manager 集成](https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/practices/manage-certificates-with-cert-manager.md)，后续将逐步实现以下目标：
+APISIX Ingress will continue to be updated in terms of functionality and ecology, and the current phase has been completed [APISIX Ingress and Cert-manager integration](https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/practices/manage-certificates-with-cert-manager.md), and the following goals will be achieved step by step.
-1. 完成 Kubernetes V1.22+ 与 CRD V1 版本的适配支持（已经完成，即将在 APISIX Ingress V1.3 版本 中发布）
-2. 支持 Gateway API（预计在 Q4 阶段实现）
-3. 扩展新架构，以便于用户在不需要使用 etcd 的情况下，可以正常使用 APISIX Ingress
-4. 丰富产品生态，扩展 APISIX Ingress 社区
+1. complete Kubernetes V1.22+ and CRD V1 version adaptation support (completed, soon to be released in APISIX Ingress V1.3 version)
+2. support for Gateway API (expected in Q4)
+3. extend the new architecture to allow users to use APISIX Ingress without the need to use etcd
+4. enrich the product ecology and expand the APISIX Ingress community
-最后也希望大家能够多多地参与到项目中来，比如每两周的周三下午 2 点都会有一次 APISIX Ingress 社区会议，会跟大家同步一下当前的项目进展或者遇到的问题。大家可以持续关注 Apache APISIX 视频号，届时可以直接参与社区会议直播。
+Finally, we hope you can participate in the project more often, for example, there will be an APISIX Ingress community meeting every two weeks on Wednesday at 2 pm, and we will synchronize the current progress of the project or the problems we encountered. Keep an eye on the Apache APISIX video to participate in the live community meetings.
-[点此查看](https://github.com/apache/apisix-ingress-controller/issues/614)更多关于 APISIX Ingress 社区会议细节。
+[Click here](https://github.com/apache/apisix-ingress-controller/issues/614) for more details about the APISIX Ingress community meetings.
diff --git a/website/blog/2021/10/13/celebrating-300-contributors-of-apisix.md b/website/blog/2021/10/13/celebrating-300-contributors-of-apisix.md
index 37d1038..cff87d4 100644
--- a/website/blog/2021/10/13/celebrating-300-contributors-of-apisix.md
+++ b/website/blog/2021/10/13/celebrating-300-contributors-of-apisix.md
@@ -1,53 +1,53 @@
---
-title: "Apache APISIX 社区新里程碑——全球贡献者突破 300 位！"
-author: "Apache APISIX 社区"
+title: New milestone for the Apache APISIX community - over 300 contributors worldwide!
+author: Apache APISIX
date: 2021-10-13
keywords:
- Apache APISIX
- contributor
- milestone
-description: Apache APISIX 社区达成新的里程碑，与 Apache APISIX 相关的项目全球贡献者突破 300 位！
+description: The Apache APISIX community has reached a new milestone, surpassing 300 contributors worldwide to projects related to Apache APISIX!
tags: [Events]
---
->Apache APISIX 社区达成新的里程碑，与 Apache APISIX 相关的项目全球贡献者突破 300 位！ 距离 Apache APISIX 主库达到 [200 位贡献者里程碑](https://apisix.apache.org/blog/2021/07/06/celebrate-200-contributors/)，**仅仅间隔 3 个月**！感谢社区贡献者们在代码、文档、运营等方方面面做出的卓越贡献。
+> The Apache APISIX community has reached a new milestone of 300 contributors worldwide to projects related to Apache APISIX! Only 3 months have passed since the Apache APISIX main repository reached the [200 contributor milestone](https://apisix.apache.org/blog/2021/07/06/celebrate-200-contributors/)! Thank you to the community contributors for their outstanding contributions in all aspects of code, documentation, operations, and more.
<!--truncate-->
-ps：推荐阅读《[贡献者，是衡量开源项目的金指标](https://apisix.apache.org/zh/blog/2021/08/14/contributors-the-golden-metric-of-openSource-projects-en)》，[贡献者趋势图](https://github.com/api7/contributor-graph)
+PS: Recommend reading "[Contributors, the golden metric of open source projects](https://apisix.apache.org/zh/blog/2021/08/14/contributors-the-golden-metric-of-openSource-projects-en), [Contributor trends graph](https://github.com/api7/contributor-graph)
-2020 年 1 月 Apache APISIX 发布了 1.0 版本，这是 Apache APISIX 第一个生产版本。上月底 Apache APISIX 发布了最新的版本 [2.10.0](https://apisix.apache.org/zh/blog/2021/09/29/release-apache-apisix-2.10/)，这是 Apache APISIX 第 24 个版本，Apache APISIX 社区保持快速且稳定的节奏，**每月都会发布一个新版本**。Apache APISIX 的每一次讨论、每一个 PR、每一个里程碑都离不开各位贡献者的参与。
+In January 2020 Apache APISIX released version 1.0, the first production version of Apache APISIX. Late last month Apache APISIX released the latest version [2.10.0](https://apisix.apache.org/zh/blog/2021/09/29/release-apache-apisix-2.10/), which is the 24th release of Apache APISIX. The Apache APISIX community maintains a fast and steady pace, with **a new release every month**. Every discussion, every PR, and every milestone of Apache APISIX is dependent on the participation of its con [...]
-成为 Apache APISIX 贡献者没有门槛，在 Apache APISIX 社区不只包含代码方面的贡献，还有文档、测试、设计、制作视频等。在 Github 上提 PR 或 Issue，参与邮件列表的讨论，通过直播分享、在交流群帮助大家解决问题、参加 Meetup，都是参与到社区的途径。欢迎大家加入到 Apache APISIX 社区！
+There is no barrier to becoming an Apache APISIX contributor, and the Apache APISIX community includes not only contributions of code, but also documentation, testing, design, making videos, and more. Raising PRs or issues on Github, participating in discussions on mailing lists, sharing via live streams, helping people solve problems in networking groups, and attending Meetups are all ways to get involved in the community. Welcome to the Apache APISIX community!
-## 社区活动
+## Community Events
-Apache APISIX 社区非常活跃，贡献者们每月都会组织活动，帮助大家更好地了解和应用 Apache APISIX。
+The Apache APISIX community is very active, and contributors organize monthly events to help people better understand and apply Apache APISIX.
### Apache APISIX Meetup
-2021 年 Apache APISIX 举办了多场线上线下 Meetup ，由 Apache APISIX PMC 成员、Committer、Contributor 和企业技术专家分享 Apache APISIX 的最佳实践。
-欢迎大家关注 [Apache APISIX bilibili](https://space.bilibili.com/551921247)，观看往期回顾内容。
+2021 Apache APISIX hosts several offline and online Meetups with Apache APISIX PMC members, Committers, Contributors, and enterprise technologists to share best practices for Apache APISIX.
+Follow [Apache APISIX bilibili](https://space.bilibili.com/551921247) for past recaps.
-### Apache APISIX Ingress 线上讨论
+### Apache APISIX Ingress Online Discussion
-Apache APISIX Ingress 项目每两周举办一次线上讨论，大家一同讨论各个 PR、issue，分享最佳实践、对 Ingress 的见解和设计思路，可查看 [issue](https://github.com/apache/apisix-ingress-controller/issues/614) 获取线上会议地址，点击 [bilibili 视频链接](https://space.bilibili.com/551921247)观看往期回顾内容。
+The Apache APISIX Ingress project hosts bi-weekly online discussions to discuss PRs, issues, share best practices, insights and design ideas for Ingress, see [issues](https://github.com/apache/apisix-ingress-controller/issues/614) for the online meeting address, and [bilibili video link](https://space.bilibili.com/551921247) for a recap of past issues.
### Weekly Report
-汇总每双周 Apache APISIX 项目功能开发、Bug 修复、社区活动、实践案例等内容，帮助大家更快了解 Apache APISIX 最新进展。
-在 Apache APISIX 官网点击 Blog 选择 Events tag 即可查看双周 Weekly report。
+This is a bi-weekly summary of Apache APISIX project features, bug fixes, community events, case studies, and more, to help you get up to speed on the latest developments in Apache APISIX.
+You can view the bi-weekly Weekly report by clicking Blog and selecting Events tag on the Apache APISIX official website.
-往期推荐：
+Past recommendations.
-- [社区周报｜新晋 committer 两位，功能亮点更新进行中](https://apisix.apache.org/zh/blog/2021/09/15/weekly-report)
-- [Apache APISIX 社区周报 ｜ 2021 8.23-8.29](https://apisix.apache.org/zh/blog/2021/08/30/weekly-report)
-- [Apache APISIX 社区周报 ｜ 2021 8.16-8.22](https://apisix.apache.org/zh/blog/2021/08/23/weekly-report)
+- [Community Weekly Report｜Two new committers, feature highlights update in progress](https://apisix.apache.org/zh/blog/2021/09/15/weekly-report)
+- [Apache APISIX Community Weekly Report ｜ 2021 8.23-8.29](https://apisix.apache.org/zh/blog/2021/08/30/weekly-report)
+- [Apache APISIX Community Weekly Report ｜ 2021 8.16-8.22](https://apisix.apache.org/zh/blog/2021/08/23/weekly-report)
-你希望 Apache APISIX 社区举办什么活动？或者想成为某个活动的组织者/志愿者，欢迎在[邮件列表](https://apisix.apache.org/zh/docs/general/subscribe-guide)讨论！
+What kind of events do you want the Apache APISIX community to organize? Or want to be an organizer/volunteer for an event, feel free to discuss it on the [mailing list](https://apisix.apache.org/zh/docs/general/subscribe-guide)!
-**社区大于代码**是 the Apache Way 中非常重要的准则，让我们一起秉承 the Apache Way，建设 Apache APISIX 以及 Apache APISIX 周边生态。Apache APISIX 社区，感恩有你；Apache APISIX 社区，也期待更多小伙伴加入。
+**The Apache APISIX community is thankful to have you, and we are looking forward to more people joining the Apache APISIX community. The Apache APISIX community is grateful to have you.
diff --git a/website/blog/2021/10/14/weekly-report-1014.md b/website/blog/2021/10/14/weekly-report-1014.md
index fc83254..b19487d 100644
--- a/website/blog/2021/10/14/weekly-report-1014.md
+++ b/website/blog/2021/10/14/weekly-report-1014.md
@@ -1,67 +1,67 @@
---
-title: "社区周报｜10.1-10.14 功能亮点更新进行中"
+title: Community Weekly｜10.1-10.14 Feature Highlight Updates in Progress
keywords:
- Apache APISIX
-- 社区周报
+- Community Weekly
- APISIX
- API Gateway
-- 贡献者
-description: “独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展，方便大家参与到 Apache APISIX 社区中来。
+- Contributor
+description: The Apache APISIX Community Weekly Newsletter hopes to help community members better understand the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
tags: [Events]
---
-> 从 10.1 到 10.14, 有 27 位开发者为 Apache APISIX 提交了 67 个 commits。感谢这些小伙伴为 Apache APISIX 添砖加瓦，是你们的无私付出，让 Apache APISIX 项目变得更好！
+> From 10.1 to 10.14, 27 developers have committed 67 commits to Apache APISIX. Thank you to these folks for making the Apache APISIX project better with your selfless efforts!
<!--truncate-->
-## 导语
+## Introduction
-Apache APISIX 从开源第一天就以社区方式成长，迅速成为全世界最活跃的开源 API 网关项目。这些成就，离不开社区小伙伴们的共同奋斗。
+Apache APISIX has grown as a community since the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements could not have been achieved without the joint efforts of our community partners.
-“独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展，方便大家参与到 Apache APISIX 社区中来。
+"If you want to go fast, go alone. If you want to go far, go together", Apache APISIX Community Weekly Report hopes to help community members better grasp the weekly progress of the Apache APISIX community and facilitate your participation in the Apache APISIX community.
-我们还整理了一些适合新来社区的小伙伴们参加的 issue！感兴趣的同学们，走过路过不要错过！
+We've also put together some issues for those new to the community!
-## 贡献者统计
+## Contributor statistics
-
+
-
+
## Good first issue
### Issue #5165
-**链接**：https://github.com/apache/apisix/issues/5165
+**Link**: https://github.com/apache/apisix/issues/5165
-**问题描述**：
+**Problem Description**:
-- 当浏览器跨域发布然后显示 CORS error 时，`wolf-rbac` 插件的登录 `url/apisix/plugin/wolf-rbac/login` 会返回 `json` 格式，但是 `header` 给出的内容类型是 `text/plain`，请修改插件登录后的内容类型为 `application/json`。
+- When a browser publishes across domains and then displays a CORS error, the login for the `wolf-rbac` plugin `url/apisix/plugin/wolf-rbac/login` returns `json` format, but the `header` gives a content type of `text/plain`, please change the content type to `application/json` after the plugin login.
-- `wolf-rabc` 的登录 `uri/apisix/plugin/wolf-rbac/login` 会失去添加头的 CORS 插件。
+- The login for `wolf-rabc` `uri/apisix/plugin/wolf-rbac/login` will lose the CORS plugin with the added header.
### Issue #5192
-**链接**：https://github.com/apache/apisix/issues/5192
+**Link**: https://github.com/apache/apisix/issues/5192
-**问题描述**：安装 APISIX 依赖的时候，不同的 Linux 发行版会有不同的执行。是否可以将这些不同的执行合并到 “install-dependencise.sh” 中，这样用户在安装依赖时会更加方便。
+**Problem Description**: When installing APISIX dependencies, different Linux distributions will have different executions. Is it possible to merge these different executions into "install-dependencise.sh" to make it easier for users to install dependencies?
-## 本周功能特性亮点
+## Feature highlights of the week
-- [Dashboard 支持配置 Service 中 host 字段提供路由默认值](https://github.com/apache/apisix-dashboard/pull/2149)（贡献者：[bzp2010](https://github.com/bzp2010)）
+- [Dashboard support for configuring the host field in Service to provide routing defaults](https://github.com/apache/apisix-dashboard/pull/2149) (Contributor: [bzp2010](https://github.com/ bzp2010))
-- [APISIX 支持测试配置文件](https://github.com/apache/apisix/pull/5171)（贡献者：[nic-chen](https://github.com/nic-chen)）
+- [APISIX support test profile](https://github.com/apache/apisix/pull/5171) (Contributor: [nic-chen](https://github.com/nic-chen))
-- [APISIX 新增 ldap-auth 插件](https://github.com/apache/apisix/pull/3894)（贡献者：[jp-gouin](https://github.com/jp-gouin)）
+- [APISIX adds ldap-auth plugin](https://github.com/apache/apisix/pull/3894) (Contributor: [jp-gouin](https://github.com/jp-gouin))
-## 本周博文推荐
+## Recommended blog posts for this week
-- [Apache APISIX 社区新里程碑——全球贡献者突破 300 位！](https://apisix.apache.org/zh/blog/2021/10/13/celebrating-300-contributors-of-apisix)：
+- [New milestone for the Apache APISIX community - topping 300 contributors worldwide!] (https://apisix.apache.org/zh/blog/2021/10/13/celebrating-300-contributors-of-apisix).
- Apache APISIX 社区达成新的里程碑，与 Apache APISIX 相关的项目全球贡献者突破 300 位！ 距离 Apache APISIX 主库达到 200 位贡献者里程碑，仅仅间隔 3 个月！感谢社区贡献者们在代码、文档、运营等方方面面做出的卓越贡献。
+ The Apache APISIX community has reached a new milestone, surpassing 300 global contributors to projects related to Apache APISIX! Just 3 months after the Apache APISIX main repository reached the 200 contributor milestone! Thank you to our community contributors for their outstanding contributions in all aspects of code, documentation, operations, and more.
-- [Apache APISIX 社区成员助力 openEuler 发布第一个社区创新版](https://apisix.apache.org/zh/blog/2021/10/01/openEuler)
+- [Apache APISIX community members help openEuler release first community innovation version](https://apisix.apache.org/zh/blog/2021/10/01/openEuler)
- 来自 Apache APISIX 社区的罗泽轩和温铭在 openEuler 9 月 30 日发布的第一个社区创新版（ openEuler 21.09 ）中，为 OpenResty 迁移工作中做了非常多的贡献，让 OpenResty 可以在欧拉开源操作系统上平稳高效的运行。OpenResty 的稳定运行也意味着 Apache APISIX 可以顺畅地运行在 openEuler 系统上，Apache APISIX 底层基于 OpenResty 做了一定开发。
+ Zexuan Luo and Ming Wen from the Apache APISIX community contributed to the first community innovation release of openEuler (openEuler 21.09) on September 30, which allowed OpenResty to run smoothly and efficiently on the Euler open source operating system. The stable operation of OpenResty also means that Apache APISIX can run smoothly on the openEuler system, and the underlying Apache APISIX is based on OpenResty for some development.
-- [Apache APISIX 2.10.0 正式发布，带来第一个 LTS 版本！](https://apisix.apache.org/zh/blog/2021/09/29/release-apache-apisix-2.10)
+- [Apache APISIX 2.10.0 is released, bringing the first LTS version!] (https://apisix.apache.org/zh/blog/2021/09/29/release-apache-apisix-2.10)
- Apache APISIX 2.10 版本正式发布！🎉 这是 Apache APISIX 首个 LTS 版本，同时支持 10+ 个新功能和新插件。快速阅读了解 2.10 版本的新特性吧！
+ Apache APISIX version 2.10 is officially released! 🎉 This is the first LTS release of Apache APISIX, with support for 10+ new features and new plugins. Have a quick read about the new features in version 2.10!
diff --git a/website/blog/2021/10/18/meetup.md b/website/blog/2021/10/18/meetup.md
index b30a528..a7ca86c 100644
--- a/website/blog/2021/10/18/meetup.md
+++ b/website/blog/2021/10/18/meetup.md
@@ -1,66 +1,65 @@
---
-title: 直播预告 | Apache APISIX × Apache SkyWalking 线上分享
+title: Webinar | Apache APISIX × Apache SkyWalking Online Meetup
keywords:
- Apache APISIX
- Apache SkyWalking
- Meetup
-- 分享
-description: 10 月 23 日，Apache APISIX 社区联合 Apache SkyWalking 社区为大家带来线上分享。
+description: On October 23rd, the Apache APISIX community is joining forces with the Apache SkyWalking community to bring you an online sharing session.
tags: [Events]
---
-> 10 月 23 日，Apache APISIX 社区联合 Apache SkyWalking 社区为大家带来线上分享，快来看看有哪些精彩的议题吧。
+> On October 23rd, the Apache APISIX community is joining forces with the Apache SkyWalking community to bring you an online sharing session.
<!--truncate-->
-## 分享议题
+## Sharing Topics
-### Apache APISIX 可观测性介绍
+### Introduction to Apache APISIX Observability
-#### 分享嘉宾
+#### Sharing Guests
-庄浩潮，Apache APISIX Contributor，Apache SkyWalking Committer & PMC 成员。
+Haochao Zhuang, Apache APISIX Contributor, Apache SkyWalking Committer & PMC member.
-#### 议题详情
+#### Topic Details
-Apache APISIX 相对原生 Nginx 有比较完善可观测性能力，将介绍 Apache APISIX 已有的监控手段和能力。以及与 Apache SkyWalking 集成之后，有哪些功能的增强，将来还会带哪些新特性。一起期待红蓝（APISIX X SkyWalking）组合能带来哪些火花。
+Apache APISIX has better observability capabilities than native Nginx, and will introduce the monitoring tools and capabilities that Apache APISIX already has. This session will introduce the monitoring tools and capabilities already available in Apache APISIX, and what enhancements have been made since the integration with Apache SkyWalking, and what new features will be added in the future. We are looking forward to seeing what sparks the Red and Blue (APISIX X SkyWalking) combination [...]
-### 利用 Apache SkyWalking Infra E2E 进行端到端测试
+### End-to-end testing with Apache SkyWalking Infra E2E
-#### 分享嘉宾
+#### Sharing Guests
-刘晗，Apache SkyWalking Committer & PMC 成员
+Han Liu, Apache SkyWalking Committer & PMC member
-#### 议题详情
+#### Topic Details
-现在越来越多的项目开始利用端到端测试来完成自动化功能检测，本次分享着重讲解 SkyWalking-Infra-E2E 框架与其在 Apache SkyWalking 中的落地。
+Nowadays, more and more projects are using end-to-end testing to automate functional testing, and this session focuses on SkyWalking-Infra-E2E framework and its implementation in Apache SkyWalking.
-### Apache APISIX Ingress Controller 如何在社区中成长
+### How Apache APISIX Ingress Controller is growing in the community
-#### 分享嘉宾
+#### Guest Speakers
-金卫，Apache APISIX PMC，Apache SkyWalking Committer
+Wei Jin, Apache APISIX PMC, Apache SkyWalking Committer
-#### 议题详情
+#### Topic Details
-1. 介绍 Apache APISIX Ingress Controller 项目
-2. 加入 Apache 社区后带来新的活力
-3. Apache APISIX Ingress Controller 在社区中的运作方式
-4. 欢迎加入 Apache APISIX 社区
+1. Introducing the Apache APISIX Ingress Controller project
+2. New energy brought by joining the Apache community
+3. How the Apache APISIX Ingress Controller works in the community
+4. Welcome to the Apache APISIX community
-### License Eye - 开源软件协议利器
+### License Eye - an open source software protocol tool
-#### 分享嘉宾
+#### Sharing Guests
-柯振旭，Apache SkyWalking PMC 成员，Apache 孵化器 PMC 成员和导师
+Zhenxu Ke, Apache SkyWalking PMC member, Apache Incubator PMC member and mentor
-#### 议题详情
+#### Topic Details
-本次分享将以 Apache SkyWalking 为例，总结开源项目运营过程中可能遇到的协议问题，并详细介绍开源协议的处理工具 License Eye 的使用方式。
+This session will take Apache SkyWalking as an example, summarize the protocol issues that may be encountered during the operation of open source projects, and introduce in detail how to use License Eye, a tool for handling open source protocols.
-## 参与方式
+## How to participate
-👇👇👇 扫码关注视频号，预约本次直播。
+👇👇👇👇 Scan the code to follow the video number and book this live broadcast.
-10 月 23 日（周六）14:00，我们直播见！
+See you live on Saturday, October 23rd at 14:00!