This is an automated email from the ASF dual-hosted git repository. juzhiyuan pushed a commit to branch chore-docusaurus in repository https://gitbox.apache.org/repos/asf/apisix-website.git
commit 59a0a706ddc7e9675e2345d2b5e5eade99a50c93 Author: juzhiyuan <[email protected]> AuthorDate: Sun Oct 10 22:27:47 2021 +0800 chore: move docs --- ...11-beike-how-to-build-gateway-based-on-apache-apisix.md | 0 .../2020-12-16-another-way-to-implement-envoy-filter.md | 0 .../2020-12-18-a-first-look-at-kubernetes-service-api.md | 0 ...outh-China-Data-Security-and-Privacy-Protection-Team.md | 0 .../01/21}/2021-01-21-run-ingress-apisix-on-amazon-eks.md | 14 ++++++-------- .../08}/2021-02-08-stable-product-delivery-with-cypress.md | 10 +++++----- .../2021-02-26-install-apache-apisix-from-helm-charts.md | 14 +++++++------- .../2021-03-02-get-front-end-test-coverage-with-cypress.md | 2 +- website/blog/{ => 2021/05/24}/2021-05-24-Tencent-Games.md | 3 +-- ...se \346\255\243\345\274\217\345\217\221\345\270\203.md" | 0 ...-06-03-experience-share-from-Apache-APISIX-committer.md | 0 .../blog/{ => 2021/06/06}/2021-06-06-apisix-two-years.md | 0 ...7-Apache-APISIX-not-affected-by-NGINX-CVE-2021-23017.md | 0 ...06-10-Apache-APISIX-and-Envoy-performance-comparison.md | 0 ...-16-Chaos-Mesh-helps-Apache-APISIX-improve-stability.md | 0 ...ard-Access-Control-Bypass-Vulnerability-Announcement.md | 0 ...on-v1.0-of-Apache-APISIX-Ingress-Controller-released.md | 0 .../2021-06-21-use-Java-to-write-Apache-APISIX-plugins.md | 0 ...reat-open-source-gateway-and-ingress-controller-fast.md | 0 .../06/28}/2021-06-28-why-we-need-Apache-APISIX.md | 0 .../06/29}/2021-06-29-release-apache-apisix-2.7-en.md | 0 .../30}/2021-06-30-etcd3-support-HTTP-access-perfectly.md | 0 .../07/06}/2021-07-06-celebrate-200-contributors.md | 0 ...ion-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md | 0 .../07/21}/2021-07-21-Apache-APISIX-Kubernetes.md | 2 +- website/blog/{ => 2021/07/25}/2021-07-25-apachecon-asia.md | 14 +++++++------- ...1-07-27-use-of-plugin-orchestration-in-Apache-APISIX.md | 0 .../07/28}/2021-07-28-release-apache-apisix-2.8-en.md | 0 website/blog/{ => 2021/08/05}/2021-08-05-Kong-to-APISIX.md | 0 ...-apache-apisix-to-improve-the-observability-of-nginx.md | 6 +++--- .../09}/2021-08-09-Apache-APISIX-in-China-Mobile-Cloud.md | 0 .../08/09}/2021-08-09-Apache-APISIX-in-Quliankeji.md | 0 website/blog/{ => 2021/08/10}/2021-08-10-apisix-nginx.md | 12 ++++++------ .../{ => 2021/08/11}/2021-08-11-interview-TuZhengsong.md | 0 ...os-Mesh-Helps-Apache-APISIX-Improve-System-Stability.md | 0 ...ributors-the-golden-metric-of-openSource-projects-en.md | 0 ...OpenID-Connect-Plugin-for-Centralized-Authentication.md | 2 +- .../{ => 2021/08/17}/2021-08-17-interview-airwallex.md | 0 .../08/18}/2021-08-18-Auth-with-Casbin-in-Apache-APISIX.md | 0 .../08/19}/2021-08-19-go-makes-Apache-APISIX-better.md | 0 website/blog/{ => 2021/08/19}/2021-08-19-weekly-report.md | 2 +- .../blog/{ => 2021/08/21}/2021-08-21-shanghai-meetup.md | 0 .../{ => 2021/08/23}/2021-08-23-ApacheCon-Asia-2021.md | 0 website/blog/{ => 2021/08/23}/2021-08-23-weekly-report.md | 0 .../{ => 2021/08/24}/2021-08-24-shanghai-meetup-recap.md | 4 ++-- .../08/25}/2021-08-25-Auth-with-Casbin-in-Apache-APISIX.md | 0 ...OpenID-Connect-Plugin-for-Centralized-Authentication.md | 14 +++++++------- .../2021-08-25-Why-Apache-APISIX-chose-Nginx-and-Lua.md | 0 .../08/27}/2021-08-27-release-apache-apisix-2.9-en.md | 0 .../08/27}/2021-08-27-release-apache-apisix-2.9.md | 0 .../blog/{ => 2021/08/30}/2021-08-30-Ingress-Meeting.md | 0 website/blog/{ => 2021/08/30}/2021-08-30-weekly-report.md | 2 +- ...eSphere-a-better-gateway-and-K8S-Ingress-Controller.md" | 0 ...hon-helps-you-quickly-with-Apache-APISIX-development.md | 0 .../{ => 2021/09/07}/2021-09-07-how-to-use-apisix-auth.md | 2 +- website/blog/{ => 2021/09/07}/2021-09-07-iQIYI-usercase.md | 12 ++++++------ ...09-how-to-contribute-to-an-OpenSource-without-coding.md | 0 .../09/13}/2021-09-13-china-mobile-cloud-usercase.md | 12 ++++++------ website/blog/{ => 2021/09/14}/2021-09-14-youzan.md | 0 website/blog/{ => 2021/09/15}/2021-09-15-weekly-report.md | 2 +- website/blog/{ => 2021/09/16}/2021-09-16-tencent-cloud.md | 2 +- .../blog/{ => 2021/09/18}/2021-09-18-xiaodian-usercase.md | 6 +++--- .../{ => 2021/09/24}/2021-09-24-youpaicloud-usercase.md | 0 website/blog/{ => 2021/09/28}/2021-09-28-WPS-usercase.md | 4 ++-- .../09/29}/2021-09-29-release-apache-apisix-2.10-en.md | 0 .../09/29}/2021-09-29-release-apache-apisix-2.10.md | 0 website/blog/{ => 2021/09/30}/2021-09-30-weekly-report.md | 2 +- website/blog/{ => 2021/10/01}/2021-10-01-openEuler.md | 2 +- 68 files changed, 71 insertions(+), 74 deletions(-) diff --git a/website/blog/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md b/website/blog/2020/12/11/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md similarity index 100% rename from website/blog/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md rename to website/blog/2020/12/11/2020-12-11-beike-how-to-build-gateway-based-on-apache-apisix.md diff --git a/website/blog/2020-12-16-another-way-to-implement-envoy-filter.md b/website/blog/2020/12/16/2020-12-16-another-way-to-implement-envoy-filter.md similarity index 100% rename from website/blog/2020-12-16-another-way-to-implement-envoy-filter.md rename to website/blog/2020/12/16/2020-12-16-another-way-to-implement-envoy-filter.md diff --git a/website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md b/website/blog/2020/12/18/2020-12-18-a-first-look-at-kubernetes-service-api.md similarity index 100% rename from website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md rename to website/blog/2020/12/18/2020-12-18-a-first-look-at-kubernetes-service-api.md diff --git a/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 b/website/blog/2021/01/11/2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md similarity index 100% rename from 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 rename to website/blog/2021/01/11/2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md diff --git a/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md b/website/blog/2021/01/21/2021-01-21-run-ingress-apisix-on-amazon-eks.md similarity index 94% rename from website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md rename to website/blog/2021/01/21/2021-01-21-run-ingress-apisix-on-amazon-eks.md index 9753ac8..133a0d2 100644 --- a/website/blog/2021-01-21-run-ingress-apisix-on-amazon-eks.md +++ b/website/blog/2021/01/21/2021-01-21-run-ingress-apisix-on-amazon-eks.md @@ -4,11 +4,11 @@ author: "Chao Zhang" authorURL: "https://github.com/tokers"; authorImageURL: "https://avatars0.githubusercontent.com/u/10428333?s=60&v=4"; keywords: -- API Gateway -- APISIX -- Apache APISIX -- Ingress -- Amazon EKS + - API Gateway + - APISIX + - Apache APISIX + - Ingress + - Amazon EKS 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. tags: [Practical Case] --- @@ -25,8 +25,6 @@ tags: [Practical Case] This post is based on [Install Ingress APISIX on Amazon EKS](http://apisix.apache.org/docs/ingress-controller/deployments/aws/). -- - 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. 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 \ -o jsonpath='{.status.loadBalancer.ingress[].hostname}' ``` - 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). +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). 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. diff --git a/website/blog/2021-02-08-stable-product-delivery-with-cypress.md b/website/blog/2021/02/08/2021-02-08-stable-product-delivery-with-cypress.md similarity index 98% rename from website/blog/2021-02-08-stable-product-delivery-with-cypress.md rename to website/blog/2021/02/08/2021-02-08-stable-product-delivery-with-cypress.md index a5991d0..7982a48 100644 --- a/website/blog/2021-02-08-stable-product-delivery-with-cypress.md +++ b/website/blog/2021/02/08/2021-02-08-stable-product-delivery-with-cypress.md @@ -4,10 +4,10 @@ author: "Yi Sun" authorURL: "https://github.com/LiteSun"; authorImageURL: "https://avatars.githubusercontent.com/u/31329157?s=400&u=e81b4bb4db2be162c1fcac6d188f5b0f82f71920&v=4"; keywords: -- API Gateway -- APISIX -- Apache APISIX -- Helm Chart + - API Gateway + - APISIX + - Apache APISIX + - Helm Chart 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. tags: [Technology] --- @@ -25,7 +25,7 @@ tags: [Technology] 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. -## What is Front-End E2E? +## What is Front-End E2E 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. diff --git a/website/blog/2021-02-26-install-apache-apisix-from-helm-charts.md b/website/blog/2021/02/26/2021-02-26-install-apache-apisix-from-helm-charts.md similarity index 96% rename from website/blog/2021-02-26-install-apache-apisix-from-helm-charts.md rename to website/blog/2021/02/26/2021-02-26-install-apache-apisix-from-helm-charts.md index 38cb046..6708bf0 100644 --- a/website/blog/2021-02-26-install-apache-apisix-from-helm-charts.md +++ b/website/blog/2021/02/26/2021-02-26-install-apache-apisix-from-helm-charts.md @@ -4,10 +4,10 @@ author: "Chao Zhang" authorURL: "https://github.com/tokers"; authorImageURL: "https://avatars.githubusercontent.com/u/10428333?s=400&u=f48ef50c5621a1616a3ede50221547e34270e061&v=4"; keywords: -- API Gateway -- APISIX -- Apache APISIX -- Helm Chart + - API Gateway + - APISIX + - Apache APISIX + - Helm Chart 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). tags: [Practical Case] --- @@ -27,14 +27,14 @@ Just a few steps to install Apache APISIX 1. Add the repository and fetch the update - ``` + ```sh $ helm repo add apisix https://charts.apiseven.com $ helm repo update ``` 2. Check out the available charts in repository - ``` + ```sh $ helm search repo apisix NAME CHART VERSION APP VERSION DESCRIPTION @@ -44,7 +44,7 @@ Just a few steps to install Apache APISIX 3. Install Apache APISIX to your Kubernetes cluster - ``` + ```sh $ helm install apisix-gw apisix/apisix --namespace default NAME: apisix-gw diff --git a/website/blog/2021-03-02-get-front-end-test-coverage-with-cypress.md b/website/blog/2021/03/02/2021-03-02-get-front-end-test-coverage-with-cypress.md similarity index 99% rename from website/blog/2021-03-02-get-front-end-test-coverage-with-cypress.md rename to website/blog/2021/03/02/2021-03-02-get-front-end-test-coverage-with-cypress.md index 3b907fc..6e23dfb 100644 --- a/website/blog/2021-03-02-get-front-end-test-coverage-with-cypress.md +++ b/website/blog/2021/03/02/2021-03-02-get-front-end-test-coverage-with-cypress.md @@ -20,7 +20,7 @@ tags: [Technology] > - https://github.com/apache/apisix > - https://github.com/apache/apisix-dashboard -## What is code coverage? +## What is code coverage 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. diff --git a/website/blog/2021-05-24-Tencent-Games.md b/website/blog/2021/05/24/2021-05-24-Tencent-Games.md similarity index 97% rename from website/blog/2021-05-24-Tencent-Games.md rename to website/blog/2021/05/24/2021-05-24-Tencent-Games.md index 425515d..f691814 100644 --- a/website/blog/2021-05-24-Tencent-Games.md +++ b/website/blog/2021/05/24/2021-05-24-Tencent-Games.md @@ -112,8 +112,7 @@ OTeam 的运作参考下图： ## OTeam 发展情况 -截止 2021 年 5 月，Apache APISIX 所在的 OTeam 在腾讯内部已为超过十个团队落地了 Apache APISIX，其中最大的业务日请求量已超过十亿，同时 OTeam 也为 Apache APISIX 开发了超过十个内部特性，其中包括内部的服务发现、RPC协议转换、打通监控平台等。 -与此同时，OTeam 也将开发的一些通用的特性贡献到了社区，为社区带来了不少 Contributor。目前 OTeam 团队中，有两位成员同时也是 ApacheAPISIX 社区的 PMC，OTeam 为社区贡献了超过 50 个PR。同时，我们相信 OTeam 今后还会与 Apache APISIX 社区开展更多的合作。 +截止 2021 年 5 月，Apache APISIX 所在的 OTeam 在腾讯内部已为超过十个团队落地了 Apache APISIX，其中最大的业务日请求量已超过十亿，同时 OTeam 也为 Apache APISIX 开发了超过十个内部特性，其中包括内部的服务发现、RPC 协议转换、打通监控平台等。与此同时，OTeam 也将开发的一些通用的特性贡献到了社区，为社区带来了不少 Contributor。目前 OTeam 团队中，有两位成员同时也是 ApacheAPISIX 社区的 PMC，OTeam 为社区贡献了超过 50 个 PR。同时，我们相信 OTeam 今后还会与 Apache APISIX 社区开展更多的合作。 ## 腾讯内部特性介绍 diff --git "a/website/blog/2021-05-25-Apache APISIX 2.6.0-Release \346\255\243\345\274\217\345\217\221\345\270\203.md" "b/website/blog/2021/05/25/2021-05-25-Apache APISIX 2.6.0-Release \346\255\243\345\274\217\345\217\221\345\270\203.md" similarity index 100% rename from "website/blog/2021-05-25-Apache APISIX 2.6.0-Release \346\255\243\345\274\217\345\217\221\345\270\203.md" rename to "website/blog/2021/05/25/2021-05-25-Apache APISIX 2.6.0-Release \346\255\243\345\274\217\345\217\221\345\270\203.md" diff --git a/website/blog/2021-06-03-experience-share-from-Apache-APISIX-committer.md b/website/blog/2021/06/03/2021-06-03-experience-share-from-Apache-APISIX-committer.md similarity index 100% rename from website/blog/2021-06-03-experience-share-from-Apache-APISIX-committer.md rename to website/blog/2021/06/03/2021-06-03-experience-share-from-Apache-APISIX-committer.md diff --git a/website/blog/2021-06-06-apisix-two-years.md b/website/blog/2021/06/06/2021-06-06-apisix-two-years.md similarity index 100% rename from website/blog/2021-06-06-apisix-two-years.md rename to website/blog/2021/06/06/2021-06-06-apisix-two-years.md diff --git a/website/blog/2021-06-07-Apache-APISIX-not-affected-by-NGINX-CVE-2021-23017.md b/website/blog/2021/06/07/2021-06-07-Apache-APISIX-not-affected-by-NGINX-CVE-2021-23017.md similarity index 100% rename from website/blog/2021-06-07-Apache-APISIX-not-affected-by-NGINX-CVE-2021-23017.md rename to website/blog/2021/06/07/2021-06-07-Apache-APISIX-not-affected-by-NGINX-CVE-2021-23017.md diff --git a/website/blog/2021-06-10-Apache-APISIX-and-Envoy-performance-comparison.md b/website/blog/2021/06/10/2021-06-10-Apache-APISIX-and-Envoy-performance-comparison.md similarity index 100% rename from website/blog/2021-06-10-Apache-APISIX-and-Envoy-performance-comparison.md rename to website/blog/2021/06/10/2021-06-10-Apache-APISIX-and-Envoy-performance-comparison.md diff --git a/website/blog/2021-06-16-Chaos-Mesh-helps-Apache-APISIX-improve-stability.md b/website/blog/2021/06/16/2021-06-16-Chaos-Mesh-helps-Apache-APISIX-improve-stability.md similarity index 100% rename from website/blog/2021-06-16-Chaos-Mesh-helps-Apache-APISIX-improve-stability.md rename to website/blog/2021/06/16/2021-06-16-Chaos-Mesh-helps-Apache-APISIX-improve-stability.md diff --git a/website/blog/2021-06-17-Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md b/website/blog/2021/06/17/2021-06-17-Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md similarity index 100% rename from website/blog/2021-06-17-Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md rename to website/blog/2021/06/17/2021-06-17-Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md diff --git a/website/blog/2021-06-18-first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released.md b/website/blog/2021/06/18/2021-06-18-first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released.md similarity index 100% rename from website/blog/2021-06-18-first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released.md rename to website/blog/2021/06/18/2021-06-18-first-GA-version-v1.0-of-Apache-APISIX-Ingress-Controller-released.md diff --git a/website/blog/2021-06-21-use-Java-to-write-Apache-APISIX-plugins.md b/website/blog/2021/06/21/2021-06-21-use-Java-to-write-Apache-APISIX-plugins.md similarity index 100% rename from website/blog/2021-06-21-use-Java-to-write-Apache-APISIX-plugins.md rename to website/blog/2021/06/21/2021-06-21-use-Java-to-write-Apache-APISIX-plugins.md diff --git a/website/blog/2021-06-23-deploy-great-open-source-gateway-and-ingress-controller-fast.md b/website/blog/2021/06/23/2021-06-23-deploy-great-open-source-gateway-and-ingress-controller-fast.md similarity index 100% rename from website/blog/2021-06-23-deploy-great-open-source-gateway-and-ingress-controller-fast.md rename to website/blog/2021/06/23/2021-06-23-deploy-great-open-source-gateway-and-ingress-controller-fast.md diff --git a/website/blog/2021-06-28-why-we-need-Apache-APISIX.md b/website/blog/2021/06/28/2021-06-28-why-we-need-Apache-APISIX.md similarity index 100% rename from website/blog/2021-06-28-why-we-need-Apache-APISIX.md rename to website/blog/2021/06/28/2021-06-28-why-we-need-Apache-APISIX.md diff --git a/website/blog/2021-06-29-release-apache-apisix-2.7-en.md b/website/blog/2021/06/29/2021-06-29-release-apache-apisix-2.7-en.md similarity index 100% rename from website/blog/2021-06-29-release-apache-apisix-2.7-en.md rename to website/blog/2021/06/29/2021-06-29-release-apache-apisix-2.7-en.md diff --git a/website/blog/2021-06-30-etcd3-support-HTTP-access-perfectly.md b/website/blog/2021/06/30/2021-06-30-etcd3-support-HTTP-access-perfectly.md similarity index 100% rename from website/blog/2021-06-30-etcd3-support-HTTP-access-perfectly.md rename to website/blog/2021/06/30/2021-06-30-etcd3-support-HTTP-access-perfectly.md diff --git a/website/blog/2021-07-06-celebrate-200-contributors.md b/website/blog/2021/07/06/2021-07-06-celebrate-200-contributors.md similarity index 100% rename from website/blog/2021-07-06-celebrate-200-contributors.md rename to website/blog/2021/07/06/2021-07-06-celebrate-200-contributors.md diff --git a/website/blog/2021-07-14-the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md b/website/blog/2021/07/14/2021-07-14-the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md similarity index 100% rename from website/blog/2021-07-14-the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md rename to website/blog/2021/07/14/2021-07-14-the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md diff --git a/website/blog/2021-07-21-Apache-APISIX-Kubernetes.md b/website/blog/2021/07/21/2021-07-21-Apache-APISIX-Kubernetes.md similarity index 98% rename from website/blog/2021-07-21-Apache-APISIX-Kubernetes.md rename to website/blog/2021/07/21/2021-07-21-Apache-APISIX-Kubernetes.md index fe26b09..81bda56 100644 --- a/website/blog/2021-07-21-Apache-APISIX-Kubernetes.md +++ b/website/blog/2021/07/21/2021-07-21-Apache-APISIX-Kubernetes.md @@ -23,7 +23,7 @@ draft: true - 方式二：在直播开始时通过 Zoom 链接进入会议室聆听分享：[会议室直播间](https://zoom.us/webinar/tJYofuChrzktGtI3wr8SZHACRnNkxr5cWgny)。 -## 来不及看直播怎么办？ +## 来不及看直播怎么办 Meetup 结束后，我们会在 Apache APISIX 的 bilibili 账号上传 Meetup 录播。欢迎大家关注 Apache APISIX bilibili 账号 [Apache-APISIX](https://space.bilibili.com/551921247)。 diff --git a/website/blog/2021-07-25-apachecon-asia.md b/website/blog/2021/07/25/2021-07-25-apachecon-asia.md similarity index 88% rename from website/blog/2021-07-25-apachecon-asia.md rename to website/blog/2021/07/25/2021-07-25-apachecon-asia.md index 09b5105..e29d1a7 100644 --- a/website/blog/2021-07-25-apachecon-asia.md +++ b/website/blog/2021/07/25/2021-07-25-apachecon-asia.md @@ -41,7 +41,7 @@ Apache APISIX 是 Apache 顶级项目，也是全球最活跃的开源网关项  -陈焱山 — 毕业后一直从事分布式存储软件开发及架构方案设计工作，深度参与了移动云建设过程，重点完成了对象存储相关的主要技术方案选型及落地开发建设工作。同时，在分布式对象存储领域拥有丰富的实战经验，目前正在思考基于APISIX七层网关实现对象存储流量治理工作，实现架构进一步升级。 +陈焱山 — 毕业后一直从事分布式存储软件开发及架构方案设计工作，深度参与了移动云建设过程，重点完成了对象存储相关的主要技术方案选型及落地开发建设工作。同时，在分布式对象存储领域拥有丰富的实战经验，目前正在思考基于 APISIX 七层网关实现对象存储流量治理工作，实现架构进一步升级。 ### 分享时间 @@ -59,7 +59,7 @@ Apache APISIX 是 Apache 顶级项目，也是全球最活跃的开源网关项  -陈军旭 — 互联网老兵，曾任职于新浪、迅雷、360等知名互联网公司，Apache APISIX Committer。 +陈军旭 — 互联网老兵，曾任职于新浪、迅雷、360 等知名互联网公司，Apache APISIX Committer。 ### 分享时间 @@ -71,13 +71,13 @@ Apache APISIX 是 Apache 顶级项目，也是全球最活跃的开源网关项 Apache APISIX 是领先的 API 网关 OSS 之一。为了确保一切按计划进行，APISIX 使用了不同种类的测试，包括单元、e2e 和模糊测试。然而，我们仍然不确定，当一些不正常但不可避免的情况发生时，例如网络故障、IO 压力或 pod 故障，APISIX 会如何表现。 -因此，在这里我们使用 Chaos Mesh，一个基于 Kubernetes 的混沌工程平台，可以顺利地注入不同种类的混沌，并将其整合到我们的CI管道中。在这个讲座的最后，听众会了解到混沌工程会在哪些方面给 API 网关带来好处，以及如何将混沌网整合到你自己的测试管道中。 +因此，在这里我们使用 Chaos Mesh，一个基于 Kubernetes 的混沌工程平台，可以顺利地注入不同种类的混沌，并将其整合到我们的 CI 管道中。在这个讲座的最后，听众会了解到混沌工程会在哪些方面给 API 网关带来好处，以及如何将混沌网整合到你自己的测试管道中。 ### 分享嘉宾  -吴舒旸 — Apache APISIX 和 Chaos Mesh 的 Committer，他领导了Chaos Mesh 与 Apache APISIX CI 的整合工作。 +吴舒旸 — Apache APISIX 和 Chaos Mesh 的 Committer，他领导了 Chaos Mesh 与 Apache APISIX CI 的整合工作。 ### 分享时间 @@ -87,7 +87,7 @@ Apache APISIX 是领先的 API 网关 OSS 之一。为了确保一切按计划 ### 议题简介 -认证和授权是 API 网关中非常必要的功能。这样一来，位于网关后面的服务就可以得到保护，避免未经授权或恶意的访问、数据泄露和黑客攻击。Apache APISIX 是一个动态、实时、高性能的API网关。而且它提供了许多插件，包括像 key-auth、Open-ID、wolf-RBAC 等认证和授权。本提案介绍了如何使用 Apache APISIX 来进行认证和授权。 +认证和授权是 API 网关中非常必要的功能。这样一来，位于网关后面的服务就可以得到保护，避免未经授权或恶意的访问、数据泄露和黑客攻击。Apache APISIX 是一个动态、实时、高性能的 API 网关。而且它提供了许多插件，包括像 key-auth、Open-ID、wolf-RBAC 等认证和授权。本提案介绍了如何使用 Apache APISIX 来进行认证和授权。 ### 分享嘉宾 @@ -125,7 +125,7 @@ Apache APISIX 是领先的 API 网关 OSS 之一。为了确保一切按计划  -张超 — Apache APISIX PMC，OpenResty贡献者，开源爱好者，现在正在研究 Service Mesh、Kubernetes 和 API Gateway。 +张超 — Apache APISIX PMC，OpenResty 贡献者，开源爱好者，现在正在研究 Service Mesh、Kubernetes 和 API Gateway。 ### 分享时间 @@ -135,7 +135,7 @@ Apache APISIX 是领先的 API 网关 OSS 之一。为了确保一切按计划 ### 议题简介 -Apache APISIX是最受欢迎的API网关之一：https://github.com/apache/apisix，我将介绍一下 Apache APISIX 的发展，包括： +Apache APISIX 是最受欢迎的 API 网关之一：https://github.com/apache/apisix，我将介绍一下 Apache APISIX 的发展，包括： 1. 我们所做的好决定 2. 我们所做的不好的决定 diff --git a/website/blog/2021-07-27-use-of-plugin-orchestration-in-Apache-APISIX.md b/website/blog/2021/07/27/2021-07-27-use-of-plugin-orchestration-in-Apache-APISIX.md similarity index 100% rename from website/blog/2021-07-27-use-of-plugin-orchestration-in-Apache-APISIX.md rename to website/blog/2021/07/27/2021-07-27-use-of-plugin-orchestration-in-Apache-APISIX.md diff --git a/website/blog/2021-07-28-release-apache-apisix-2.8-en.md b/website/blog/2021/07/28/2021-07-28-release-apache-apisix-2.8-en.md similarity index 100% rename from website/blog/2021-07-28-release-apache-apisix-2.8-en.md rename to website/blog/2021/07/28/2021-07-28-release-apache-apisix-2.8-en.md diff --git a/website/blog/2021-08-05-Kong-to-APISIX.md b/website/blog/2021/08/05/2021-08-05-Kong-to-APISIX.md similarity index 100% rename from website/blog/2021-08-05-Kong-to-APISIX.md rename to website/blog/2021/08/05/2021-08-05-Kong-to-APISIX.md diff --git a/website/blog/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md b/website/blog/2021/08/06/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md similarity index 98% rename from website/blog/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md rename to website/blog/2021/08/06/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md index 0f31859..24695c8 100644 --- a/website/blog/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md +++ b/website/blog/2021/08/06/2021-08-06-using-apache-apisix-to-improve-the-observability-of-nginx.md @@ -156,11 +156,11 @@ Apache APISIX 最重要的一个优势是有一个活跃的社区，一个活跃 ## 结合 Apache SkyWalking，在可观测性上做进一步提升 -Apache APISIX 与 Apache SkyWalking 结合可以做哪些提升？除了 SkyWalking tracing 插件，还可以将tracing、metrics、logging、events 汇聚到 SkyWalking，借助 SkyWalking 的聚合能力让数据实现联动。 +Apache APISIX 与 Apache SkyWalking 结合可以做哪些提升？除了 SkyWalking tracing 插件，还可以将 tracing、metrics、logging、events 汇聚到 SkyWalking，借助 SkyWalking 的聚合能力让数据实现联动。 ### SkyWalking Satellite -SkyWalking Satellite 由 Apache APISIX社区、Apache SkyWalking 社区、百度深度合作开发。 +SkyWalking Satellite 由 Apache APISIX 社区、Apache SkyWalking 社区、百度深度合作开发。  @@ -197,7 +197,7 @@ ALS 方案最大的好处是可以直接通过 access log 方式分析和聚合 至于稳定性方面， Apahce APISIX 已经开源了近 50 个插件，每一个插件都会有端到端的测试，这些插件都是经过验证的、是稳定可用的。但是自定义插件要遵循一定的规范，虽然很简单，但是大家也不能太随意。自定义插件的稳定性保证，需要由业务方自己来保证。 -### 如何确认规则已生效？ +### 如何确认规则已生效 问：Nginx 的 nginx.conf 文件里面可能配置了很多规则，后面的规则可能被前面的规则拦截，不清楚后面的规则是否生效，Apache APISIX 是否有什么方法知道哪些规则已生效？ diff --git a/website/blog/2021-08-09-Apache-APISIX-in-China-Mobile-Cloud.md b/website/blog/2021/08/09/2021-08-09-Apache-APISIX-in-China-Mobile-Cloud.md similarity index 100% rename from website/blog/2021-08-09-Apache-APISIX-in-China-Mobile-Cloud.md rename to website/blog/2021/08/09/2021-08-09-Apache-APISIX-in-China-Mobile-Cloud.md diff --git a/website/blog/2021-08-09-Apache-APISIX-in-Quliankeji.md b/website/blog/2021/08/09/2021-08-09-Apache-APISIX-in-Quliankeji.md similarity index 100% rename from website/blog/2021-08-09-Apache-APISIX-in-Quliankeji.md rename to website/blog/2021/08/09/2021-08-09-Apache-APISIX-in-Quliankeji.md diff --git a/website/blog/2021-08-10-apisix-nginx.md b/website/blog/2021/08/10/2021-08-10-apisix-nginx.md similarity index 96% rename from website/blog/2021-08-10-apisix-nginx.md rename to website/blog/2021/08/10/2021-08-10-apisix-nginx.md index 7aaaf7f..7027eb4 100644 --- a/website/blog/2021-08-10-apisix-nginx.md +++ b/website/blog/2021/08/10/2021-08-10-apisix-nginx.md @@ -1,14 +1,14 @@ --- title: "Apache APISIX 架构分析：如何动态管理 Nginx 集群？" author: "陶辉" -keywords: +keywords: - API 网关 - Apache APISIX - Nginx - Lua - 动态管理 date: "2021-08-10" -description: 本文转发自陶辉个人博客，主要介绍了基于APISIX 2.8 版本、OpenResty 1.19.3.2 版本以及 Nginx 1.19.3 版本进行 Apache APISIX 实现 REST API 远程控制 Nginx 集群的原理讲解。 +description: 本文转发自陶辉个人博客，主要介绍了基于 APISIX 2.8 版本、OpenResty 1.19.3.2 版本以及 Nginx 1.19.3 版本进行 Apache APISIX 实现 REST API 远程控制 Nginx 集群的原理讲解。 tags: [Technology] draft: true --- @@ -194,7 +194,7 @@ Apache APISIX 将需要监控的配置以不同的前缀存入了 etcd，目前 * /apisix/plugin_metadata/：部分插件的元数据 * /apisix/plugins/：所有 Plugin 插件的列表 * /apisix/proto/：当透传 gRPC 协议时，部分插件需要转换协议内容，该配置存储 protobuf 消息定义 -* /apisix/routes/：路由信息，是 HTTP请 求匹配的入口，可以直接指定上游 Server，也可以挂载 services 或者 upstream +* /apisix/routes/：路由信息，是 HTTP 请 求匹配的入口，可以直接指定上游 Server，也可以挂载 services 或者 upstream * /apisix/services/：可以将相似的 router 中的共性部分抽象为 services，再挂载 plugin * /apisix/ssl/：SSL 证书公、私钥及相关匹配规则 * /apisix/stream_routes/：OSI 四层网关的路由匹配规则 @@ -461,7 +461,7 @@ end 2021/08/03 17:15:28 [info] 16437#16437: *23572 [lua] upstreams.lua:72: key: /upstreams/1, client: 127.0.0.1, server: _, request: "PUT /apisix/admin/upstreams/1 HTTP/1.1", host: "127.0.0.1:9080" ``` -### 为什么新配置不 reload 就可以生效？ +### 为什么新配置不 reload 就可以生效 我们再来看 admin 请求执行完 Nginx Worker 进程可以立刻生效的原理。 @@ -476,7 +476,7 @@ end 上述过程虽然执行效率极高，却是写死在 find_config 阶段及 Nginx HTTP 框架中的，一旦变更必须在 nginx -s reload 后才能生效。因此，Apache APISIX 索性完全抛弃了上述流程。 -从 nginx.conf 中可以看到，访问任意域名、URI 的请求都会匹配到 `http_access_phase` 这个 lua函数： +从 nginx.conf 中可以看到，访问任意域名、URI 的请求都会匹配到 `http_access_phase` 这个 lua 函数： ```conf server { @@ -510,7 +510,7 @@ end Nginx 集群的管理必须依赖中心化配置组件，而高可靠又具备 watch 推送机制的 etcd 无疑是最合适的选择！虽然当下 Resty 生态没有 gRPC 客户端，但每个 Worker 进程直接通过 HTTP/1.1 协议同步 etcd 配置仍不失为一个好的方案。 -动态修改 Nginx 配置的关键在于2点：Lua 语言的灵活度远高于 nginx.conf 语法，而且 Lua 代码可以通过 loadstring 从外部数据中导入。当然，为了保障路由匹配的执行效率，Apache APISIX 通过 C 语言实现了前缀基数树，基于 Host、Method、URI 进行请求匹配，在保障动态性的基础上提升了性能。 +动态修改 Nginx 配置的关键在于 2 点：Lua 语言的灵活度远高于 nginx.conf 语法，而且 Lua 代码可以通过 loadstring 从外部数据中导入。当然，为了保障路由匹配的执行效率，Apache APISIX 通过 C 语言实现了前缀基数树，基于 Host、Method、URI 进行请求匹配，在保障动态性的基础上提升了性能。 Apache APISIX 拥有许多优秀的设计，本文仅讨论了 Nginx 集群的动态管理。 diff --git a/website/blog/2021-08-11-interview-TuZhengsong.md b/website/blog/2021/08/11/2021-08-11-interview-TuZhengsong.md similarity index 100% rename from website/blog/2021-08-11-interview-TuZhengsong.md rename to website/blog/2021/08/11/2021-08-11-interview-TuZhengsong.md diff --git a/website/blog/2021-08-12-Chaos-Mesh-Helps-Apache-APISIX-Improve-System-Stability.md b/website/blog/2021/08/12/2021-08-12-Chaos-Mesh-Helps-Apache-APISIX-Improve-System-Stability.md similarity index 100% rename from website/blog/2021-08-12-Chaos-Mesh-Helps-Apache-APISIX-Improve-System-Stability.md rename to website/blog/2021/08/12/2021-08-12-Chaos-Mesh-Helps-Apache-APISIX-Improve-System-Stability.md diff --git a/website/blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md b/website/blog/2021/08/14/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md similarity index 100% rename from website/blog/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md rename to website/blog/2021/08/14/2021-08-14-contributors-the-golden-metric-of-openSource-projects-en.md diff --git a/website/blog/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md b/website/blog/2021/08/16/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md similarity index 99% rename from website/blog/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md rename to website/blog/2021/08/16/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md index c40145d..b578c26 100644 --- a/website/blog/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md +++ b/website/blog/2021/08/16/2021-08-16-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md @@ -226,7 +226,7 @@ curl -XPOST 127.0.0.1:9080/apisix/admin/routes -H "X-Api-Key: edd1c9f034335f136 2. Enter the username and password for the user's Okta account and click "Sign In" to log in to your Okta account. 3. After successful login, you can access the get page in "httpbin.org". The "httpbin.org/get" page will return the requested data with X-Access-Token,X-Id-Token, and X-Userinfo as follows. - ``` + ```sh "X-Access-Token": "******Y0RPcXRtc0FtWWVuX2JQaFo1ZVBvSlBNdlFHejN1dXY5elV3IiwiYWxnIjoiUlMyNTYifQ.***TVER3QUlPbWZYSVRzWHRxRWh2QUtQMWRzVDVGZHZnZzAiLCJpc3MiOiJodHRwczovL3FxdGVzdG1hbi5va3RhLmNvbSIsImF1ZCI6Imh0dHBzOi8vcXF0ZXN0bWFuLm9rdGEuY29tIiwic3ViIjoiMjgzMDE4Nzk5QHFxLmNvbSIsImlhdCI6MTYyODEyNjIyNSwiZXhwIjoxNjI4MTI5ODI1LCJjaWQiOiIwb2ExMWc4ZDg3TzBGQ0dYZzY5NiIsInVpZCI6IjAwdWEwNWVjZEZmV0tMS3VvNjk1Iiwic2NwIjpbIm9wZW5pZCIsInByb2Zpb***.****iBshIcJhy8QNvzAFD0fV4gh7OAdTXFMu5k0hk0JeIU6Tfg_Mh-josfap3 [...] "X-Id-Token": "******aTdDRDJnczF5RnlXMUtPZUtuSUpQdyIsImFtciI6WyJwd2QiXSwic3ViIjoiMDB1YTA1ZWNkRmZXS0xLdW82OTUiLCJpc3MiOiJodHRwczpcL1wvcXF0ZXN0bWFuLm9rdGEuY29tIiwiYXVkIjoiMG9hMTFnOGQ4N08wRkNHWGc2OTYiLCJuYW1lIjoiUGV0ZXIgWmh1IiwianRpIjoiSUQuNGdvZWo4OGUyX2RuWUI1VmFMeUt2djNTdVJTQWhGNS0tM2l3Z0p5TTcxTSIsInZlciI6MSwicHJlZmVycmVkX3VzZXJuYW1lIjoiMjgzMDE4Nzk5QHFxLmNvbSIsImV4cCI6MTYyODEyOTgyNSwiaWRwIjoiMDBvYTA1OTFndHAzMDhFbm02OTUiLCJub25jZSI6ImY3MjhkZDMxMWRjNGY3MTI4YzlmNjViOGYzYjJkMDgyIiwiaWF0IjoxN [...] "X-Userinfo": "*****lfbmFtZSI6IlpodSIsImxvY2FsZSI6ImVuLVVTIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiMjgzMDE4Nzk5QHFxLmNvbSIsInVwZGF0ZWRfYXQiOjE2MjgwNzA1ODEsInpvbmVpbmZvIjoiQW1lcmljYVwvTG9zX0FuZ2VsZXMiLCJzdWIiOiIwMHVhMDVlY2RGZldLTEt1bzY5NSIsImdpdmVuX25hbWUiOiJQZXRlciIsIm5hbWUiOiJQZXRl****" diff --git a/website/blog/2021-08-17-interview-airwallex.md b/website/blog/2021/08/17/2021-08-17-interview-airwallex.md similarity index 100% rename from website/blog/2021-08-17-interview-airwallex.md rename to website/blog/2021/08/17/2021-08-17-interview-airwallex.md diff --git a/website/blog/2021-08-18-Auth-with-Casbin-in-Apache-APISIX.md b/website/blog/2021/08/18/2021-08-18-Auth-with-Casbin-in-Apache-APISIX.md similarity index 100% rename from website/blog/2021-08-18-Auth-with-Casbin-in-Apache-APISIX.md rename to website/blog/2021/08/18/2021-08-18-Auth-with-Casbin-in-Apache-APISIX.md diff --git a/website/blog/2021-08-19-go-makes-Apache-APISIX-better.md b/website/blog/2021/08/19/2021-08-19-go-makes-Apache-APISIX-better.md similarity index 100% rename from website/blog/2021-08-19-go-makes-Apache-APISIX-better.md rename to website/blog/2021/08/19/2021-08-19-go-makes-Apache-APISIX-better.md diff --git a/website/blog/2021-08-19-weekly-report.md b/website/blog/2021/08/19/2021-08-19-weekly-report.md similarity index 96% rename from website/blog/2021-08-19-weekly-report.md rename to website/blog/2021/08/19/2021-08-19-weekly-report.md index cd86544..350f7aa 100644 --- a/website/blog/2021-08-19-weekly-report.md +++ b/website/blog/2021/08/19/2021-08-19-weekly-report.md @@ -1,5 +1,5 @@ --- -title: Apache APISIX 社区周报 ｜ 2021年8月9日～8月15日 +title: Apache APISIX 社区周报 ｜ 08-09 至 08-15 keywords: - 社区周报 - 贡献者 diff --git a/website/blog/2021-08-21-shanghai-meetup.md b/website/blog/2021/08/21/2021-08-21-shanghai-meetup.md similarity index 100% rename from website/blog/2021-08-21-shanghai-meetup.md rename to website/blog/2021/08/21/2021-08-21-shanghai-meetup.md diff --git a/website/blog/2021-08-23-ApacheCon-Asia-2021.md b/website/blog/2021/08/23/2021-08-23-ApacheCon-Asia-2021.md similarity index 100% rename from website/blog/2021-08-23-ApacheCon-Asia-2021.md rename to website/blog/2021/08/23/2021-08-23-ApacheCon-Asia-2021.md diff --git a/website/blog/2021-08-23-weekly-report.md b/website/blog/2021/08/23/2021-08-23-weekly-report.md similarity index 100% rename from website/blog/2021-08-23-weekly-report.md rename to website/blog/2021/08/23/2021-08-23-weekly-report.md diff --git a/website/blog/2021-08-24-shanghai-meetup-recap.md b/website/blog/2021/08/24/2021-08-24-shanghai-meetup-recap.md similarity index 95% rename from website/blog/2021-08-24-shanghai-meetup-recap.md rename to website/blog/2021/08/24/2021-08-24-shanghai-meetup-recap.md index 8deb7b9..3115a2b 100644 --- a/website/blog/2021-08-24-shanghai-meetup-recap.md +++ b/website/blog/2021/08/24/2021-08-24-shanghai-meetup-recap.md @@ -16,13 +16,13 @@ draft: true <!--truncate--> -Apache APISIX Meetup 上海站已于上周六（8月21日）顺利举办🎉🎉🎉 +Apache APISIX Meetup 上海站已于上周六（8 月 21 日）顺利举办🎉🎉🎉 本次 Meetup 由 [API7.AI](https://www.apiseven.com/zh) 发起，邀请了爱奇艺、AirWallex 空中云汇等合作伙伴，与 Apache APISIX 技术大咖、Apache APISIX PMC 成员、社区技术专家汇聚一堂，共同探讨了关于 Apache APISIX 社区发展、行业实践等话题。 一起来回顾下大会中令人难忘的精彩演讲吧！ -## 基于Apache APISIX，爱奇艺 API 网关的落地实践 +## 基于 Apache APISIX，爱奇艺 API 网关的落地实践 **讲师**：何聪 diff --git a/website/blog/2021-08-25-Auth-with-Casbin-in-Apache-APISIX.md b/website/blog/2021/08/25/2021-08-25-Auth-with-Casbin-in-Apache-APISIX.md similarity index 100% rename from website/blog/2021-08-25-Auth-with-Casbin-in-Apache-APISIX.md rename to website/blog/2021/08/25/2021-08-25-Auth-with-Casbin-in-Apache-APISIX.md diff --git a/website/blog/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md b/website/blog/2021/08/25/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md similarity index 96% rename from website/blog/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md rename to website/blog/2021/08/25/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md index 2bdf52a..1594dde 100644 --- a/website/blog/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md +++ b/website/blog/2021/08/25/2021-08-25-Using-the-Apache-APISIX-OpenID-Connect-Plugin-for-Centralized-Authentication.md @@ -9,7 +9,7 @@ keywords: - Apache APISIX - Okta - 集中认证 -description: 本文展示了使用 Apache APISIX OpenID Connect Plugin 进行 Okta 集中认证的过程。 本文包含了对Apache APISIX 和 Okta 集中认证的概念介绍，展示了在 Apache APISIX 中直接建立来自 Okta 的集中式身份认证的过程。这种集中认证的方法减少了开发者的学习和维护成本，提供了安全和精简的用户体验。 +description: 本文展示了使用 Apache APISIX OpenID Connect Plugin 进行 Okta 集中认证的过程。 本文包含了对 Apache APISIX 和 Okta 集中认证的概念介绍，展示了在 Apache APISIX 中直接建立来自 Okta 的集中式身份认证的过程。这种集中认证的方法减少了开发者的学习和维护成本，提供了安全和精简的用户体验。 tags: [Practical Case] draft: true --- @@ -18,11 +18,11 @@ draft: true <!--truncate--> -## 什么是 Apache APISIX？ +## 什么是 Apache APISIX [Apache APISIX](https://apisix.apache.org/) 是一个动态、实时、高性能的 API 网关，提供负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。Apache APISIX 不仅支持插件动态变更和热插拔，而且拥有众多实用的插件。Apache APISIX 的 OpenID Connect 插件支持 OpenID，用户可以使用该插件将身份认证从传统认证模式替换为集中认证模式。 -## 什么是身份认证？ +## 什么是身份认证 身份认证是指通过一定的手段，对用户的身份进行验证。应用通过身份认证识别用户身份，并根据用户身份 ID 从身份提供方（Identity Provider）获取详细的用户元数据，并以此判断用户是否拥有访问指定资源的权限。身份认证模式分为两大类：**传统认证模式**和**集中认证模式**。 @@ -43,7 +43,7 @@ draft: true 1. 简化应用开发流程，降低开发应用工作量和维护成本，避免各个应用重复开发身份认证代码。 2. 提高业务的安全性，集中身份认证模式在网关层面能够及时拦截未经身份认证的请求，保护后端的应用。 -## 什么是 OpenID？ +## 什么是 OpenID OpenID 是一种集中认证模式，它是一个去中心化的身份认证系统。使用 OpenID 的好处是，用户只需要在一个 OpenID 身份提供方的网站上注册和登录，使用一份账户密码信息即可访问不同应用。Okta 是一个常见的 OpenID 身份提供方，Apache APISIX OpenID Connect 插件支持 OpenID，所以用户可以使用该插件将传统认证模式替换为集中认证模式。 @@ -61,7 +61,7 @@ OpenID 认证过程有以下 7 个步骤，如下图所示。  -## 如何使用 Apache APISIX 的 OpenID Connect 插件配置 Okta 认证？ +## 如何使用 Apache APISIX 的 OpenID Connect 插件配置 Okta 认证 使用 Apache APISIX OpenID Connect 插件配置 Okta 认证的过程非常简单，只需三步即可完成 Okta 配置 ，从传统身份认证模式切换到集中身份认证模式。下文讲述了使用 Apache APISIX 的 OpenID Connect 插件配置 Okta 认证的操作步骤。 @@ -220,7 +220,7 @@ curl -XPOST 127.0.0.1:9080/apisix/admin/routes -H "X-Api-Key: edd1c9f034335f136 3. 登录成功之后，能成功访问到 httpbin.org 中的 get 页面。该 httpbin.org/get 页面将返回请求的数据如下： - ``` + ```sh "X-Access-Token": "******Y0RPcXRtc0FtWWVuX2JQaFo1ZVBvSlBNdlFHejN1dXY5elV3IiwiYWxnIjoiUlMyNTYifQ.***TVER3QUlPbWZYSVRzWHRxRWh2QUtQMWRzVDVGZHZnZzAiLCJpc3MiOiJodHRwczovL3FxdGVzdG1hbi5va3RhLmNvbSIsImF1ZCI6Imh0dHBzOi8vcXF0ZXN0bWFuLm9rdGEuY29tIiwic3ViIjoiMjgzMDE4Nzk5QHFxLmNvbSIsImlhdCI6MTYyODEyNjIyNSwiZXhwIjoxNjI4MTI5ODI1LCJjaWQiOiIwb2ExMWc4ZDg3TzBGQ0dYZzY5NiIsInVpZCI6IjAwdWEwNWVjZEZmV0tMS3VvNjk1Iiwic2NwIjpbIm9wZW5pZCIsInByb2Zpb***.****iBshIcJhy8QNvzAFD0fV4gh7OAdTXFMu5k0hk0JeIU6Tfg_Mh-josfap3 [...] "X-Id-Token": "******aTdDRDJnczF5RnlXMUtPZUtuSUpQdyIsImFtciI6WyJwd2QiXSwic3ViIjoiMDB1YTA1ZWNkRmZXS0xLdW82OTUiLCJpc3MiOiJodHRwczpcL1wvcXF0ZXN0bWFuLm9rdGEuY29tIiwiYXVkIjoiMG9hMTFnOGQ4N08wRkNHWGc2OTYiLCJuYW1lIjoiUGV0ZXIgWmh1IiwianRpIjoiSUQuNGdvZWo4OGUyX2RuWUI1VmFMeUt2djNTdVJTQWhGNS0tM2l3Z0p5TTcxTSIsInZlciI6MSwicHJlZmVycmVkX3VzZXJuYW1lIjoiMjgzMDE4Nzk5QHFxLmNvbSIsImV4cCI6MTYyODEyOTgyNSwiaWRwIjoiMDBvYTA1OTFndHAzMDhFbm02OTUiLCJub25jZSI6ImY3MjhkZDMxMWRjNGY3MTI4YzlmNjViOGYzYjJkMDgyIiwiaWF0IjoxN [...] "X-Userinfo": "*****lfbmFtZSI6IlpodSIsImxvY2FsZSI6ImVuLVVTIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiMjgzMDE4Nzk5QHFxLmNvbSIsInVwZGF0ZWRfYXQiOjE2MjgwNzA1ODEsInpvbmVpbmZvIjoiQW1lcmljYVwvTG9zX0FuZ2VsZXMiLCJzdWIiOiIwMHVhMDVlY2RGZldLTEt1bzY5NSIsImdpdmVuX25hbWUiOiJQZXRlciIsIm5hbWUiOiJQZXRl****" @@ -246,7 +246,7 @@ curl -XPOST 127.0.0.1:9080/apisix/admin/routes -H "X-Api-Key: edd1c9f034335f136 ## 关于 Okta -Okta 是一个可定制的、安全的集中身份认证解决方案。Okta 可以为您的应用程序添加认证和授权。不需要自己编写代码，即可在您的应用程序中直接获得可扩展的认证。您可以将应用程序连接到Okta，并定义用户的登录方式。每次用户尝试认证时，Okta都会验证他们的身份，并将所需信息发回给您的应用程序。 +Okta 是一个可定制的、安全的集中身份认证解决方案。Okta 可以为您的应用程序添加认证和授权。不需要自己编写代码，即可在您的应用程序中直接获得可扩展的认证。您可以将应用程序连接到 Okta，并定义用户的登录方式。每次用户尝试认证时，Okta 都会验证他们的身份，并将所需信息发回给您的应用程序。 ## 关于 Apache APISIX diff --git a/website/blog/2021-08-25-Why-Apache-APISIX-chose-Nginx-and-Lua.md b/website/blog/2021/08/25/2021-08-25-Why-Apache-APISIX-chose-Nginx-and-Lua.md similarity index 100% rename from website/blog/2021-08-25-Why-Apache-APISIX-chose-Nginx-and-Lua.md rename to website/blog/2021/08/25/2021-08-25-Why-Apache-APISIX-chose-Nginx-and-Lua.md diff --git a/website/blog/2021-08-27-release-apache-apisix-2.9-en.md b/website/blog/2021/08/27/2021-08-27-release-apache-apisix-2.9-en.md similarity index 100% rename from website/blog/2021-08-27-release-apache-apisix-2.9-en.md rename to website/blog/2021/08/27/2021-08-27-release-apache-apisix-2.9-en.md diff --git a/website/blog/2021-08-27-release-apache-apisix-2.9.md b/website/blog/2021/08/27/2021-08-27-release-apache-apisix-2.9.md similarity index 100% rename from website/blog/2021-08-27-release-apache-apisix-2.9.md rename to website/blog/2021/08/27/2021-08-27-release-apache-apisix-2.9.md diff --git a/website/blog/2021-08-30-Ingress-Meeting.md b/website/blog/2021/08/30/2021-08-30-Ingress-Meeting.md similarity index 100% rename from website/blog/2021-08-30-Ingress-Meeting.md rename to website/blog/2021/08/30/2021-08-30-Ingress-Meeting.md diff --git a/website/blog/2021-08-30-weekly-report.md b/website/blog/2021/08/30/2021-08-30-weekly-report.md similarity index 99% rename from website/blog/2021-08-30-weekly-report.md rename to website/blog/2021/08/30/2021-08-30-weekly-report.md index c9a21fd..09aef64 100644 --- a/website/blog/2021-08-30-weekly-report.md +++ b/website/blog/2021/08/30/2021-08-30-weekly-report.md @@ -55,7 +55,7 @@ Apache APISIX 从开源第一天就以社区方式成长，迅速成为全世界 **链接**：[Issue #3601](https://github.com/apache/apisix/issues/3601) -**问题描述**：目前 APISIX 只有请求-响应 gRPC 代理的单元测试，没有流式 gRPC 的相关测试。需要为其添加流式gRPC的测试用例。 +**问题描述**：目前 APISIX 只有请求-响应 gRPC 代理的单元测试，没有流式 gRPC 的相关测试。需要为其添加流式 gRPC 的测试用例。 ### Issue #3931 diff --git "a/website/blog/2021-08-31-Apache APISIX \303\227 KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md" "b/website/blog/2021/08/31/2021-08-31-Apache APISIX \303\227 KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md" similarity index 100% rename from "website/blog/2021-08-31-Apache APISIX \303\227 KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md" rename to "website/blog/2021/08/31/2021-08-31-Apache APISIX \303\227 KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md" diff --git a/website/blog/2021-09-06-python-helps-you-quickly-with-Apache-APISIX-development.md b/website/blog/2021/09/06/2021-09-06-python-helps-you-quickly-with-Apache-APISIX-development.md similarity index 100% rename from website/blog/2021-09-06-python-helps-you-quickly-with-Apache-APISIX-development.md rename to website/blog/2021/09/06/2021-09-06-python-helps-you-quickly-with-Apache-APISIX-development.md diff --git a/website/blog/2021-09-07-how-to-use-apisix-auth.md b/website/blog/2021/09/07/2021-09-07-how-to-use-apisix-auth.md similarity index 99% rename from website/blog/2021-09-07-how-to-use-apisix-auth.md rename to website/blog/2021/09/07/2021-09-07-how-to-use-apisix-auth.md index a0df2b0..eee3c3e 100644 --- a/website/blog/2021-09-07-how-to-use-apisix-auth.md +++ b/website/blog/2021/09/07/2021-09-07-how-to-use-apisix-auth.md @@ -21,7 +21,7 @@ draft: true 如上图，Jack 通过账号密码请求服务端应用，服务端应用中需要有一个专门用做身份认证的模块来处理这部分的逻辑。请求处理完毕之后，如果使用 JWT Token 认证方式，服务器会反馈一个 Token 去标识这个用户为 Jack。如果登录过程中账号密码输入错误，就会导致身份认证失败。这个场景大家肯定都非常熟悉，这里就不做展开举例了。 -## 网络身份认证的意义在哪里？ +## 网络身份认证的意义在哪里 ### 安全性 diff --git a/website/blog/2021-09-07-iQIYI-usercase.md b/website/blog/2021/09/07/2021-09-07-iQIYI-usercase.md similarity index 87% rename from website/blog/2021-09-07-iQIYI-usercase.md rename to website/blog/2021/09/07/2021-09-07-iQIYI-usercase.md index 62e8e4b..c1dfef2 100644 --- a/website/blog/2021-09-07-iQIYI-usercase.md +++ b/website/blog/2021/09/07/2021-09-07-iQIYI-usercase.md @@ -31,13 +31,13 @@ draft: true 在选择 Apache APISIX 之前，爱奇艺平台已经在使用 Kong 了，但是后来 Kong 被放弃了。 -### 为什么放弃 Kong？ +### 为什么放弃 Kong  -Kong 使用 PostgreSQL 来存储它的信息，这显然不是一个好方式。 同时在调研过程中我们查看了 Apache APISIX 与 Kong 的性能的对比，在性能优化方面 Apache APISIX 比 Kong 提升了10 倍，这个指标是非常让人惊喜的。 同时我们也比较了一些主要的网关产品，Apache APISIX 的响应延迟比其它网关低 50% 以上，在 CPU 达到 70% 以上时 Apache APISIX 仍能稳定运转。 +Kong 使用 PostgreSQL 来存储它的信息，这显然不是一个好方式。 同时在调研过程中我们查看了 Apache APISIX 与 Kong 的性能的对比，在性能优化方面 Apache APISIX 比 Kong 提升了 10 倍，这个指标是非常让人惊喜的。 同时我们也比较了一些主要的网关产品，Apache APISIX 的响应延迟比其它网关低 50% 以上，在 CPU 达到 70% 以上时 Apache APISIX 仍能稳定运转。 -我们也发现 Apache APISIX 其实和 Kong一样，都是基于 OpenResty 技术层面做的开发，所以在技术层面的迁移成本就比较低。而且 Apache APISIX 具有良好的环境适应性，能够被轻易地部署在包括云计算平台在内的各种环境上。 +我们也发现 Apache APISIX 其实和 Kong 一样，都是基于 OpenResty 技术层面做的开发，所以在技术层面的迁移成本就比较低。而且 Apache APISIX 具有良好的环境适应性，能够被轻易地部署在包括云计算平台在内的各种环境上。 同时也看到 Apache APISIX 整个开源项目的活跃度非常高，对问题的处理非常迅速，并且项目的云原生架构也符合我司后续规划，所以我们选择了 Apache APISIX。 @@ -55,7 +55,7 @@ Kong 使用 PostgreSQL 来存储它的信息，这显然不是一个好方式。 数据面主要面向前端用户，从 LB 到网关整个架构都是多地多链路灾备部署，以用户就近接入原则进行布点。 -从控制面的角度来说，因为多集群构成，会存在一个微服务平台，去做集群管理和服务管理。微服务平台可以让用户体验服务暴露的一站式服务，立即使用，无需提交工单。控制面后端会有 Gateway Controller 和 Service Controller，前者主要控制所有的API的创建、插件等相关配置，后者则是控制服务注册注销和健康检查。 +从控制面的角度来说，因为多集群构成，会存在一个微服务平台，去做集群管理和服务管理。微服务平台可以让用户体验服务暴露的一站式服务，立即使用，无需提交工单。控制面后端会有 Gateway Controller 和 Service Controller，前者主要控制所有的 API 的创建、插件等相关配置，后者则是控制服务注册注销和健康检查。 ### 应用场景二：基础功能 @@ -113,13 +113,13 @@ Kong 使用 PostgreSQL 来存储它的信息，这显然不是一个好方式。 ### 成果四：优化了 ETCD 连接数量的性能问题 -目前是 Apache APISIX 的每个 worker 都会跟 ETCD 连接，每一个监听目录都会去建一个连接。比如一台物理机是 80 core，监听目录有 10个，单台网关服务器就有 800 个连接。一个网关集群 10 台的话，8000 个连接对 ETCD 压力蛮大的。我们做的优化是只拿一个 worker 去监听有限的必要目录，和其余 worker 之间共享信息。 +目前是 Apache APISIX 的每个 worker 都会跟 ETCD 连接，每一个监听目录都会去建一个连接。比如一台物理机是 80 core，监听目录有 10 个，单台网关服务器就有 800 个连接。一个网关集群 10 台的话，8000 个连接对 ETCD 压力蛮大的。我们做的优化是只拿一个 worker 去监听有限的必要目录，和其余 worker 之间共享信息。 ### 待优化 除了上述问题，还有一些问题也正在努力优化中。 -1. 大量 API 的问题，即使APISIX能够支持，我们也要考虑其他依赖组件的瓶颈。比如上述的 ETCD、Prometheus 监控和日志服务。所以后续我们可能会采取大集群共享和小集群独立这两种方式来混合部署业务，比如一些重要业务我们会以小集群方式进行部署。 +1. 大量 API 的问题，即使 APISIX 能够支持，我们也要考虑其他依赖组件的瓶颈。比如上述的 ETCD、Prometheus 监控和日志服务。所以后续我们可能会采取大集群共享和小集群独立这两种方式来混合部署业务，比如一些重要业务我们会以小集群方式进行部署。 2. 关于 Prometheus 监控指标，后续我们也会进行相应的缩减和优化，对 DNS 服务发现这块做更多的优化。 ## 对 Apache APISIX 的期望 diff --git a/website/blog/2021-09-09-how-to-contribute-to-an-OpenSource-without-coding.md b/website/blog/2021/09/09/2021-09-09-how-to-contribute-to-an-OpenSource-without-coding.md similarity index 100% rename from website/blog/2021-09-09-how-to-contribute-to-an-OpenSource-without-coding.md rename to website/blog/2021/09/09/2021-09-09-how-to-contribute-to-an-OpenSource-without-coding.md diff --git a/website/blog/2021-09-13-china-mobile-cloud-usercase.md b/website/blog/2021/09/13/2021-09-13-china-mobile-cloud-usercase.md similarity index 97% rename from website/blog/2021-09-13-china-mobile-cloud-usercase.md rename to website/blog/2021/09/13/2021-09-13-china-mobile-cloud-usercase.md index f13cfe5..b6c30ad 100644 --- a/website/blog/2021-09-13-china-mobile-cloud-usercase.md +++ b/website/blog/2021/09/13/2021-09-13-china-mobile-cloud-usercase.md @@ -29,7 +29,7 @@ draft: true ## 为什么选择 Apache APISIX 作为网关 -### 为什么抛弃 Nginx？ +### 为什么抛弃 Nginx #### 理由一：综合能力欠缺 @@ -39,7 +39,7 @@ Apache APISIX 作为一个微服务网关，与其他 API 网关相比，它的 众所周知，像 Nginx 所有的功能都是基于配置文件来实现的，因而像 Proxy 存在路由上游的证书不能动态加载。Apache APISIX 支持全平台、多协议、全动态、精细化路由、安全防护，而且运维友好，可以对接 Prometheus、SkyWalking 等，有高度扩展能力，这些都是实际生产中需要的能力。 -### 在技术选型时，为什么我们最终选择 Apache APISIX ？ +### 在技术选型时，为什么我们最终选择 Apache APISIX #### 理由一：基于产品架构的需要 @@ -55,7 +55,7 @@ Apache APISIX 的特性、功能插件、自定义开发功能，都可以在后  -## 在 Apache APISIX 的数据面，我们改了些什么？ +## 在 Apache APISIX 的数据面，我们改了些什么 ### 改进一：内外网请求分离访问 @@ -84,15 +84,15 @@ limit-conn key 这个插件主要是支持 remote_addr、server_addr、X-Forward ### 改进四：新增功能特性开关 -#### 开关1：临时关闭某个对象存储功能 +#### 开关 1：临时关闭某个对象存储功能 在网关层通过接入 Apache APISIX，兼容了 S3 接口规范，避免对后端服务的接入层、持久化层的资源浪费。 -#### 开关2：支持 GET 请求优先级最高 +#### 开关 2：支持 GET 请求优先级最高 实现了在支持 GET 请求优先的情况下，在取回用户数据时 GET 请求优先级最高，高于 PUT 、DELETE 等请求。 -#### 开关3：对 Ordered List 请求返回 501 Not Implemented +#### 开关 3：对 Ordered List 请求返回 501 Not Implemented 在对象存储中一般会有对桶的 Ordered List 的功能需求。第三、四代移动云对象存储面向的都是百亿文件对象，如果依旧使用 Ordered List，一方面请求访问后端响应的时间会特别长，另一方面会占用较多资源，对后端的稳定性提出较大的挑战。 diff --git a/website/blog/2021-09-14-youzan.md b/website/blog/2021/09/14/2021-09-14-youzan.md similarity index 100% rename from website/blog/2021-09-14-youzan.md rename to website/blog/2021/09/14/2021-09-14-youzan.md diff --git a/website/blog/2021-09-15-weekly-report.md b/website/blog/2021/09/15/2021-09-15-weekly-report.md similarity index 98% rename from website/blog/2021-09-15-weekly-report.md rename to website/blog/2021/09/15/2021-09-15-weekly-report.md index e7caff4..270584e 100644 --- a/website/blog/2021-09-15-weekly-report.md +++ b/website/blog/2021/09/15/2021-09-15-weekly-report.md @@ -91,7 +91,7 @@ make: *** [deps] Error 1 - [支持配置后退 SNI](https://github.com/apache/apisix/pull/5000)(贡献者：spacewander) - [proxy-mirror 支持按比例镜像请求](https://github.com/apache/apisix/pull/4965)(贡献者：okaybase) - [Control API 新增 dump 路由配置](https://github.com/apache/apisix/pull/5011)(贡献者：Zheaoli) -- [dashboard支持Service Discovery 配置](https://github.com/apache/apisix-dashboard/pull/2081)(贡献者：bzp2010) +- [dashboard 支持 Service Discovery 配置](https://github.com/apache/apisix-dashboard/pull/2081)(贡献者：bzp2010) - [dashboard Route 高级配置条件中支持内置参数配置](https://github.com/apache/apisix-dashboard/pull/1984)(贡献者：lookbrook) - [dashboard Upstream 支持 Keepalive Pool 配置](https://github.com/apache/apisix-dashboard/pull/2117)(贡献者：bzp2010) diff --git a/website/blog/2021-09-16-tencent-cloud.md b/website/blog/2021/09/16/2021-09-16-tencent-cloud.md similarity index 99% rename from website/blog/2021-09-16-tencent-cloud.md rename to website/blog/2021/09/16/2021-09-16-tencent-cloud.md index 93256f1..56698ce 100644 --- a/website/blog/2021-09-16-tencent-cloud.md +++ b/website/blog/2021/09/16/2021-09-16-tencent-cloud.md @@ -47,7 +47,7 @@ draft: true Kong 和 Apache APISIX 所使用的技术栈相同，都是 OpenResty。但是在存储依赖这一栏，Kong 依赖的是关系型数据库 PostgreSQL。在软件行业，数据库的高可用配置是非常复杂的。不仅需要配备专门的 DBA，而且实施难度也非常大。关系型数据库太重了，我们并不需要使用关系型数据库来保证 ACID 和 MVCC。 -### 为什么选择了 Apache APISIX？ +### 为什么选择了 Apache APISIX Apache APISIX 在存储依赖和路由规则这两方面做的非常好，很适合我们的业务场景。我们的业务比较看重路由灵活度和路由匹配算法。目前已接入 50 多个上游和数百条路由规则，所以我们希望路由匹配的性能越高越好。Apache APISIX 路由匹配算法复杂度明显优于 Kong，且配置生效时间小于 1ms，单核 QPS 远高于 Kong。综合以上技术和操作层面，我们最终选择了 Apache APISIX。 diff --git a/website/blog/2021-09-18-xiaodian-usercase.md b/website/blog/2021/09/18/2021-09-18-xiaodian-usercase.md similarity index 98% rename from website/blog/2021-09-18-xiaodian-usercase.md rename to website/blog/2021/09/18/2021-09-18-xiaodian-usercase.md index c8ba77b..155560d 100644 --- a/website/blog/2021-09-18-xiaodian-usercase.md +++ b/website/blog/2021/09/18/2021-09-18-xiaodian-usercase.md @@ -120,9 +120,9 @@ OpenShift 具有非常严格的 SCC 机制，在利用 OpenShift 去部署 Apach 在使用期间我们也观察到 Load 一直突高不下的情况，经检查发现 etcd 内的数据量已达到 600 多兆，所以我们采取了定期压缩 etcd 的措施，将历史事物数据全部清除。具体代码可参考： -``` -ETCDCTL_API=3 etcdctl --endpoints=http://etcd-1:2379 compact 1693729 -ETCDCTL_API=3 etcdctl --endpoints=http://etcd-1:2379 defrag +```sh +$ ETCDCTL_API=3 etcdctl --endpoints=http://etcd-1:2379 compact 1693729 +$ ETCDCTL_API=3 etcdctl --endpoints=http://etcd-1:2379 defrag ``` ### 获取 Client-IP diff --git a/website/blog/2021-09-24-youpaicloud-usercase.md b/website/blog/2021/09/24/2021-09-24-youpaicloud-usercase.md similarity index 100% rename from website/blog/2021-09-24-youpaicloud-usercase.md rename to website/blog/2021/09/24/2021-09-24-youpaicloud-usercase.md diff --git a/website/blog/2021-09-28-WPS-usercase.md b/website/blog/2021/09/28/2021-09-28-WPS-usercase.md similarity index 98% rename from website/blog/2021-09-28-WPS-usercase.md rename to website/blog/2021/09/28/2021-09-28-WPS-usercase.md index 51d0ab8..a6a2872 100644 --- a/website/blog/2021-09-28-WPS-usercase.md +++ b/website/blog/2021/09/28/2021-09-28-WPS-usercase.md @@ -30,7 +30,7 @@ draft: true 后续我们对 API Gateway 功能有了强需求后，开始去调研相关的开源网关产品。 -## 为什么选择了 Apache APISIX？ +## 为什么选择了 Apache APISIX 实际上 2019 年年底开始调研网关产品时，Kong 算是一个比较流行的选择。 @@ -73,7 +73,7 @@ draft: true 一般公司网关架构中，都会涉及多台机器，有的可能多至几百台，同时每台机器还要顾及 worker 数量。所以当多台机器监控相同 Key 时，etcd 的压力就会比较大，因为 etcd 的其中一个机制是为了保证数据一致性，需要所有事件返回给监听请求后才能处理新请求，当发送缓冲满了后就会丢弃请求。所以当多台机器同时监听时就会导致 etcd 超时运行，提示 Overload 报错等状况。 -针对上述问题，我们使用了自研的 etcd Proxy。之前 Apache APISIX 与 etcd 的连接关系如下图左侧所示，每个节点均与 etcd 连接。所以作为一个大规模入口时，连接数量会特别大，对etcd 造成压力。 +针对上述问题，我们使用了自研的 etcd Proxy。之前 Apache APISIX 与 etcd 的连接关系如下图左侧所示，每个节点均与 etcd 连接。所以作为一个大规模入口时，连接数量会特别大，对 etcd 造成压力。  diff --git a/website/blog/2021-09-29-release-apache-apisix-2.10-en.md b/website/blog/2021/09/29/2021-09-29-release-apache-apisix-2.10-en.md similarity index 100% rename from website/blog/2021-09-29-release-apache-apisix-2.10-en.md rename to website/blog/2021/09/29/2021-09-29-release-apache-apisix-2.10-en.md diff --git a/website/blog/2021-09-29-release-apache-apisix-2.10.md b/website/blog/2021/09/29/2021-09-29-release-apache-apisix-2.10.md similarity index 100% rename from website/blog/2021-09-29-release-apache-apisix-2.10.md rename to website/blog/2021/09/29/2021-09-29-release-apache-apisix-2.10.md diff --git a/website/blog/2021-09-30-weekly-report.md b/website/blog/2021/09/30/2021-09-30-weekly-report.md similarity index 96% rename from website/blog/2021-09-30-weekly-report.md rename to website/blog/2021/09/30/2021-09-30-weekly-report.md index dd699b9..b9ec8f0f 100644 --- a/website/blog/2021-09-30-weekly-report.md +++ b/website/blog/2021/09/30/2021-09-30-weekly-report.md @@ -96,7 +96,7 @@ property "price" is required - [hmac-auth 支持校验请求体](https://github.com/apache/apisix/pull/5038)（贡献者：[arthur-zhang](https://github.com/arthur-zhang)） -- [APISIX Ingress controller 集成了 cert-manager ，用户可以更方便的管理TLS证书，并与 APISIX Ingress 配合使用](https://github.com/apache/apisix-ingress-controller/pull/685)（贡献者：[lingsamuel](https://github.com/lingsamuel)） +- [APISIX Ingress controller 集成了 cert-manager ，用户可以更方便的管理 TLS 证书，并与 APISIX Ingress 配合使用](https://github.com/apache/apisix-ingress-controller/pull/685)（贡献者：[lingsamuel](https://github.com/lingsamuel)） - [- APISIX Dashboard 支持多种配置文件](https://github.com/apache/apisix-dashboard/pull/1946)（贡献者：[bzp2010](https://github.com/bzp2010)） diff --git a/website/blog/2021-10-01-openEuler.md b/website/blog/2021/10/01/2021-10-01-openEuler.md similarity index 97% rename from website/blog/2021-10-01-openEuler.md rename to website/blog/2021/10/01/2021-10-01-openEuler.md index 39aa206..4881fba 100644 --- a/website/blog/2021-10-01-openEuler.md +++ b/website/blog/2021/10/01/2021-10-01-openEuler.md @@ -20,7 +20,7 @@ draft: true <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)》。 +[温铭](https://github.com/moonming)，Apache Member，Apache APISIX PMC Chair，OpenResty 的核心开发者，前 360 开源技术委员会委员，十余年开发经验。著有极客时间专栏《[OpenResty 从入门到实战](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"}} />
![https://static.apiseven.com/202108/1633068755509-66b85782-ecca-43cc-bbcc-5a7b11cee0f4.png"](https://static.apiseven.com/202108/1633068755509-66b85782-ecca-43cc-bbcc-5a7b11cee0f4.png"){kind=link}
![https://static.apiseven.com/202108/1633068755501-b52403ee-c43a-4da7-9ca7-46bc457da6fa.png"](https://static.apiseven.com/202108/1633068755501-b52403ee-c43a-4da7-9ca7-46bc457da6fa.png"){kind=link}