Change:
Per today's SIG-Docs meeting, we want to localize the contributor cheatsheet. The actual content in the below link: The translated content would be put into repo as well.
/kind feature
+1
Per-language task issues were created: Chinese: Korean: Japanese: German: Spanish: French: Indonesian: Portuguese: Italian: Hindi: /cc
/cc
Wonderful, thank you so much! o/
+1
+1
How is localization managed inside the community repository? It is not a hugo website so I am not sure about how the different languages are managed there.
For this specifically it would probably be best to mimic the format used in the root of the website repo. Within the contributor-cheatsheet directory add a . We can then update the welcome message bot to include links to the translated copies
Thanks for opening this. For English, I'd like this issue to include adding a section to , below Ways to Contribute: Other localizations can include that section with a link to their localization-specific cheatsheet.
I see your point, I will file a PR now.
Taking the lead for the French translation
Translation of the localize contributor cheatsheet in Korean is done. (ref : kubernetes/community)
I'm working on Ukrainian uk localization.
/reopen accidentally closed by
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
checkin /remove-lifecycle stale
Current state as of 15th Aug 2019(Feel free to edit when it has to be changed) [x] Chinese: [x] Korean: [x] Japanese: [x] German: [x] Spanish: [x] French: [x] Indonesian: [x] Portuguese: [x] Italian: [x] Hindi:
/lifecycle frozen /priority backlog
any progress so far? Would be glad to join forces)
Can we start an Oriya [or] localization? I would love to take lead in doing this. Let me know your thoughts about it.
All ten tasks are completed and merged. Closing this epic. Feel free to file a new issue/epic if there are other localization efforts to be covered. /close
Closing this issue. <detailsIn response to : All ten tasks are completed and merged. Closing this epic. Feel free to file a new issue/epic if there are other localization efforts to be covered. /close </details

Discussion:
{% capture overview %} ## Overview <del> Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally a Kubernetes developer can spawn all the instances locally and test code as they commit. This page will show you how to deploy a cluster on a local machine. </del> <ins> Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally, a Kubernetes developer can spawn all necessary nodes inside local containers and test new configurations as they are committed. This page will show you how to deploy a cluster to LXD containers on a local machine. </ins> {% endcapture %} <del> The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. </del> <ins> The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](https://kubernetes.io/docs/tutorials/kubernetes-basics/cluster-intro/) for more info). </ins> {% capture prerequisites %} ## Prerequisites