jiebi/CodeConvo huggingface dataset:
Change:
<ins> --- title: 新しいコンテンツの貢献の概要 linktitle: 概要 content_type: concept main_menu: true weight: 5 --- <!-- overview --> このセクションでは、新しいコンテンツの貢献を行う前に知っておくべき情報を説明します。 <!-- body --> ## 貢献の基本 - KubernetesのドキュメントはMarkdownで書き、Kubernetesのウェブサイトは[Hugo](https://gohugo.io/)を使ってビルドします。 - ソースは[GitHub](https://github.com/kubernetes/website)にあります。Kubernetesのドキュメントは`/content/en/docs/`にあります。リファレンスドキュメントの一部は、`update-imported-docs/`ディレクトリ内のスクリプトから自動的に生成されます。 - [Page content types](/docs/contribute/style/page-content-types/)にHugoによるドキュメントのコンテンツの見え方を記述しています。 - 標準のHugoのshortcodeに加えて、多数の[カスタムのHugo shortcode](/docs/contribute/style/hugo-shortcodes/)を使用してコンテンツの見え方をコントロールしています。 - ドキュメントのソースは`/content/`内にある複数の言語で利用できます。各言語はそれぞれ[ISO 639-1標準](https://www.loc.gov/standards/iso639-2/php/code_list.php)で定義された2文字のコードの名前のフォルダを持ちます。たとえば、英語のドキュメントのソースは`/content/en/docs/`内に置かれています。 - 複数言語でのドキュメントへの貢献や新しい翻訳の開始に関する情報については、[Kubernetesのドキュメントを翻訳する](/docs/contribute/localization)を参照してください。 ## 始める前に {#before-you-begin} ### CNCF CLAに署名する {#sign-the-cla} すべてのKubernetesのコントリビューターは、[コントリビューターガイド](https://github.com/kubernetes/community/blob/master/contributors/guide/README.md)を読み、[Contributor License Agreement(コントリビューターライセンス契約、CLA)への署名](https://github.com/kubernetes/community/blob/master/CLA.md)を**必ず行わなければなりません**。 CLAへの署名が完了していないコントリビューターからのpull requestは、自動化されたテストで失敗します。名前とメールアドレスは`git config`コマンドで表示されるものに一致し、gitの名前とメールアドレスはCNCF CLAで使われたものに一致しなければなりません。 ### どのGitブランチを使用するかを選ぶ pull requestをオープンするときは、どのブランチをベースにして作業するかをあらかじめ知っておく必要があります。 シナリオ | ブランチ :---------|:------------ 現在のリリースに対する既存または新しい英語のコンテンツ | `master` 機能変更のリリースに対するコンテンツ | 機能変更が含まれるメジャーおよびマイナーバージョンに対応する、`dev-<version>`というパターンのブランチを使います。たとえば、機能変更が`v{{< skew nextMinorVersion >}}`に含まれる場合、ドキュメントの変更は``dev-{{< skew nextMinorVersion >}}``ブランチに追加します。 他の言語内のコンテンツ(翻訳) | 各翻訳対象の言語のルールに従います。詳しい情報は、[翻訳のブランチ戦略](/docs/contribute/localization/#branching-strategy)を読んでください。 それでも選ぶべきブランチがわからないときは、Slack上の`#sig-docs`チャンネルで質問してください。 {{< note >}} すでにpull requestを作成していて、ベースブランチが間違っていたことに気づいた場合は、作成者であるあなただけがベースブランチを変更できます。 {{< /note >}} ### 言語ごとのPR pull requestはPRごとに1つの言語に限定してください。複数の言語に同一の変更を行う必要がある場合は、言語ごとに別々のPRを作成してください。 ## コントリビューターのためのツール `kubernetes/website`リポジトリ内の[doc contributors tools](https://github.com/kubernetes/website/tree/master/content/en/docs/doc-contributor-tools)ディレクトリには、コントリビューターとしての旅を楽にしてくれるツールがあります。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /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
Change:
1. To change a Service from dual-stack to single-stack, change `.spec.ipFamilyPolicy` from `PreferDualStack` or `RequireDualStack` to `SingleStack`. When you change this Service from <del> dual-stack to single-stack, Kubernetes retains only the first element in the `.spec.ClusterIPs` array, and sets `.spec.ClusterIP` to that IP address and sets `.spec.ipFamilies` to the address family of `.spec.ClusterIPs`. </del> <ins> dual-stack to single-stack, Kubernetes retains only the first element in the `.spec.clusterIPs` array, and sets `.spec.clusterIP` to that IP address and sets `.spec.ipFamilies` to the address family of `.spec.clusterIPs`. </ins> ### Headless Services without selector

Discussion:
page is plenty of wrong references to the non defined ` instead.
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue 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
/kind bug
/assign
Thanks for solving this so so quick (you are the best ;-)
Change:
ユーザーはDaemonSetが作成したPodを修正可能です。しかし、Podは全てのフィールドの更新を許可していません。また、DaemonSetコントローラーは次のNode(同じ名前でも)が作成されたときにオリジナルのテンプレートを使ってPodを作成します。 <del> ユーザーはDaemonSetを削除可能です。`kubectl`コマンドで`--cascade=false`を指定するとDaemonSetのPodはNode上に残り続けます。その後、同じセレクターで新しいDaemonSetを作成すると、新しいDaemonSetは既存のPodを再利用します。PodでDaemonSetを置き換える必要がある場合は、`updateStrategy`に従ってそれらを置き換えます。 </del> <ins> ユーザーはDaemonSetを削除可能です。`kubectl`コマンドで`--cascade=orphan`を指定するとDaemonSetのPodはNode上に残り続けます。その後、同じセレクターで新しいDaemonSetを作成すると、新しいDaemonSetは既存のPodを再利用します。PodでDaemonSetを置き換える必要がある場合は、`updateStrategy`に従ってそれらを置き換えます。 </ins> ユーザーはDaemonSet上で[ローリングアップデートの実施](/docs/tasks/manage-daemon/update-daemon-set/)が可能です。

Discussion:
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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja
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
Change:
--- <del> title: "Controllers" </del> <ins> title: "Workload Resources" </ins> weight: 20 ---

Discussion:
This "Workloads" doc page just has two links to Pods and Controllers. It would be great to give an overview of the purpose of workloads (why such an architectural construct is required? and how it is used in Kubernetes). Thanks.
An introduction to the workload concepts would be really useful /kind feature /language en /priority backlog
/triage accepted
Change:
For self-registration, the kubelet is started with the following options: --> <del> ### 节点自注册 </del> <ins> ### 节点自注册 {#self-registration-of-nodes} </ins> 当 kubelet 标志 `--register-node` 为 true（默认）时，它会尝试向 API 服务注册自己。 这是首选模式，被绝大多数发行版选用。

Discussion:
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: ! URL #self-registration-of-nodes #manual-node-administration # # Proposed Solution: {#self-registration-of-nodes} {#manual-node-administration} Page to Update: <!--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
/language zh /assign
Change:
`.spec.template`は`.spec`内での必須のフィールドの1つです。 <del> `.spec.template`は[Podテンプレート](/docs/concepts/workloads/pods/#pod-templates)となります。これはフィールドがネストされていて、`apiVersion`や`kind`をもたないことを除いては、{{< glossary_tooltip text="Pod" term_id="pod" >}}のテンプレートと同じスキーマとなります。 </del> <ins> `.spec.template`は[Podテンプレート](/ja/docs/concepts/workloads/pods/#pod-template)となります。これはフィールドがネストされていて、`apiVersion`や`kind`をもたないことを除いては、{{< glossary_tooltip text="Pod" term_id="pod" >}}のテンプレートと同じスキーマとなります。 </ins> Podに対する必須のフィールドに加えて、DaemonSet内のPodテンプレートは適切なラベルを指定しなくてはなりません([Podセレクター](#pod-selector)の項目を参照ください)。

Discussion:
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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja
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
Change:
spec: containers: - name: hello-world <del> image: gcr.io/google-samples/node-hello:1.0 </del> <ins> image: us-docker.pkg.dev/google-samples/containers/gke/hello-app:2.0 </ins> ports: - containerPort: 8080 protocol: TCP

Discussion:
After running the kubectl apply command at , "kubectl get all" shows it is having "ImagePullBackOff" error When I do a describe it says the image is too old and need to be updated According to this link , the image was created back in 2016. Can we either update all the sample images to use manifest version 2 or find another image that works out of the box?
Related issue:
We shoudl fix this i think. sftim Any idea how we could resolve to help with tutorial working again?
Sample yaml reported in the issue: /language en
It seems that the image may have been removed by Google. We can either update the sample with image's new location (will need some searching), similar to what we’ve done for other tutorials (example ), or find a suitable alternative image to use.
I'd love to help out if appropriate, it appears to be a good first issue but I am not sure.
Would be good to fix this issue with the tutorial. /priority backlog /triage accepted
/kind bug
Change:
2. Modify the resulted `kubelet.conf` manually to adjust the cluster name and the server endpoint, or run `kubeadm kubeconfig user --config` (it accepts `InitConfiguration`). <del> If your cluster does not have the `ca.key` file, you must sign the embedded certificates in the `kubelet.conf` externally. </del> <ins> If your cluster does not have the `ca.key` file, you must sign the embedded certificates in the `kubelet.conf` externally. For additional information, see [PKI certificates and requirements](/docs/setup/best-practices/certificates/) and [Certificate Management with kubeadm](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#external-ca-mode). </ins> 1. Copy the resulting `kubelet.conf` to `/etc/kubernetes/kubelet.conf` on the new node. 2. Execute `kubeadm join` with the flag

Discussion:
"If your cluster does not have the file, you must sign the embedded certificates in the externally." Externally? Huh? "Copy the resulting to on the new node." Resulting from what, pray tell? What wrote this file?
Page reported in issue: /language en
/sig cluster-lifecycle
/retitle Ambiguous and unclear instructions in "kubeadm join" guide for handling missing file
this sentence can link to this page: and this section about external CA: /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : "If your cluster does not have the file, you must sign the embedded certificates in the externally." Externally? Huh? and this section about external CA: </details
you should only add “help wanted” to issues that are well defined and have been accepted. Did you want to accept this?
/triage accepted
I will try to help with this. /assign
/assign Will try to help with this too!
Hi Are you still working on this issue
Not really! Feel free to assign yourself to the issue if you're interested
/assign
Change:
abstract: "自動化されたコンテナのデプロイ・スケール・管理" cid: home --- <del> {{< announcement >}} {{< deprecationwarning >}} </del> {{< blocks/section id="oceanNodes" >}} {{% blocks/feature image="flower" %}}

Discussion:
Umbrella issue: Remove the following from L6-8:
/assign inductor
/kind cleanup
On it!
/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
Change:
Area of Concern for Workload Security | Recommendation | ------------------------------ | --------------------- | RBAC Authorization (Access to the Kubernetes API) | https://kubernetes.io/docs/reference/access-authn-authz/rbac/ <del> Authentication | https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/ </del> <ins> Authentication | https://kubernetes.io/docs/concepts/security/controlling-access/ </ins> Application secrets management (and encrypting them in etcd at rest) | https://kubernetes.io/docs/concepts/configuration/secret/ <br> https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/ Pod Security Policies | https://kubernetes.io/docs/concepts/policy/pod-security-policy/ Quality of Service (and Cluster resource management) | https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/

Discussion:
! Chinese page link can not open
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
/language zh
/assign
/kind bug
Change:
<ins> --- title: 启用/禁用 Kubernetes API content_type: task --- <!-- --- title: Enable Or Disable A Kubernetes API content_type: task --- --> <!-- overview --> <!-- This page shows how to enable or disable an API version from your cluster's {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. --> 本页展示怎么用集群的 {{< glossary_tooltip text="控制平面" term_id="control-plane" >}}. 启用/禁用 API 版本。 <!-- steps --> <!-- Specific API versions can be turned on or off by passing `--runtime-config=api/<version>` as a command line argument to the API server. The values for this argument are a comma-separated list of API versions. Later values override earlier values. The `runtime-config` command line argument also supports 2 special keys: --> 通过 API 服务器的命令行参数 `--runtime-config=api/<version>` ， 可以开启/关闭某个指定的 API 版本。 此参数的值是一个逗号分隔的 API 版本列表。 此列表中，后面的值可以覆盖前面的值。 命令行参数 `runtime-config` 支持两个特殊的值（keys）： <!-- - `api/all`, representing all known APIs - `api/legacy`, representing only legacy APIs. Legacy APIs are any APIs that have been explicitly [deprecated](/zh/docs/reference/using-api/deprecation-policy/). For example, to turning off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true` to the `kube-apiserver`. --> - `api/all`：指所有已知的 API - `api/legacy`：指过时的 API。过时的 API 就是明确地 [弃用](/zh/docs/reference/using-api/deprecation-policy/) 的 API。 例如：为了停用除去 v1 版本之外的全部其他 API 版本， 就用参数 `--runtime-config=api/all=false,api/v1=true` 启动 `kube-apiserver`。 ## {{% heading "whatsnext" %}} <!-- Read the [full documentation](/docs/reference/command-line-tools-reference/kube-apiserver/) for the `kube-apiserver` component. --> 阅读[完整的文档](/zh/docs/reference/command-line-tools-reference/kube-apiserver/), 以了解 `kube-apiserver` 组件。 </ins>  No newline at end of file

Discussion:
Translate docs/tasks/administer-cluster/enable-disable-api/ into Chinese
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
/language zh /assign
Change:
</tr> <tr> <del> <td colspan="2">--default-not-ready-toleration-seconds int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 300</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration.</p></td> </tr> <tr> <td colspan="2">--default-unreachable-toleration-seconds int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 300</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration.</p></td> </tr> <tr> </del> <td colspan="2">--detect-local-mode LocalMode</td> </tr> <tr>

Discussion:
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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
Operators are software extensions to Kubernetes that make use of [custom resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) to manage applications and their components. Operators follow <del> Kubernetes principles, notably the [control loop](/docs/concepts/#kubernetes-control-plane). </del> <ins> Kubernetes principles, notably the [control loop](/docs/concepts/architecture/controller). </ins> <!-- body -->

Discussion:
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--Hyperlinks don't work Hyperlinks to topics <bKubernetes control plane</band <bKubernetes objects</btakes to back to <bConcepts</bpage rather than respective topics. Proposed Solution: Update linkw to point to correct content. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi If related documents are not missing, then Perhaps Kubernetes control plane should point to I noticed that the corresponding file , later than the link on page . And Kubernetes objects perhaps should point to . Seems a little bit weird. These documents should be in the same hierarchy I think. Let me create a PR to solve this issue. /assign
/kind bug
I think the link for Kubernetes control-plane should be to and I agree above that the link for Kubernetes objects should be to /assign
Hi Thanks for your PR! I submitted a PR (ref: ) to fix this issue about half a month ago, and just got approved 3 days ago. Since the CLA checking was missing after I migrated to a new github account, this PR was not merged until a few minutes ago after I let the robot recheck my CLA.
Change:
</tr> <tr> <ins> <td colspan="2">--vmodule &lt;comma-separated 'pattern=N' settings&gt;</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>comma-separated list of pattern=N settings for file-filtered logging</p></td> </tr> <tr> </ins> <td colspan="2">--write-config-to string</td> </tr> <tr>

Discussion:
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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
{{< codenew file="admin/dns/dnsutils.yaml" >}} <ins> {{< note >}} This example creates a pod in the `default` namespace. DNS name resolution for services depends on the namespace of the pod. For more information, review [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/#what-things-get-dns-names). {{< /note >}} </ins> Use that manifest to create a Pod: ```shell

Discussion:
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 guidance on DNS resolution for services between namespaces is confusing users. Proposed Solution: add additional info on the troubleshooting pages, add a table to the services concept page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted /kind cleanup
/sig network