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 0ef2aec fix(CI): Update lint workflow so the Markdown and YAML
linters run (#132)
0ef2aec is described below
commit 0ef2aec2b09d1af2ce7f208db469c4b1d04e5ab1
Author: John Bampton <[email protected]>
AuthorDate: Mon Jan 11 13:40:51 2021 +1000
fix(CI): Update lint workflow so the Markdown and YAML linters run (#132)
Due to the ASF's policies changing we cannot use the original GitHub
Actions for linting as they are not approved
Lint Markdown
---
.github/workflows/lint.yml | 11 ++++++++++-
.../blog/2020-12-18-a-first-look-at-kubernetes-service-api.md | 2 +-
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
index 618187f..aa87558 100644
--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@@ -19,5 +19,14 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
+ - uses: actions/setup-python@v2
+ with:
+ python-version: '3.x' # Version range or exact version of a Python
version to use, using SemVer's version range syntax
+ architecture: 'x64' # optional x64 or x86. Defaults to x64 if not
specified
+ - name: Install dependencies
+ run: |
+ python -m pip install --upgrade pip
+ pip install yamllint
- name: 🧹 YAML Lint
- uses: ibiqlik/action-yamllint@v3
+ run: |
+ yamllint .
diff --git a/website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md
b/website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md
index b9c25c5..f6cb381 100644
--- a/website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md
+++ b/website/blog/2020-12-18-a-first-look-at-kubernetes-service-api.md
@@ -138,7 +138,7 @@ RBAC（基于角色的访问控制）是用于 Kubernetes 授权的标准。允
- Custom Route 以上扩展点都不能满足时，可以完全自定义一个 Route。
-# 总结
+## 总结
本文通过提问的方式，对 Kubernetes Service APIs 做了一些基本介绍，从整体来看，Kubernetes Service APIs
提炼了很多 ingress 的最佳实践，比如表达能力的增强，其实就是扩展了 Route 的能力，再比如 BackendPolicy 对象，可以为
upstream 指定几乎所有的 Kubernetes 后端资源。当然，项目初期也有不足的地方，目前 Kubernetes Service APIs
虽然已经从大的层面上规定了资源对象，但资源对象内部还有不少细节需要讨论之后再确定，以防止可能出现的冲突场景，结构上存在一定变数。
