Thursday, November 08, 2018
Kubernetes Docs Updates, International Edition
Author: Zach Corleissen (Linux Foundation)
As a co-chair of SIG Docs, I’m excited to share that Kubernetes docs have a fully mature workflow for localization (l10n).
Abbreviations galore
L10n is an abbreviation for localization.
I18n is an abbreviation for internationalization.
I18n is what you do to make l10n easier. L10n is a fuller, more comprehensive process than translation (t9n).
Why localization matters
The goal of SIG Docs is to make Kubernetes easier to use for as many people as possible.
One year ago, we looked at whether it was possible to host the output of a Chinese team working independently to translate the Kubernetes docs. After many conversations (including experts on OpenStack l10n), much transformation, and renewed commitment to easier localization, we realized that open source documentation is, like open source software, an ongoing exercise at the edges of what’s possible.
Consolidating workflows, language labels, and team-level ownership may seem like simple improvements, but these features make l10n scalable for increasing numbers of l10n teams. While SIG Docs continues to iterate improvements, we’ve paid off a significant amount of technical debt and streamlined l10n in a single workflow. That’s great for the future as well as the present.
Consolidated workflow
Localization is now consolidated in the kubernetes/website repository. We’ve configured the Kubernetes CI/CD system, Prow, to handle automatic language label assignment as well as team-level PR review and approval.
Language labels
Prow automatically applies language labels based on file path. Thanks to SIG Docs contributor June Yi, folks can also manually assign language labels in pull request (PR) comments. For example, when left as a comment on an issue or PR, this command assigns the label language/ko (Korean).
/language ko
These repo labels let reviewers filter for PRs and issues by language. For example, you can now filter the k/website dashboard for PRs with Chinese content.
Team review
L10n teams can now review and approve their own PRs. For example, review and approval permissions for English are assigned in an OWNERS file in the top subfolder for English content.
Adding OWNERS files to subdirectories lets localization teams review and approve changes without requiring a rubber stamp approval from reviewers who may lack fluency.
What’s next
We’re looking forward to the doc sprint in Shanghai to serve as a resource for the Chinese l10n team.
We’re excited to continue supporting the Japanese and Korean l10n teams, who are making excellent progress.
If you’re interested in localizing Kubernetes for your own language or region, check out our guide to localizing Kubernetes docs and reach out to a SIG Docs chair for support.
Get involved with SIG Docs
If you’re interested in Kubernetes documentation, come to a SIG Docs weekly meeting, or join #sig-docs in Kubernetes Slack.
2015.04.16
Kubernetes Release: 0.15.0
Release 说明：
- 启用 1beta3 API 并将其设置为默认 API 版本 (#6098)
- 增加了多端口服务(#6182)
- 添加了一个控制器框架 (#5270, #5473)
- Kubelet 现在监听一个安全的 HTTPS 端口 (#6380)
- 使 kubectl 错误更加友好 (#6338)
- apiserver 现在支持客户端 cert 身份验证 (#6190)
- apiserver 现在限制了它处理的并发请求的数量 (#6207)
- 添加速度限制删除 pod (#6355)
- 将平衡资源分配算法作为优先级函数实现在调度程序包中 (#6150)
- 从主服务器启用日志收集功能 (#6396)
- 添加了一个 api 端口来从 Pod 中提取日志 (#6497)
- 为调度程序添加了延迟指标 (#6368)
- 为 REST 客户端添加了延迟指标 (#6409)
- etcd 现在在 master 上的一个 pod 中运行 (#6221)
- nginx 现在在 master上的容器中运行 (#6334)
- 开始为主组件构建 Docker 镜像 (#6326)
- 更新了 GCE 程序以使用 gcloud 0.9.54 (#6270)
- 更新了 AWS 程序来修复区域与区域语义 (#6011)
- 记录镜像 GC 失败时的事件 (#6091)
- 为 kubernetes 客户端添加 QPS 限制器 (#6203)
- 减少运行 make release 所需的时间 (#6196)
- 新卷的支持
- 更新到 heapster 版本到 v0.10.0 (#6331)
- 更新到 etcd 2.0.9 (#6544)
- 更新到 Kibana 到 v1.2 (#6426)
- 漏洞修复
要下载，请访问 https://github.com/GoogleCloudPlatform/kubernetes/releases/tag/v0.15.0