Skip to content

Commit 7e32e68

Browse files
authored
chore: reorder docs & docusaurus configurations (#654)
1 parent f998205 commit 7e32e68

File tree

143 files changed

+668
-2033
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

143 files changed

+668
-2033
lines changed

website/i18n/zh/docusaurus-plugin-content-blog/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md renamed to website/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,13 @@ description: 贝壳找房使用 Apache APISIX 作为生产系统的 API 网关
1111
tags: [User Case]
1212
---
1313

14-
> 本文讲述了贝壳找房当初为什么选择 Apache APISIX 作为API 网关,以及使用过程中的一些心得。
14+
> 本文讲述了贝壳找房当初为什么选择 Apache APISIX 作为 API 网关,以及使用过程中的一些心得。
1515
1616
<!--truncate-->
1717

1818
我是王辉,在贝壳找房负责 API 网关系统的开发,贝壳找房使用 Apache APISIX 作为生产系统的 API 网关,每天处理过亿的生产流量,性能优异,而且很稳定。正好 Apache APISIX 刚刚加入 Apache 孵化器,除了恭喜之外,我想来分享下贝壳找房当初为什么选择 Apache APISIX,以及使用过程中的一些心得。
1919

20-
## 选择 Kong 还是 Apache APISIX
20+
## 选择 Kong 还是 Apache APISIX
2121

2222
![Apache APISIX vs Kong in QPS](https://static.apiseven.com/2020/05/1588752135-Snipaste_2020-05-06_16-02-04.png)
2323
![Apache APISIX 架构图](https://static.apiseven.com/2020/05/1588756665-Snipaste_2020-05-06_17-17-29.png)
@@ -46,7 +46,7 @@ tags: [User Case]
4646

4747
![Apache APISIX 技术亮点](https://static.apiseven.com/2020/05/1588756618-Snipaste_2020-05-06_17-16-13.png)
4848

49-
## Apache APISIX 能提供哪些能力
49+
## Apache APISIX 能提供哪些能力
5050

5151
+ 热更新和热插件
5252
+ 动态负载均衡

website/blog/2020-12-16-another-way-to-implement-envoy-filter.md renamed to website/blog/2020/12/16/another-way-to-implement-envoy-filter.md

File renamed without changes.

website/i18n/zh/docusaurus-plugin-content-blog/2020-12-18-a-first-look-at-kubernetes-service-api.md renamed to website/blog/2020/12/18/first-look-at-kubernetes-service-api.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ tags: [Technology]
3535

3636
## 介绍
3737

38-
### Kubernetes Service APIs 号称第二代 Ingress 技术,到底在哪些方面优于第一代
38+
### Kubernetes Service APIs 号称第二代 Ingress 技术,到底在哪些方面优于第一代
3939

4040
Kubernetes Service APIs 设计之初,目标并没有局限在 Ingress, 而是为了增强 service networking,着重通过以下几点来增强:表达性、扩展性、RBAC。
4141

@@ -61,7 +61,7 @@ matches:
6161

6262
3. 面向角色 RBAC:多层 API 的实现,其中一个思想就是从使用者的角度去设计资源对象。这些资源最终会与 Kubernetes 上运行应用程序的常见角色进行映射。
6363

64-
## Kubernetes Service APIs 抽象出了哪些资源对象
64+
## Kubernetes Service APIs 抽象出了哪些资源对象
6565

6666
Kubernetes Service APIs 基于使用者角色,将定义了以下几种资源:
6767

@@ -93,7 +93,7 @@ GatewayClass, Gateway, Route
9393

9494
通过 BackendPolicy 对象,可以配置 TLS、健康检查 以及指定后端服务类型,比如 service 还是 pod。
9595

96-
## Kubernetes Service APIs 的推行会带来哪些改变
96+
## Kubernetes Service APIs 的推行会带来哪些改变
9797

9898
Kubernetes Service APIs 作为一种实现标准,带来了以下改变:
9999

@@ -107,11 +107,11 @@ Kubernetes Service APIs 作为一种实现标准,带来了以下改变:
107107

108108
5. 跨命名空间引用:跨不同命名空间的路由可以绑定到 Gateway。允许跨命名空间的互相访问。同时也可以限制某个 Gateway 下的 Route 可以访问的命名空间范围。
109109

110-
## 目前有哪些 ingress 实现了 Kubernetes Service APIs
110+
## 目前有哪些 ingress 实现了 Kubernetes Service APIs
111111

112112
目前已知的从代码层面能看到对 Kubernetes Service APIs 资源对象支持的 Ingress 有 Contour, ingress-gce。
113113

114-
## Kubernetes Service APIs 如何管理资源读写权限
114+
## Kubernetes Service APIs 如何管理资源读写权限
115115

116116
Kubernetes Service APIs 按照使用者的维度分为 3 个角色
117117

@@ -133,7 +133,7 @@ RBAC(基于角色的访问控制)是用于 Kubernetes 授权的标准。允
133133
| Cluster Operators | No | Yes | Yes |
134134
| Application Developers | No | No | Yes |
135135

136-
## Kubernetes Service APIs 有哪些扩展点
136+
## Kubernetes Service APIs 有哪些扩展点
137137

138138
网关的需求非常丰富,同一个场景实现的方式多种多样,各有利弊。Kubernetes Service APIs 提炼出 多层 资源对象,同时也预留了一些扩展点。
139139

website/blog/2021-08-27-release-apache-apisix-2.9.md

Lines changed: 0 additions & 78 deletions
This file was deleted.

website/i18n/zh/docusaurus-plugin-content-blog/2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md renamed to website/blog/2021/01/11/interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,4 +43,4 @@ tags: [Interview]
4343

4444
Apache APISIX 的第一个 CVE:Apache APISIX Admin API 默认 Token 漏洞(CVE-2020-13945)。[安全漏洞详情](https://nvd.nist.gov/vuln/detail/CVE-2020-13945)
4545

46-
![2021-01-11-1](../../../static/img/blog_img/2021-01-11-1.png)
46+
![2021-01-11-1](/img/blog_img/2021-01-11-1.png)

website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md renamed to website/blog/2021/01/21/run-ingress-apisix-on-amazon-eks.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ author: "Chao Zhang"
44
authorURL: "https://github.com/tokers"
55
authorImageURL: "https://avatars0.githubusercontent.com/u/10428333?s=60&v=4"
66
keywords:
7-
- API Gateway
8-
- APISIX
9-
- Apache APISIX
10-
- Ingress
11-
- Amazon EKS
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Ingress
11+
- Amazon EKS
1212
description: Amazon EKS provides flexibility to start, run, and scale Kubernetes applications in the AWS cloud or on-premises. This article explains how to run Ingress APISIX on it.This article explains how to run Ingress APISIX on Amazon EKS.
1313
tags: [Practical Case]
1414
---
@@ -25,8 +25,6 @@ tags: [Practical Case]
2525
2626
This post is based on [Install Ingress APISIX on Amazon EKS](http://apisix.apache.org/docs/ingress-controller/deployments/aws/).
2727

28-
-
29-
3028
Amazon Elastic Kubernetes Service ([Amazon EKS](https://amazonaws-china.com/eks/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc&eks-blogs.sort-by=item.additionalFields.createdDate&eks-blogs.sort-order=desc)) gives you the flexibility to start, run, and scale Kubernetes applications in the AWS cloud or on-premises. This article explains how to run Ingress APISIX on it.
3129

3230
Ingress APISIX brings good features (traffic splitting, multiple protocols, authentication and etc) of Apache APISIX to Kubernetes, with a well-designed Controller component to drive it, which helps users to achieve complex demands for the north-south traffic.
@@ -70,7 +68,7 @@ kubectl get service apisix-gateway \
7068
-o jsonpath='{.status.loadBalancer.ingress[].hostname}'
7169
```
7270

73-
Another thing should be concerned that the `allow.ipList` field should be customized according to the [EKS CIDR Ranges](https://amazonaws-china.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/) in your EKS cluster, so that the apisix-ingress-controller can be authorized by Apache APISIX (for the resources pushing).
71+
Another thing should be concerned that the `allow.ipList` field should be customized according to the [EKS CIDR Ranges](https://amazonaws-china.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/) in your EKS cluster, so that the apisix-ingress-controller can be authorized by Apache APISIX (for the resources pushing).
7472

7573
See [values.yaml](https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/values.yaml) to learn all the configuration items if you have other requirements.
7674

website/blog/2021-02-08-stable-product-delivery-with-cypress.md renamed to website/blog/2021/02/08/stable-product-delivery-with-cypress.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ author: "Yi Sun"
44
authorURL: "https://github.com/LiteSun"
55
authorImageURL: "https://avatars.githubusercontent.com/u/31329157?s=400&u=e81b4bb4db2be162c1fcac6d188f5b0f82f71920&v=4"
66
keywords:
7-
- API Gateway
8-
- APISIX
9-
- Apache APISIX
10-
- Helm Chart
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Helm Chart
1111
description: This article explains how Yi Sun, GitHub ID [@LiteSun](https://github.com/LiteSun), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/), implements stable product delivery with Cypress.
1212
tags: [Technology]
1313
---
@@ -25,7 +25,7 @@ tags: [Technology]
2525

2626
The Apache APISIX Dashboard is designed to make it as easy as possible for users to operate Apache APISIX through a front-end interface, and since the project's inception, there have been 552 commits and 10 releases. With such rapid product iteration, it is important to ensure the quality of the open-source product. For this reason, we have introduced an E2E testing module to ensure stable product delivery.
2727

28-
## What is Front-End E2E?
28+
## What is Front-End E2E
2929

3030
E2E, which stands for "End to End", can be translated as "end-to-end" testing. It mimics user behavior, starting with an entry point and executing actions step-by-step until a job is completed. Sound testing prevents code changes from breaking the original logic.
3131

website/blog/2021-02-26-install-apache-apisix-from-helm-charts.md renamed to website/blog/2021/02/26/install-apache-apisix-from-helm-charts.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ author: "Chao Zhang"
44
authorURL: "https://github.com/tokers"
55
authorImageURL: "https://avatars.githubusercontent.com/u/10428333?s=400&u=f48ef50c5621a1616a3ede50221547e34270e061&v=4"
66
keywords:
7-
- API Gateway
8-
- APISIX
9-
- Apache APISIX
10-
- Helm Chart
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Helm Chart
1111
description: A few days ago, Zhiliu Inc released an online Helm Charts repository. Users can easily install Apache APISIX, Apache apisix-dashboard and Apache apisix-ingress-controller from it (rather than cloning the corresponding project in advance).
1212
tags: [Practical Case]
1313
---
@@ -27,14 +27,14 @@ Just a few steps to install Apache APISIX
2727

2828
1. Add the repository and fetch the update
2929

30-
```
30+
```sh
3131
$ helm repo add apisix https://charts.apiseven.com
3232
$ helm repo update
3333
```
3434

3535
2. Check out the available charts in repository
3636

37-
```
37+
```sh
3838
$ helm search repo apisix
3939

4040
NAME CHART VERSION APP VERSION DESCRIPTION
@@ -44,7 +44,7 @@ Just a few steps to install Apache APISIX
4444

4545
3. Install Apache APISIX to your Kubernetes cluster
4646

47-
```
47+
```sh
4848
$ helm install apisix-gw apisix/apisix --namespace default
4949

5050
NAME: apisix-gw

website/blog/2021-03-02-get-front-end-test-coverage-with-cypress.md renamed to website/blog/2021/03/02/get-front-end-test-coverage-with-cypress.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ tags: [Technology]
2020
> - https://github.com/apache/apisix
2121
> - https://github.com/apache/apisix-dashboard
2222
23-
## What is code coverage?
23+
## What is code coverage
2424

2525
Code coverage is a metric in software testing that describes the proportion and extent to which the source code in a program is tested, and the resulting proportion is called code coverage. Test code coverage reflects the health of the code to a certain extent.
2626

website/i18n/zh/docusaurus-plugin-content-blog/2021-05-24-Tencent-Games.md renamed to website/blog/2021/05/24/Tencent-Games.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,7 @@ OTeam 的运作参考下图:
111111

112112
## OTeam 发展情况
113113

114-
截止 2021 年 5 月,Apache APISIX 所在的 OTeam 在腾讯内部已为超过十个团队落地了 Apache APISIX,其中最大的业务日请求量已超过十亿,同时 OTeam 也为 Apache APISIX 开发了超过十个内部特性,其中包括内部的服务发现、RPC协议转换、打通监控平台等。
115-
与此同时,OTeam 也将开发的一些通用的特性贡献到了社区,为社区带来了不少 Contributor。目前 OTeam 团队中,有两位成员同时也是 ApacheAPISIX 社区的 PMC,OTeam 为社区贡献了超过 50 个PR。同时,我们相信 OTeam 今后还会与 Apache APISIX 社区开展更多的合作。
114+
截止 2021 年 5 月,Apache APISIX 所在的 OTeam 在腾讯内部已为超过十个团队落地了 Apache APISIX,其中最大的业务日请求量已超过十亿,同时 OTeam 也为 Apache APISIX 开发了超过十个内部特性,其中包括内部的服务发现、RPC 协议转换、打通监控平台等。与此同时,OTeam 也将开发的一些通用的特性贡献到了社区,为社区带来了不少 Contributor。目前 OTeam 团队中,有两位成员同时也是 ApacheAPISIX 社区的 PMC,OTeam 为社区贡献了超过 50 个 PR。同时,我们相信 OTeam 今后还会与 Apache APISIX 社区开展更多的合作。
116115

117116
## 腾讯内部特性介绍
118117

0 commit comments

Comments
 (0)