jiebi/CodeConvo huggingface dataset:
Change:
cd easy-rsa-master/easyrsa3 ./easyrsa init-pki <del> <!-- 1.  Generate a new certificate authority (CA). `--batch` sets automatic mode; `--req-cn` specifies the Common Name (CN) for the CA's new root certificate. --> 1.  生成新的证书颁发机构（CA）。参数 `--batch` 用于设置自动模式； </del> <ins> <!-- 2.  Generate a new certificate authority (CA). `--batch` sets automatic mode; `--req-cn` specifies the Common Name (CN) for the CA's new root certificate. --> 2.  生成新的证书颁发机构（CA）。参数 `--batch` 用于设置自动模式； </ins> 参数 `--req-cn` 用于设置新的根证书的通用名称（CN）。 ./easyrsa --batch "--req-cn=${MASTER_IP}@`date +%s`" build-ca nopass <del> <!-- 1.  Generate server certificate and key. The argument `--subject-alt-name` sets the possible IPs and DNS names the API server will be accessed with. The `MASTER_CLUSTER_IP` is usually the first IP from the service CIDR that is specified as the `--service-cluster-ip-range` argument for both the API server and the controller manager component. The argument `--days` is used to set the number of days after which the certificate expires. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 1.  生成服务器证书和秘钥。 </del> <ins> <!-- 3.  Generate server certificate and key. The argument `--subject-alt-name` sets the possible IPs and DNS names the API server will be accessed with. The `MASTER_CLUSTER_IP` is usually the first IP from the service CIDR that is specified as the `--service-cluster-ip-range` argument for both the API server and the controller manager component. The argument `--days` is used to set the number of days after which the certificate expires. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 3.  生成服务器证书和秘钥。 </ins> 参数 `--subject-alt-name` 设置 API 服务器的 IP 和 DNS 名称。 `MASTER_CLUSTER_IP` 用于 API 服务器和控制管理器，通常取 CIDR 的第一个 IP，由 `--service-cluster-ip-range` 的参数提供。 参数 `--days` 用于设置证书的过期时间。

Discussion:
Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.
Change:
* Make sure control plane components logs no TLS errors. {{< note >}} <del> To generate certificates and private keys for your cluster using the `openssl` command line tool, see [Certificates (`openssl`)](/docs/concepts/cluster-administration/certificates/#openssl). You can also use [`cfssl`](/docs/concepts/cluster-administration/certificates/#cfssl). </del> <ins> To generate certificates and private keys for your cluster using the `openssl` command line tool, see [Certificates (`openssl`)](/docs/tasks/administer-cluster/certificates/#openssl). You can also use [`cfssl`](/docs/tasks/administer-cluster/certificates/#cfssl). </ins> {{< /note >}} 1. Annotate any Daemonsets and Deployments to trigger pod replacement in a safer rolling fashion.

Discussion:
This is a clean up 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. --Why is this needed is a task page. A better home for it would be within Comments Be sure to add Netlify redirects (see ) from the old to the new page. /language en /kind cleanup
/assign
From (I agree)
/sig auth
/triage accepted
I left notes (PR ) about how to create a new task page from the page. Does this sound like a good approach?
Change:
<ins> --- title: Downward API id: downward-api date: 2022-03-21 short_description: > 将 Pod 和容器字段值暴露给容器中运行的代码的机制。 aka: full_link: /docs/concepts/workloads/pods/downward-api/ tags: - architecture --- <!-- title: Downward API id: downward-api date: 2022-03-21 short_description: > A mechanism to expose Pod and container field values to code running in a container. aka: full_link: /docs/concepts/workloads/pods/downward-api/ tags: - architecture --> <!-- Kubernetes' mechanism to expose Pod and container field values to code running in a container. --> Kubernetes 将 Pod 和容器字段值暴露给容器中运行的代码的机制。 <!--more--> <!-- It is sometimes useful for a container to have information about itself, without needing to make changes to the container code that directly couple it to Kubernetes. --> 在不需要修改容器代码的前提下让容器拥有关于自身的信息是很有用的。修改代码可能使容器直接耦合到 Kubernetes。 <!-- The Kubernetes downward API allows containers to consume information about themselves or their context in a Kubernetes cluster. Applications in containers can have access to that information, without the application needing to act as a client of the Kubernetes API. --> Kubernetes Downward API 允许容器使用它们自己或它们在 Kubernetes 集群中所处环境的信息。 容器中的应用程序可以访问该信息，而不需要以 Kubernetes API 客户端的形式执行操作。 <!-- There are two ways to expose Pod and container fields to a running container: - using [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) - using [a `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) Together, these two ways of exposing Pod and container fields are called the _downward API_. --> 有两种方法可以将 Pod 和容器字段暴露给正在运行的容器： * 使用[环境变量](/zh-cn/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) * 使用 [`downwardAPI` 卷](/zh-cn/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) 这两种暴露 Pod 和容器字段的方式统称为 **Downward API**。 </ins>  No newline at end of file

Discussion:
The commit introduced a new page which is missing in the localization: Need help to translate it. /language zh /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 : The commit introduced a new page which is missing in the localization: /help </details
/triage accepted
I want to translate this document. Can you assign it to me
/assign
Change:
{{ range . }} {{ with (where $.section.Translations ".Lang" . ) -}} {{ $p := index . 0 -}} <del> {{ $pages =  $pages | lang.Merge (union $p.Pages $p.Sections) -}} </del> <ins> {{ $pages = where ( $pages | lang.Merge (union $p.Pages $p.Sections)) ".Params.toc_hide" "!=" true -}} </ins> {{ end -}} {{ end -}} {{ end -}}

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: Except for the [EN] version, the unnecessary 'Tools Include' item is displayed in translated versions. Check the left side navigation menu in , However, the translated versions(, , , , , , ) have 'Tools Included' item. Why 'Tools Included' item is shown only in translated versions? This item is an intended headless page(, ) and should not be rendered. Proposed Solution: The item should not appear in translated versions. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/triage accepted
/assign
Change:
ノードが到達不能(例えば、ノードがダウンしているなどので理由で、ノードコントローラーがハートビートの受信を停止した場合)になると、ノードコントローラーは、NodeStatusのNodeReady conditionをConditionUnknownに変更する役割があります。その後も該当ノードが到達不能のままであった場合、Graceful Terminationを使って全てのPodを退役させます。デフォルトのタイムアウトは、ConditionUnknownの報告を開始するまで40秒、その後Podの追い出しを開始するまで5分に設定されています。 ノードコントローラーは、`--node-monitor-period`に設定された秒数ごとに各ノードの状態をチェックします。 <del> #### ハートビート ハートビートは、Kubernetesノードから送信され、ノードが利用可能か判断するのに役立ちます。 ２つのハートビートがあります：`NodeStatus`の更新と[Lease object](/docs/reference/generated/kubernetes-api/{{< latest-version >}}#lease-v1-coordination-k8s-io)です。 各ノードは`kube-node-lease`という{{< glossary_tooltip term_id="namespace" text="namespace">}}に関連したLeaseオブジェクトを持ちます。 Leaseは軽量なリソースで、クラスターのスケールに応じてノードのハートビートにおけるパフォーマンスを改善します。 kubeletが`NodeStatus`とLeaseオブジェクトの作成および更新を担当します。 - kubeletは、ステータスに変化があったり、設定した間隔の間に更新がない時に`NodeStatus`を更新します。`NodeStatus`更新のデフォルト間隔は５分です。（到達不能の場合のデフォルトタイムアウトである40秒よりもはるかに長いです） - kubeletは10秒間隔(デフォルトの更新間隔)でLeaseオブジェクトの生成と更新を実施します。Leaseの更新は`NodeStatus`の更新とは独立されて行われます。Leaseの更新が失敗した場合、kubeletは200ミリ秒から始まり7秒を上限とした指数バックオフでリトライします。 </del> #### 信頼性

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. --About Graceful node shutdown Swap memory management Why is this needed Graceful node shutdown is FEATURE STATE: Kubernetes v1.21 [beta] and Swap memory management is FEATURE STATE: Kubernetes v1.22 [alpha] The Japanese documents do not reflect the latest updates of them. In addition to that, I made some corrections. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/language ja
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten because the related PR is under reviewing /triage accepted
Change:
<ins> --- title: Container Runtime Interface id: container-runtime-interface date: 2021-11-24 full_link: /docs/concepts/architecture/cri short_description: > El protocolo principal para la comunicación entre el kubelet y el Container Runtime. aka: tags: - cri --- El protocolo principal para la comunicación entre el _kubelet_ y el _Container Runtime_. <!--more--> La _Kubernetes Container Runtime Interface_ (CRI) define el principal protocolo de [gRPC](https://grpc.io) para la comunicación entre los [componentes de clúster](/docs/concepts/overview/components/#componentes-de-nodo) _{{<glossary_tooltip text="kubelet" term_id="kubelet">}}_ y _{{<glossary_tooltip text="container runtime" term_id="container-runtime">}}_. </ins>

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /language es /kind feature /sig docs
/assign
Change:
1. If the pod does not have a `ServiceAccount` set, it sets the `ServiceAccount` to `default`. 1. It ensures that the `ServiceAccount` referenced by the pod exists, and otherwise rejects it. <del> 1. It adds a `volume` to the pod which contains a token for API access if neither the ServiceAccount `automountServiceAccountToken` nor the Pod's `automountServiceAccountToken` is set to `false`. 1. It adds a `volumeSource` to each container of the pod mounted at `/var/run/secrets/kubernetes.io/serviceaccount`, if the previous step has created a volume for ServiceAccount token. 1. If the pod does not contain any `imagePullSecrets`, then `imagePullSecrets` of the `ServiceAccount` are added to the pod. </del> <ins> 1. It adds a `volume` to the pod which contains a token for API access if neither the ServiceAccount `automountServiceAccountToken` nor the Pod's `automountServiceAccountToken` is set to `false`. 1. It adds a `volumeSource` to each container of the pod mounted at `/var/run/secrets/kubernetes.io/serviceaccount`, if the previous step has created a volume for the ServiceAccount token. 1. If the pod does not contain any `imagePullSecrets`, then `imagePullSecrets` of the `ServiceAccount` are added to the pod. </ins> #### Bound Service Account Token Volume {{< feature-state for_k8s_version="v1.22" state="stable" >}} <del> The ServiceAccount admission controller will add the following projected volume instead of a Secret-based volume for the non-expiring service account token created by Token Controller. </del> <ins> The ServiceAccount admission controller will add the following projected volume instead of a Secret-based volume for the non-expiring service account token created by the Token controller. </ins> ```yaml - name: kube-api-access-<random-suffix>

Discussion:
says about : Since 1.22 is released, the text shall not say what is planned to happen in the 1.22 versions, as if those were in the future.
/triage accepted /kind bug /assign
/language en
Change:
#### Referring to an imagePullSecrets on a Pod Now, you can create pods which reference that secret by adding an `imagePullSecrets` <del> section to a Pod definition. </del> <ins> section to a Pod definition. Each item in the `imagePullSecrets` array can only reference a Secret in the same namespace. </ins> For example:

Discussion:
In the section, it could be really helpful to add a callout note that the secret MUST be of . I spent hours trying to debug image pull issues because my image pull secret was of the default secret type (Opaque) instead of .
/retitle Call out that image pull Secrets must be of appropriate type /language en /kind feature
/triage accepted with the proviso that the PR will need tech review: I haven't looked at the code to check the list of Secret types that are acceptable.
/assign
Hi These are the types of secrets that are supported And we use and as a type for . I hope this will be helpful for the PR.
Change:
<div class="row"> <div class="col-md-12"> <del> <h3>Using labels</h3> </del> <ins> <h3>Step 2: Using labels</h3> </ins> <div class="content"> <p>The Deployment created automatically a label for our Pod. With the <code>describe deployment</code> subcommand you can see the name (the <em>key</em>) of that label:</p> <p><code><b>kubectl describe deployment</b></code></p>

Discussion:
Hello I found an inconsistency in the Kubernetes Tutorial. When following the steps for exposing an app it deletes the service in the end. When following up on the next page: "Once you're ready, move on to ." There seems to be the expectancy of an existing service, which got deleted in the previous steps. Step 3: Deleting a service: You deleted the service associated with the deployment. Following step: Load Balancing: The tutorial then expects you to use the deleted service to check load balancing, which is not possible. The $NODE_PORT variable is set using the deleted service. First the service should be re-created. Kind regards. Daisy
Page reported in issue: /language en
/retitle Tutorial Inconsistency: Deletion of service in "Using a Service to Expose Your App" hinders progression in "Running Multiple Instances of Your App" tutorial
the documentation does mention a note at the start of the page NOTE If you are trying this after , you may need to start from as the services may have been deleted Would adding more emphasis to this note address your request?
Modifying the note accordingly would help to address the issue.
/triage accepted Fixes are welcome
/assign I will submit a PR.
I won't say the documentation is wrong here, but things can be improved /kind feature
/priority backlog
My mistake, apologies. The note is actually pretty clear like mentioned. Perhaps a small modification to make the instruction more clear would be enough. Thankyou. NOTE If you are trying this after , you may need to start from as the services may have been deleted
Change:
<li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span></li><li class="metric_deprecated_version"><label class="metric_detail">Deprecated Versions:</label><span>1.30.0</span></li></ul> </div><div class="metric" data-stability="alpha"> <ins> <div class="metric_name">apiserver_encryption_config_controller_automatic_reload_last_timestamp_seconds</div> <div class="metric_help">Timestamp of the last successful or failed automatic reload of encryption configuration split by apiserver identity.</div> <ul> <li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li> <li data-type="gauge"><label class="metric_detail">Type:</label> <span class="metric_type">Gauge</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span><span class="metric_label">status</span></li></ul> </div><div class="metric" data-stability="alpha"> </ins> <div class="metric_name">apiserver_encryption_config_controller_automatic_reload_success_total</div> <div class="metric_help">Total number of successful automatic reloads of encryption configuration split by apiserver identity.</div> <ul>

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: removed metric from the documented metrics for Kubernetes v1.30, but the metric is still collected for the API server (ref: and ). Proposed Solution: Reinstate the documentation for such metric. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.30 <!--Additional Information:--
/sig instrumentation
/triage accepted
This metrics exists in the file generated by . Or there is a problem with the file generated by before. Let me generate the metrics file again and see. /assign
After I re-ran the script, some metrics were indeed missing (not just metrics ), it was a problem with the generated script, I will take a closer look.
Change:
* [コンテナ環境](/ja/docs/concepts/containers/container-environment/)の詳細 <del> * [コンテナライフサイクルイベントへのハンドラー紐付け](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオン </del> <ins> * [コンテナライフサイクルイベントへのハンドラー紐付け](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオン </ins>

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/container-lifecycle- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/container-lifecycle- is outdated. 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:
padding-bottom: 10px border-bottom: 1px solid #cccccc <ins> // Make sure anchor links aren't hidden by the header &:before display: block content: " " margin-top: -$header-clearance height: $header-clearance visibility: hidden </ins> h1 font-size: 32px padding-right: 60px

Discussion:
For any section deeplink, the linked section title and some content is now obscured in the viewport by the floating header menu. Example: ! This occurs regardless of browser window width: ! Yay responsive design, but :cry: being able to actually read the content w/o scrolling.
Thanks to for the fix!
Change:
- `["IPv4","IPv6"]` (dual stack) - `["IPv6","IPv4"]` (dual stack) <del> The first family you list is used for the legacy `.spec.ClusterIP` field. </del> <ins> The first family you list is used for the legacy `.spec.clusterIP` field. </ins> ### Dual-stack Service configuration scenarios

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:
### Pull Requestを送るまで <del> 未翻訳ページの新規翻訳作業と既存ページの修正作業でそれぞれ手順が異なります。 既存ページへの追加修正については、後述の[マイルストーンについて](#milestones)に目を通すことをおすすめします。 </del> #### 新規ページを翻訳する場合の手順 {#translate-new-page} 1. `kubernetes/website`リポジトリをフォークする <del> 2. `master`から任意の名前でブランチを作成する </del> <ins> 2. `main`から任意の名前でブランチを作成する </ins> 3. `content/en`のディレクトリから必要なファイルを`content/ja`にコピーし、翻訳する <del> 4. `master`ブランチに向けてPull Requestを作成する </del> <ins> 4. `main`ブランチに向けてPull Requestを作成する </ins> #### 既存のページの誤字脱字や古い記述を修正する場合の手順 1. `kubernetes/website`リポジトリをフォークする <del> 2. `dev-1.18-ja.2`(最新のマイルストーンブランチに適宜読み替えること)から任意の名前でブランチを作成し、該当箇所を編集する 3. `dev-1.18-ja.2`(最新のマイルストーンブランチに適宜読み替えること)ブランチに向けてPull Requestを作成する ### マイルストーンについて {#milestones} 翻訳作業を集中的に管理するために、日本語を含む複数の言語ではマイルストーンを採用しています。 各マイルストーンでは、 - 最低要件のコンテンツの追加・更新(項目については[こちら](https://kubernetes.io/docs/contribute/localization/#translating-documents)を参照してください) - バージョンに追従できていない翻訳済みコンテンツの更新 を行い、ドキュメントの全体的なメンテナンスを行っています。 マイルストーンのバージョンはOwner権限を持つメンバーが管理するものとします。 </del> <ins> 2. `main`から任意の名前でブランチを作成する 3. `content/ja`のディレクトリから必要なファイルを編集する 4. `main`ブランチに向けてPull Requestを作成する </ins> ## 翻訳スタイルガイド

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. --Update Why is this needed the Japanese localization, milestones are no longer used. default branch for kubernetes/website is now 'main' instead of 'master'. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
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 ja /assign
/area localization