Localizing Kubernetes documentation
This page shows you how to localize the docs for a different language.
Because contributors can't approve their own pull requests, you need at least two contributors to begin a localization.
All localization teams must be self-sustaining with their own resources. The Kubernetes website is happy to host your work, but it's up to you to translate it.
Find your two-letter language code
First, consult the ISO 639-1 standard to find your localization's two-letter country code. For example, the two-letter code for Korean is
Fork and clone the repo
Then, clone your fork and
cd into it:
git clone https://github.com/<username>/website cd website
Open a pull request
Next, open a pull request (PR) to add a localization to the
The PR must include all of the minimum required content before it can be approved.
For an example of adding a new localization, see the PR to enable docs in French.
Join the Kubernetes GitHub organization
Once you've opened a localization PR, you can become members of the Kubernetes GitHub organization. Each person on the team needs to create their own Organization Membership Request in the
Add your localization team in GitHub
@kubernetes/sig-docs-**-owners can approve PRs that change content within (and only within) your localization directory:
For each localization, The
@kubernetes/sig-docs-**-reviews team automates review assignment for new PRs.
@kubernetes/website-maintainers can create new localization branches to coordinate translation efforts.
@kubernetes/website-milestone-maintainers can use the
/milestone Prow command to assign a milestone to issues or PRs.
Configure the workflow
Next, add a GitHub label for your localization in the
kubernetes/test-infra repository. A label lets you filter issues and pull requests for your specific language.
For an example of adding a label, see the PR for adding the Italian language label.
Let Kubernetes SIG Docs know you're interested in creating a localization! Join the SIG Docs Slack channel and the SIG Docs Localizations Slack channel. Other localization teams are happy to help you get started and answer any questions you have.
Please also consider participating in the SIG Docs Localization Subgroup meeting. The mission of the SIG Docs localization subgroup is to work across the SIG Docs localization teams to collaborate on defining and documenting the processes for creating localized contribution guides. In addition, the SIG Docs localization subgroup will look for opportunities for the creation and sharing of common tools across localization teams and also serve to identify new requirements to the SIG Docs Leadership team. If you have questions about this meeting, please inquire on the SIG Docs Localizations Slack channel.
You can also create a Slack channel for your localization in the
kubernetes/community repository. For an example of adding a Slack channel, see the PR for adding a channel for Persian.
Minimum required content
Modify the site configuration
The Kubernetes website uses Hugo as its web framework. The website's Hugo configuration resides in the
config.toml file. To support a new localization, you'll need to modify
Add a configuration block for the new language to
config.toml, under the existing
[languages] block. The German block, for example, looks like:
[languages.de] title = "Kubernetes" description = "Produktionsreife Container-Verwaltung" languageName = "Deutsch" contentDir = "content/de" weight = 3
When assigning a
weight parameter for your block, find the language block with the highest weight and add 1 to that value.
For more information about Hugo's multilingual support, see "Multilingual Mode".
Add a new localization directory
Add a language-specific subdirectory to the
content folder in the repository. For example, the two-letter code for German is
Localize the community code of conduct
Open a PR against the
cncf/foundation repository to add the code of conduct in your language.
Add a localized README file
To guide other localization contributors, add a new
README-**.md to the top level of k/website, where
** is the two-letter language code. For example, a German README file would be
Provide guidance to localization contributors in the localized
README-**.md file. Include the same information contained in
README.md as well as:
- A point of contact for the localization project
- Any information specific to the localization
After you create the localized README, add a link to the file from the main English
README.md, and include contact information in English. You can provide a GitHub ID, email address, Slack channel, or other method of contact. You must also provide a link to your localized Community Code of Conduct.
Setting up the OWNERS files
To set the roles of each user contributing to the localization, create an
OWNERS file inside the language-specific subdirectory with:
- reviewers: A list of kubernetes teams with reviewer roles, in this case, the
sig-docs-**-reviewsteam created in Add your localization team in GitHub.
- approvers: A list of kubernetes teams with approvers roles, in this case, the
sig-docs-**-ownersteam created in Add your localization team in GitHub.
- labels: A list of GitHub labels to automatically apply to a PR, in this case, the language label created in Configure the workflow.
More information about the
OWNERS file can be found at go.k8s.io/owners.
The Spanish OWNERS file, with language code
es, looks like:
# See the OWNERS docs at https://go.k8s.io/owners # This is the localization project for Spanish. # Teams and members are visible at https://github.com/orgs/kubernetes/teams. reviewers: - sig-docs-es-reviews approvers: - sig-docs-es-owners labels: - language/es
After adding the language-specific
OWNERS file, update the root
OWNERS_ALIASES file with the new Kubernetes teams for the localization,
For each team, add the list of GitHub users requested in Add your localization team in GitHub, in alphabetical order.
--- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -48,6 +48,14 @@ aliases: - stewart-yu - xiangpengzhao - zhangxiaoyu-zidif + sig-docs-es-owners: # Admins for Spanish content + - alexbrand + - raelga + sig-docs-es-reviews: # PR reviews for Spanish content + - alexbrand + - electrocucaracha + - glo-pena + - raelga sig-docs-fr-owners: # Admins for French content - perriea - remyleone
Localizing all of the Kubernetes documentation is an enormous task. It's okay to start small and expand over time.
At a minimum, all localizations must include:
|Home||All heading and subheading URLs|
|Setup||All heading and subheading URLs|
|Tutorials||Kubernetes Basics, Hello Minikube|
|Site strings||All site strings in a new localized TOML file|
Translated documents must reside in their own
content/**/ subdirectory, but otherwise follow the same URL path as the English source. For example, to prepare the Kubernetes Basics tutorial for translation into German, create a subfolder under the
content/de/ folder and copy the English source:
mkdir -p content/de/docs/tutorials cp content/en/docs/tutorials/kubernetes-basics.md content/de/docs/tutorials/kubernetes-basics.md
Translation tools can speed up the translation process. For example, some editors offers plugins to quickly translate text.
Caution: Machine-generated translation is insufficient on its own. Localization requires extensive human review to meet minimum standards of quality.
To ensure accuracy in grammar and meaning, members of your localization team should carefully review all machine-generated translations before publishing.
Localizations must be based on the English files from a specific release targeted by the localization team. Each localization team can decide which release to target which is referred to as the target version below.
To find source files for your target version:
- Navigate to the Kubernetes website repository at https://github.com/kubernetes/website.
- Select a branch for your target version from the following table:
Target version Branch Next version
master branch holds content for the current release
v1.20. The release team will create
release-1.20 branch shortly before the next release: v1.21.
Site strings in i18n
Localizations must include the contents of
i18n/en.toml in a new language-specific file. Using German as an example:
Add a new localization file to
i18n/. For example, with German (
cp i18n/en.toml i18n/de.toml
Then translate the value of each string:
[docs_label_i_am] other = "ICH BIN..."
Localizing site strings lets you customize site-wide text and features: for example, the legal copyright text in the footer on each page.
Language specific style guide and glossary
Some language teams have their own language-specific style guide and glossary. For example, see the Korean Localization Guide.
Because localization projects are highly collaborative efforts, we encourage teams to work in shared localization branches.
To collaborate on a localization branch:
We recommend the following branch naming scheme:
dev-<source version>-<language code>.<team milestone>
For example, an approver on a German localization team opens the localization branch
dev-1.12-de.1directly against the k/website repository, based on the source branch for Kubernetes v1.12.
Individual contributors open feature branches based on the localization branch.
For example, a German contributor opens a pull request with changes to
Approvers review and merge feature branches into the localization branch.
Periodically, an approver merges the localization branch to its source branch by opening and approving a new pull request. Be sure to squash the commits before approving the pull request.
Repeat steps 1-4 as needed until the localization is complete. For example, subsequent German localization branches would be:
Teams must merge localized content into the same branch from which the content was sourced.
- a localization branch sourced from
mastermust be merged into
- a localization branch sourced from
release-1.19must be merged into
Note: If your localization branch was created from
masterbranch but it is not merged into
masterbefore new release branch
release-1.20created, merge it into both
masterand new release branch
release-1.20. To merge your localization branch into new release branch
release-1.20, you need to switch upstream branch of your localization branch to
At the beginning of every team milestone, it's helpful to open an issue comparing upstream changes between the previous localization branch and the current localization branch. There are two scripts for comparing upstream changes.
upstream_changes.py is useful for checking the changes made to a specific file. And
diff_l10n_branches.py is useful for creating a list of outdated files for a specific localization branch.
While only approvers can open a new localization branch and merge pull requests, anyone can open a pull request for a new localization branch. No special permissions are required.
For more information about working from forks or directly from the repository, see "fork and clone the repo".
SIG Docs welcomes upstream contributions and corrections to the English source.
Help an existing localization
You can also help add or improve content to an existing localization. Join the Slack channel for the localization, and start opening PRs to help. Please limit pull requests to a single localization since pull requests that change content in multiple localizations could be difficult to review.
Once a localization meets requirements for workflow and minimum output, SIG docs will:
- Enable language selection on the website
- Publicize the localization's availability through Cloud Native Computing Foundation (CNCF) channels, including the Kubernetes blog.