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.17
Kubernetes 社区每周聚会笔记- 2015年4月17日
每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
议程
- Mesos 集成
- 高可用性（HA）
- 向 e2e 添加性能和分析详细信息以跟踪回归
- 客户端版本化
笔记
Mesos 集成
Mesos 集成提案：
没有阻塞集成的因素。
文档需要更新。
HA
提案今天应该会提交。
Etcd 集群。
apiserver 负载均衡。
控制器管理器和其他主组件的冷备用。
向 e2e 添加性能和分析详细信息以跟踪回归
希望红色为性能回归
需要公共数据库才能发布数据
- 查看
Justin 致力于多平台 e2e 仪表盘
客户端版本化
*
*
客户端库当前使用内部 API 对象。
尽管没有人反映频繁修改
types.go有多痛苦，但我们很为此担心。结构化类型在客户端中很有用。版本化的结构就可以了。
如果从 json/yaml (kubectl) 开始，则不应转换为结构化类型。使用 swagger。
Security context
*
管理员可以限制谁可以运行特权容器或需要特定的 unix uid
kubelet 将能够从 apiserver 获取证书
政策提案将于下周左右出台
- 讨论用户的上游，等等进入Kubernetes，至少是可选的
1.0 路线图
重点是性能，稳定性，集群升级
TJ 一直在对roadmap.md进行一些编辑，但尚未发布PR
Kubernetes UI
依赖关系分解为第三方
@lavalamp 是评论家