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.05.11
Kubernetes 社区每周聚会笔记- 2015年5月1日
每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
简单的滚动更新 - Brendan
滚动更新 = RCs和Pods很好的例子。
…pause… (Brendan 需要 Kelsey 的演示恢复技巧)
滚动更新具有恢复功能:取消更新并重新启动，更新从停止的地方继续。
新控制器获取旧控制器的名称，因此外观是纯粹的更新。
还可以在 update 中命名版本(最后不会重命名)。
Rocket 演示 - CoreOS 的伙计们
Rocket 和 docker 之间的主要区别: Rocket 是无守护进程和以 pod 为中心。。
Rocket 具有原生的 AppContainer 格式，但也支持 docker 镜像格式。
可以在同一个 pod 中运行 AppContainer 和 docker 容器。
变更接近于合并。
演示 service accounts 和 secrets 被添加到 pod - Jordan
问题：很难获得与API通信的令牌。
新的API对象：”ServiceAccount”
ServiceAccount 是命名空间，控制器确保命名空间中至少存在一个个默认 service account。
键入 “ServiceAccountToken”，控制器确保至少有一个默认令牌。
演示
- 可以使用 ServiceAccountToken 创建新的 service account。控制器将为它创建令牌。
可以创建一个带有 service account 的 pod, pod 将在 /var/run/secrets/kubernets.io/…
Kubelet 在容器中运行 - Paul
- Kubelet 成功地运行了带有 secret 的 pod。
- Kubelet 成功地运行了带有 secret 的 pod。