Skip to content

Commit 5f7954a

Browse files
authored
docs: update keywords, description, and brief intro for blogs (#606)
1 parent bd2b88e commit 5f7954a

File tree

58 files changed

+354
-181
lines changed

Some content is hidden

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

58 files changed

+354
-181
lines changed

website/blog/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "贝壳找房:如何基于 Apache APISIX 搭建网关"
3-
author: 王辉
3+
author: "王辉"
44
keywords:
55
- API 网关
66
- APISIX
@@ -10,7 +10,9 @@ keywords:
1010
description: 贝壳找房使用 Apache APISIX 作为生产系统的 API 网关,每天处理过亿的生产流量,性能优异,而且很稳定。正好 Apache APISIX 刚刚加入 Apache 孵化器,除了恭喜之外,我想来分享下贝壳找房当初为什么选择 Apache APISIX,以及使用过程中的一些心得。
1111
tags: [technology, practical case]
1212
---
13+
1314
> 本文讲述了贝壳找房当初为什么选择 Apache APISIX 作为API 网关,以及使用过程中的一些心得。
15+
1416
<!--truncate-->
1517

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

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

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,18 @@
11
---
22
title: "Envoy and Apache APISIX: Another way to implement the Envoy filter"
3-
author: nic-chen
3+
author: "Junxu Chen"
44
authorURL: "https://github.com/nic-chen"
5-
authorImageURL: "https://avatars0.githubusercontent.com/u/33000667"
5+
authorImageURL: "https://avatars.githubusercontent.com/u/33000667?v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Envoy
11+
description: Envoy is an L7 proxy and communication bus designed for large modern service oriented architectures. A pluggable filter chain mechanism allows filters to be written to perform different tasks and inserted into the main server.
612
tags: [technology]
713
---
814

9-
> [@nic-chen](https://github.com/nic-chen), Apache APISIX PMC from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
15+
> This article explains how to run Apache APISIX plugins in Envoy.
1116
1217
<!--truncate-->
1318

website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,18 @@
11
---
22
title: "初探 Kubernetes Service APIs"
3-
author: Wei Jin
3+
author: "金卫"
44
authorURL: "https://github.com/gxthrj"
55
authorImageURL: "https://avatars2.githubusercontent.com/u/4413028?s=400&u=e140a6d2bf19c426da6498b8888edc96509be649&v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Kubernetes Service APIs
11+
description: 本文通过提问的方式,对 Kubernetes Service APIs 做了一些基本介绍,从整体来看,Kubernetes Service APIs 提炼了很多 ingress 的最佳实践,比如表达能力的增强,其实就是扩展了 Route 的能力,再比如 BackendPolicy 对象,可以为 upstream 指定几乎所有的 Kubernetes 后端资源。
612
tags: [technology]
713
---
814

9-
> [@gxthrj](https://github.com/gxthrj), Apache APISIX PMC & Apache apisix-ingress-controller Founder from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
15+
> 本文通过提问的方式,对 Kubernetes Service APIs 做了一些基本介绍,从整体来看,Kubernetes Service APIs 提炼了很多 ingress 的最佳实践,比如表达能力的增强,其实就是扩展了 Route 的能力,再比如 BackendPolicy 对象,可以为 upstream 指定几乎所有的 Kubernetes 后端资源。
1116
1217
<!--truncate-->
1318

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: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,21 @@
11
---
22
title: "Apache APISIX 贡献者专访 | 普华永道华南数据安全与隐私保护团队高级安全顾问王鹏诚"
3-
author: Ming Wen
3+
author: "温铭"
44
authorURL: "https://github.com/moonming"
55
authorImageURL: "https://avatars.githubusercontent.com/u/26448043?v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- 普华永道
11+
- 漏洞
12+
description: 近日,来自普华永道华南数据安全及隐私保护团队的高级安全顾问王鹏诚向国家信息安全漏洞共享平台(CNVD)和 Apache 软件基金会,报告了 Apache APISIX 的第一个 CVE:Apache APISIX Admin API 默认 Token 漏洞(CVE-2020-13945)。为了感谢鹏诚对 Apache APISIX 社区做的贡献,我们也特意对鹏诚进行了专访。
613
tags: [security, news]
714
---
8-
> [@moonming](https://github.com/moonming), Apache APISIX PMC Chair from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
9-
>
1015

11-
<!--truncate-->
12-
## 背景介绍
16+
> 近日,来自普华永道华南数据安全及隐私保护团队的高级安全顾问王鹏诚向国家信息安全漏洞共享平台(CNVD)和 Apache 软件基金会,报告了 Apache APISIX 的第一个 CVE:Apache APISIX Admin API 默认 Token 漏洞(CVE-2020-13945)。为了感谢鹏诚对 Apache APISIX 社区做的贡献,我们也特意对鹏诚进行了专访。
1317
14-
近日,来自普华永道华南数据安全及隐私保护团队的高级安全顾问王鹏诚向国家信息安全漏洞共享平台(CNVD)和 Apache 软件基金会,报告了 Apache APISIX 的第一个 CVE:Apache APISIX Admin API 默认 Token 漏洞(CVE-2020-13945)。为了感谢鹏诚对 Apache APISIX 社区做的贡献,我们也特意对鹏诚进行了专访。
18+
<!--truncate-->
1519

1620
## 贡献者简介
1721

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

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,19 @@
11
---
22
title: Run Ingress APISIX on Amazon EKS
3-
author: Chao Zhang
3+
author: "Chao Zhang"
44
authorURL: "https://github.com/tokers"
55
authorImageURL: "https://avatars0.githubusercontent.com/u/10428333?s=60&v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Ingress
11+
- Amazon EKS
12+
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.
613
tags: [technology, practical case]
714
---
815

9-
> [@Chao Zhang](https://github.com/tokers), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
16+
> 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.
1117
1218
<!--truncate-->
1319

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

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,18 @@
11
---
22
title: "Stable Product Delivery with Cypress"
3-
author: Yi Sun
3+
author: "Yi Sun"
44
authorURL: "https://github.com/LiteSun"
55
authorImageURL: "https://avatars.githubusercontent.com/u/31329157?s=400&u=e81b4bb4db2be162c1fcac6d188f5b0f82f71920&v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Helm Chart
11+
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.
612
tags: [technology]
713
---
814

9-
> [@LiteSun](https://github.com/LiteSun), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
15+
> This article explains how Yi Sun, GitHub ID [@LiteSun](https://github.com/LiteSun), became Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/), implements stable product delivery with Cypress.
1116
1217
<!--truncate-->
1318

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

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,18 @@
11
---
22
title: "Install Apache APISIX from Helm Charts"
3-
author: Chao Zhang
3+
author: "Chao Zhang"
44
authorURL: "https://github.com/tokers"
55
authorImageURL: "https://avatars.githubusercontent.com/u/10428333?s=400&u=f48ef50c5621a1616a3ede50221547e34270e061&v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Helm Chart
11+
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).
612
tags: [technology, practical case]
713
---
814

9-
> [@tokers](https://github.com/tokers), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
15+
> A few days ago, [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/) 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).
1116
1217
<!--truncate-->
1318

@@ -16,8 +21,6 @@ tags: [technology, practical case]
1621
> - https://github.com/apache/apisix
1722
> - https://github.com/apache/apisix-helm-chart
1823
19-
A few days ago, [Zhiliu Inc](https://www.apiseven.com/) 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).
20-
2124
## How To Use
2225

2326
Just a few steps to install Apache APISIX

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

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
22
title: "Get Front-End Test Coverage with Cypress"
3-
author: Yi Sun
3+
author: "Yi Sun"
44
authorURL: "https://github.com/LiteSun"
55
authorImageURL: "https://avatars.githubusercontent.com/u/31329157?s=400&u=e81b4bb4db2be162c1fcac6d188f5b0f82f71920&v=4"
66
tags: [technology]
77
---
88

9-
> [@LiteSun](https://github.com/LiteSun), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
10-
>
9+
> In the article ["Stable Product Delivery with Cypress"](/blog/2021/02/08/stable-product-delivery-with-cypress), we discussed why we chose Cypress as our E2E testing framework. After spending nearly two months refining the test cases, we needed test coverage to quantify whether the test coverage was sufficient.This article will describe how to get APISIX Dashboard front-end E2E coverage using Cypress.
1110
1211
<!--truncate-->
1312

@@ -16,10 +15,6 @@ tags: [technology]
1615
> - https://github.com/apache/apisix
1716
> - https://github.com/apache/apisix-dashboard
1817
19-
## Background
20-
21-
In the article ["Stable Product Delivery with Cypress"](/blog/2021/02/08/stable-product-delivery-with-cypress), we discussed why we chose Cypress as our E2E testing framework. After spending nearly two months refining the test cases, we needed test coverage to quantify whether the test coverage was sufficient.This article will describe how to get APISIX Dashboard front-end E2E coverage using Cypress.
22-
2318
## What is code coverage?
2419

2520
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.

website/blog/2021-03-27-traffic-split-in-apache-apisix-ingress-controller.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,17 @@ title: "Traffic Split in Apache APISIX Ingress Controller"
33
author: "Chao Zhang"
44
authorURL: "https://github.com/tokers"
55
authorImageURL: "https://avatars.githubusercontent.com/u/10428333?s=460&u=f48ef50c5621a1616a3ede50221547e34270e061&v=4"
6+
keywords:
7+
- API Gateway
8+
- APISIX
9+
- Apache APISIX
10+
- Traffic Split
11+
- Ingress Controller
12+
description: Traffic Split is a feature that splits and deliveries traffic to multiple backend services. Solutions like API Gateway and Service Mesh are capable of doing traffic splitting and implement functionalities like Canary Release and Blue-Green Deployment.
613
tags: [technology, practical case]
714
---
8-
> [@tokers](https://github.com/tokers), Apache APISIX Committer from [Shenzhen Zhiliu Technology Co.](https://www.apiseven.com/)
9-
>
15+
16+
> Traffic Split is a feature that splits and deliveries traffic to multiple backend services. Solutions like API Gateway and Service Mesh are capable of doing traffic splitting and implement functionalities like Canary Release and Blue-Green Deployment.
1017
1118
<!--truncate-->
1219

website/blog/2021-05-24-Tencent-Games.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: "支持 10 亿日流量的基础设施:当 Apahce APISIX 遇上腾讯"
3-
author: 徐鑫
3+
author: "徐鑫"
44
keywords:
55
- API 网关
66
- APISIX
77
- Apache APISIX
88
- 腾讯游戏
99
- 基础设施
10-
description: 截止 2021 年 5 月,Apache APISIX 所在的 OTeam 在腾讯内部已为超过十个团队落地了 Apache APISIX,其中最大的业务日请求量已超过十亿,同时 OTeam 也为 Apache APISIX 开发了超过十个内部特性,其中包括内部的服务发现、RPC协议转换、打通监控平台等
10+
description: 本文整理自腾讯游戏负责内部容器平台的工程师徐鑫在 Apache APISIX Meetup - 深圳站的演讲,通过阅读本文,您不仅可以了解网关是什么、网关模式对传统服务架构的改进,还可以了解腾讯 OTeam 诞生的原因,以及 Apache APISIX 是如何在腾讯内部落地的
1111
tags: [technology,practical case]
1212
---
1313

0 commit comments

Comments
 (0)