jiebi/CodeConvo huggingface dataset:
Code change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update tasks/tools/install- to follow v1.17 of the original (Englist) text. Why is this needed content/ja/docs/tasks/tools/install- is outdated. Comments /language ja /good-first-issue File to update Original https://v1- diff between translated and v1.17 Note Currently, we use branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update tasks/tools/install- to follow v1.17 of the original (Englist) text. content/ja/docs/tasks/tools/install- is outdated. /language ja /good-first-issue Currently, we use branch. Please open a PR targeting the branch. 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
/assign
/close
Closing this issue. <detailsIn response to : /close 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

Related discussion:
text: {{% /capture %}} <ins> ## インストールの確認 ハイパーバイザーとMinikube両方のインストール成功を確認するため、以下のコマンドをローカルKubernetesクラスターを起動するために実行してください: {{< note >}} `minikube start`で`--vm-driver`の設定をするため、次の`<driver_name>`の部分では、インストールしたハイパーバイザーの名前を小文字で入力してください。`--vm-driver`値のすべてのリストは、[specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver)で確認できます。 {{< /note >}} ```shell minikube start --vm-driver=<driver_name> ``` `minikube start`が完了した場合、次のコマンドを実行してクラスターの状態を確認します。 ```shell minikube status ``` クラスターが起動していると、`minikube status`の出力はこのようになります。 ``` host: Running kubelet: Running apiserver: Running kubeconfig: Configured ``` 選択したハイパーバイザーでMinikubeが動作しているか確認した後は、そのままMinikubeを使い続けることもできます。また、クラスターを停止することもできます。クラスターを停止するためには、次を実行してください。 ```shell minikube stop ``` </ins> ## ローカル状態のクリーンアップ {#cleanup-local-state} もし以前に　Minikubeをインストールしていたら、以下のコマンドを実行します。
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: section () contains an outdated claim ( in 2016 in commit ) that compromise of a node/kubelet gives an attacker access to all secrets in the cluster. Specifically: My understanding is that modern clusters by default are configured to provide node/kubelet access only to secrets for Pods scheduled on that node/kubelet. . Tested on Amazon EKS 1.15. Proposed Solution: Edit to either entirely remove the above quote, or, if the security improvement is not enabled by default, provide information about how to enable it. Page to Update:
/kind bug /priority important-longterm Working on this also addresses from the style guide.
/language en
Thanks for reporting this
The outdated statement appears to be there in as well. I suspect it might be there in more languages.
That's OK - the localization teams have their own processes for picking up changes that are fixed in the upstream English localization.
/assign
I notice also that says: (my emphasis)
/sig auth
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
Anyone who'd like to, please feel free to open a pull request with an update.
/kind documentation
/sig security
/triage accepted

Related discussion:
text: - A user who can create a Pod that uses a secret can also see the value of that secret. Even if the API server policy does not allow that user to read the Secret, the user could run a Pod which exposes the secret. <del> - Currently, anyone with root permission on any node can read _any_ secret from the API server, by impersonating the kubelet. It is a planned feature to only send secrets to nodes that actually require them, to restrict the impact of a root exploit on a single node. </del> ## {{% heading "whatsnext" %}}
Code change:
This is a Feature Request What would you like to be Translate docs/reference/glossary/secret into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign

Related discussion:
text: <ins> --- title: Secret id: secret date: 2018-04-12 full_link: /ja/docs/concepts/configuration/secret/ short_description: > パスワードやOAuthトークン、SSHキーのような機密の情報を保持します。 aka: tags: - core-object - security --- パスワードやOAuthトークン、SSHキーのような機密の情報を保持します。 <!--more--> 機密情報の取り扱い方法を細かく制御することができ、保存時には[暗号化](/ja/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)するなど、誤って公開してしまうリスクを減らすことができます。{{< glossary_tooltip text="Pod" term_id="pod" >}}は、ボリュームマウントされたファイルとして、またはPodのイメージをPullするkubeletによって、Secretを参照します。Secretは機密情報を扱うのに最適で、機密でない情報には[ConfigMap](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)が適しています。 </ins>
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The example used to verify the relationship between the version of kube-proxy and kube-apiserver is problematic Proposed Solution: The version of kube-proxy must be less than or euqual to the version of kube-apiserver, so if the version of kube-proxy is 1.18, the version of kube-apiserver can be 1.18, 1.19 and 1.20. The setence should be "kube-apiserver version must be between 1.18 and 1.20, inclusive". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind bug /language en
thanks for finding this problem. PRs welcome! /help /good-first-issue /sig docs architecture /priority important-longterm
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : thanks for finding this problem. PRs welcome! /good-first-issue /sig docs architecture /priority important-longterm </details
/assign

Related discussion:
text: Example: <del> If `kube-proxy` version is **{{< skew latestVersion >}}**: </del> <ins> If `kube-proxy` version is **{{< skew oldestMinorVersion >}}**: </ins> <del> * `kubelet` version must be at the same minor version as **{{< skew latestVersion >}}**. </del> <ins> * `kubelet` version must be at the same minor version as **{{< skew oldestMinorVersion >}}**. </ins> * `kube-apiserver` version must be between **{{< skew oldestMinorVersion >}}** and **{{< skew latestVersion >}}**, inclusive.
Code change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I'd like to sort "", common words alphabetically in Japanese localization guide. Why is this needed It'll be easier to find a word in the list. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign

Related discussion:
text: 英語 | 日本語 --------- | --------- <del> cluster|クラスター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ </del> Addon/Add-on|アドオン <del> Quota|クォータ For more information|さらなる情報(一時的) prefix | プレフィックス container | コンテナ directory | ディレクトリ </del> <ins> Aggregation Layer | アグリゲーションレイヤー architecture | アーキテクチャ </ins> binary | バイナリ <ins> cluster|クラスター community | コミュニティ container | コンテナ </ins> controller | コントローラー <del> operator | オペレーター Aggregation Layer | アグリゲーションレイヤー </del> <ins> Deployment/Deploy|KubernetesリソースとしてのDeploymentはママ表記、一般的な用語としてのdeployの場合は、デプロイ directory | ディレクトリ For more information|さらなる情報(一時的) GitHub | GitHub (ママ表記) </ins> Issue | Issue (ママ表記) <ins> operator | オペレーター orchestrate(動詞)|オーケストレーションする Persistent Volume|KubernetesリソースとしてのPersistentVolumeはママ表記、一般的な用語としての場合は、永続ボリューム prefix | プレフィックス </ins> Pull Request | Pull Request (ママ表記) <del> GitHub | GitHub (ママ表記) </del> <ins> Quota|クォータ </ins> registry | レジストリ <del> architecture | アーキテクチャ </del> secure | セキュア <del> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </del> a set of ~ | ～の集合 <del> community | コミュニティ </del> <ins> stacked | 積層(例: stacked etcd clusterは積層etcdクラスター) </ins> ### 備考
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Mismatch between descriptive node names ! Proposed Solution: Change node name from 'noee2' to 'node2' Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ko /assign

Related discussion:
text: * 클라이언트는 `node2:nodePort`로 패킷을 보낸다. * `node2`는 소스 IP 주소(SNAT)를 패킷 상에서 자신의 IP 주소로 교체한다. <del> * `noee2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </del> <ins> * `node2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </ins> * 패킷은 node 1로 라우팅 된 다음 엔드포인트로 라우팅 된다. * 파드의 응답은 node2로 다시 라우팅된다. * 파드의 응답은 클라이언트로 다시 전송된다.
Code change:
At the bottom of the page, in the section, the following links lead to a 404 page not found: RuntimeClass Design, link RuntimeClass Scheduling Design, link

Related discussion:
text: ## {{% heading "whatsnext" %}} <del> - [RuntimeClass Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/runtime-class.md) - [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/runtime-class-scheduling.md) </del> <ins> - [RuntimeClass Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md) - [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md#runtimeclass-scheduling) </ins> - Read about the [Pod Overhead](/docs/concepts/configuration/pod-overhead/) concept - [PodOverhead Feature Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md)
Code change:
Clicking the "Containers" hyperlink leads to the "What is Kubernetes?" page. I'm not sure if this was intended. There is some explanation of containerized deployments (after a scroll) but I wonder if it makes more sense to direct them to the "Containers" term page. As a user learning in the docs, it was a bit confusing. Pods hyperlink re-direction shown below, from this <img width="901" alt="Screen Shot 2020-10-09 at 1 58 28 PM" src="https://user-"Leads to the below <img width="843" alt="Screen Shot 2020-10-09 at 1 58 54 PM" src="https://user-"Perhaps redirecting to the page defining containers in the concepts may be better, though I believe more definition could be there.
/triage accepted
/kind bug /language en /priority backlog /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind bug /language en /priority backlog /help 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
Hi I'd like to work on this
Awesome! I think you can assign it yourself by running the "assign" command. Context here: and example here:
/assign

Related discussion:
text: _Pods_ are the smallest deployable units of computing that you can create and manage in Kubernetes. A _Pod_ (as in a pod of whales or pea pod) is a group of one or more <del> {{< glossary_tooltip text="containers" term_id="container" >}}, with shared storage/network resources, and a specification </del> <ins> [containers](/docs/concepts/containers/), with shared storage/network resources, and a specification </ins> for how to run the containers. A Pod's contents are always co-located and co-scheduled, and run in a shared context. A Pod models an application-specific "logical host": it contains one or more application
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Clicking the "" hyperlink leads to the 404 page. <img width="876" alt="WeChatc2b6a16c89afc8d1086c8c92a0a7f437" src="https://user-"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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
/assign
/language zh

Related discussion:
text: title: 容器运行环境（Container Runtime） id: container-runtime date: 2019-06-05 <del> full_link: /docs/reference/generated/container-runtime </del> <ins> full_link: /docs/setup/production-environment/container-runtimes </ins> short_description: > 容器运行环境是负责运行容器的软件。
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Clicking the "" hyperlink leads to the 404 page. <img width="876" alt="WeChatc2b6a16c89afc8d1086c8c92a0a7f437" src="https://user-"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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
/assign
/language zh

Related discussion:
text: title: Container Runtime id: container-runtime date: 2019-06-05 <del> full_link: /docs/reference/generated/container-runtime </del> <ins> full_link: /docs/setup/production-environment/container-runtimes </ins> short_description: > The container runtime is the software that is responsible for running containers.
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Clicking the "" hyperlink leads to the 404 page. <img width="876" alt="WeChatc2b6a16c89afc8d1086c8c92a0a7f437" src="https://user-"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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
/assign
/language zh

Related discussion:
text: <!--more--> <!-- <del> Kubernetes supports several container runtimes: [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) and any implementation of the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md). </del> <ins> Kubernetes supports several container runtimes: {{< glossary_tooltip term_id="docker">}}, {{< glossary_tooltip term_id="containerd" >}}, {{< glossary_tooltip term_id="cri-o" >}}, and any implementation of the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md). </ins> --> <del> Kubernetes 支持多个容器运行环境: [Docker](http://www.docker.com)、 [containerd](https://containerd.io)、[cri-o](https://cri-o.io/)、 [rktlet](https://github.com/kubernetes-incubator/rktlet) 以及任何实现 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)。 </del> <ins> Kubernetes 支持多个容器运行环境: {{< glossary_tooltip term_id="docker">}}、 {{< glossary_tooltip term_id="containerd" >}}、{{< glossary_tooltip term_id="cri-o" >}} 以及任何实现 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)。 </ins>
Code change:
This is a Bug Report Problem: is mis-configured for markdown files, and is stripping white space at the end of lines. Markdown uses these spaces for formatting in some casees. Currently, if the .editorconfig file is being used (via plugin or whatnot), then these formatting cues can be removed on save. Proposed Solution: add the following after the section in the file. dotfile to Update: .editorconfig Test environment MacOS 10.14.6 Both of: VS Code using neovim using
Good spot /kind bug /triage accepted /priority backlog
/assign

Related discussion:
text: max_line_length = 80 trim_trailing_whitespace = true <ins> [*.md] trim_trailing_whitespace = false </ins> [*.{css,html,js,json,sass,md,mmark,toml,yaml}] indent_style = space indent_size = 2
Code change:
Translate tutorials/configuration/configure-java-microservice/ into Chinese /language zh /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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

Related discussion:
text: <ins> --- title: "示例：配置 java 微服务" weight: 10 --- <!-- --- title: "Example: Configuring a Java Microservice" weight: 10 --- --> </ins>  No newline at end of file
Code change:
Translate tutorials/configuration/configure-java-microservice/ into Chinese /language zh /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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

Related discussion:
text: <ins> --- title: "互动教程 - 配置 java 微服务" weight: 20 --- <!-- --- title: "Interactive Tutorial - Configuring a Java Microservice" weight: 20 --- --> <!DOCTYPE html> <html lang="en"> <body> <link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet"> <link href="/docs/tutorials/kubernetes-basics/public/css/overrides.css" rel="stylesheet"> <script src="https://katacoda.com/embed.js"></script> <div class="layout" id="top"> <main class="content katacoda-content"> <div class="katacoda"> <div class="katacoda__alert"> <!-- To interact with the Terminal, please use the desktop/tablet version --> 如需要与终端交互，请使用台式机/平板电脑版 </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/9" data-katacoda-color="326de6" data-katacoda-secondary="273d6d" data-katacoda-hideintro="false" data-katacoda-prompt="Kubernetes Bootcamp Terminal" style="height: 600px;"></div> </div> </main> </div> </body> </html> </ins>