jiebi/CodeConvo huggingface dataset:
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: has a heading, “Download Kubernetes”. However, this heading isn't followed by a button labelled Download as you might expect. Instead, there are links to the release notes. Proposed Solution: Either: Rename the heading to “Release Notes”(?) or Add a button (maybe using a shortcode), Download, that links to (and set this up to be updated automatically when a new version is released). The button should be under the “Download Kubernetes” heading. or Add a button (maybe using a shortcode), Download, that links to The button should be under the “Download Kubernetes” heading. This will take readers to the right page but they will have to find the download links themselves. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 Additional Information: /language en
If we wanna go with either option 1 or option 3, I can help with that. Not sure what is the best way to automagically keep the link updated in option 2. Is there some Hugo site param that can be used for that?
let's go with a thing we can implement, and if someone (you? me?) feels strongly they can log a new issue to track the idea of making it even better.

Discussion:
description: Anyone can contribute, whether you’re new to the project or you’ve been around a long time. button: Contribute to the docs button_path: /docs/contribute <del> - name: download title: Download Kubernetes </del> <ins> - name: release-notes title: Release Notes </ins> description: If you are installing Kubernetes or upgrading to the newest version, refer to the current release notes. - name: about title: About the documentation

title: v1.18 Release Notes weight: 10 card: <del> name: download </del> <ins> name: release-notes </ins> weight: 20 anchors: - anchor: "#"
Change:
This is a Bug Report <!--Required Information--Problem: Text formatting issue under the Create a Minikube cluster heading. The text is listed erroneously (this appears to be a simple authoring/build issue with the content. Proposed Solution: Fix the typo or the build issue for this section of the page. Page to Update:
/labels language/en /assign
Relevant to issue
/language en /kind bug /priority important-longterm

Discussion:
{{< kat-button >}} <del> {{< note >}}If you installed Minikube locally, run `minikube start`.{{< /note >}} </del> <ins> {{< note >}} If you installed Minikube locally, run `minikube start`. {{< /note >}} </ins> 2. Open the Kubernetes dashboard in a browser:

kubectl config view ``` <del> {{< note >}}For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/).{{< /note >}} </del> <ins> {{< note >}} For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/). {{< /note >}} </ins> ## Create a Service
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 link navigates to . However, there is no ID . Proposed Solution: It would probably be fine to replace the link with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign PR created:
/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

Discussion:
- **CPU requirement (cores)** and **Memory requirement (MiB)**: You can specify the minimum [resource limits](/docs/tasks/configure-pod-container/limit-range/) for the container. By default, Pods run with unbounded CPU and memory limits. <del> - **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/user-guide/containers/#containers-and-commands). You can use the command options and arguments to override the default. </del> <ins> - **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/tasks/inject-data-application/define-command-argument-container/). You can use the command options and arguments to override the default. </ins> - **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.
Change:
This is a Bug Report Problem: The document is not rendered correctly: ! Proposed Solution: In-lining this special cases text by removing the call-out seems reasonable? Page to Update:
This is related to tracking issue . The long term fix is probably along the lines of For a work-around, how about rewording the note so that it remains called out but does not use a bulleted list? /kind bug /language en

Discussion:
There are two special cases: <del> * An empty `key` with operator `Exists` matches all keys, values and effects which means this </del> <ins> An empty `key` with operator `Exists` matches all keys, values and effects which means this </ins> will tolerate everything. <del> ```yaml tolerations: - operator: "Exists" ``` * An empty `effect` matches all effects with key `key`. ```yaml tolerations: - key: "key" operator: "Exists" ``` </del> <ins> An empty `effect` matches all effects with key `key`. </ins> {{< /note >}}
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: / . '' '' . English | -- | -- Default Limit | Default Request | max limit/request ratio | / Resource Limit | Proposed Solution: / '' '' , . LimitRange API yaml English -- -- Default Limit Default Request max limit/request ratio Resource Limit limit ResourceQuota, LimitRange request ResourceQuota, LimitRange Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
. before : LimitRange after : ResourceQuota, LimitRange LimitRange ResourceQuota .

Discussion:
DaemonSet | 데몬셋(DaemonSet) | API 오브젝트인 경우 Dashboard | 대시보드 | Data Plane | 데이터 플레인 | <del> Default Limit | 기본 상한 | Default Request | 기본 요청량 | </del> Deployment | 디플로이먼트(Deployment) | API 오브젝트인 경우 deprecated | 사용 중단(deprecated) | descriptor | 디스크립터, 식별자 |

Lease | 리스(Lease) | API 오브젝트인 경우 lifecycle | 라이프사이클 | LimitRange | 리밋레인지(LimitRange) | API 오브젝트인 경우 <ins> limit | 한도(limit) | 리소스의 개수나 용량을 한정하기 위한 수치로 사용된 경우 선택적으로 사용 (API 오브젝트의 속성으로 limit을 사용한 경우는 가능한 영문 유지) </ins> Linux | 리눅스 | load | 부하 | LocalSubjectAccessReview | 로컬서브젝트액세스리뷰(LocalSubjectAccessReview) | API 오브젝트인 경우

Machine | 머신 | manifest | 매니페스트 | Master | 마스터 | <del> max limit/request ratio | 최대 상한/요청량 비율 | </del> metadata | 메타데이터 | metric | 메트릭 | masquerading | 마스커레이딩 |

replicas | 레플리카 | ReplicationController | 레플리케이션컨트롤러(ReplicationController) | API 오브젝트인 경우 repository | 리포지터리 | <ins> request | 요청(request) | 리소스의 개수나 용량에 대한 요청 수치를 표현하기 위해 사용된 경우 선택적으로 사용 (API 오브젝트 속성으로 request를 사용한 경우는 가능한 영문을 유지) </ins> resource | 리소스 | <del> Resource Limit | 리소스 상한 | </del> ResourceQuota | 리소스쿼터(ResourceQuota) | API 오브젝트인 경우 return | 반환하다 | revision | 리비전 |
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 to follow v1.17 of the original (Englist) text. Why is this needed it outdated. Comments /language ja /good-first-issue File to update Original 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 here or #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 to follow v1.17 of the original (Englist) text. it 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 Bo0km4n
/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

Discussion:
- fundamental - core-object --- <del> クラスター内の各ノードで実行されるエージェントです。各コンテナがPodで実行されていることを保証します。 </del> <ins> クラスター内の各{{< glossary_tooltip text="ノード" term_id="node" >}}で実行されるエージェントです。各{{< glossary_tooltip text="コンテナ" term_id="container" >}}が{{< glossary_tooltip text="Pod" term_id="pod" >}}で実行されていることを保証します。 </ins> <!--more--> <del> kubeletは、さまざまなメカニズムを通じて提供されるPodSpecのセットを取得し、それらのPodSpecに記述されているコンテナが正常に実行されている状態に保ちます。kubeletは、Kubernetesが作成したものではないコンテナは管理しません。 </del> <ins> kubeletは、さまざまなメカニズムを通じて提供されるPodSpecのセットを取得し、それらのPodSpecに記述されているコンテナが正常に実行されている状態を保証します。kubeletは、Kubernetesが作成したものではないコンテナは管理しません。 </ins>
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: Blog " MIPS Kubernetes " format error. Proposed Solution: Update blog format. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh

Discussion:
<del> <!-- </del> <ins> --- </ins> layout: blog <del> title: "Kubernetes on MIPS" </del> <ins> title: "基于 MIPS 架构的 Kubernetes 方案" </ins> date: 2020-01-15 slug: Kubernetes-on-MIPS <del> --> </del> --- <ins> <!-- </ins> layout: blog <del> title: "基于 MIPS 架构的 Kubernetes 方案" </del> <ins> title: "Kubernetes on MIPS" </ins> date: 2020-01-15 slug: Kubernetes-on-MIPS <del> --- </del> <ins> --> </ins> <!-- **Authors:** TimYin Shi, Dominic Yin, Wang Zhan, Jessica Jiang, Will Cai, Jeffrey Gao, Simon Sun (Inspur)
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: When the status of the pod is Completed, the command below does not work: kubectl exec hostaliases-pod -- cat /etc/hosts With the error : error: cannot exec into a container in a completed pod; current phase is Succeeded Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.18.3 <!--Additional Information:--
i am not certain about this but we can't exec into a pod which is completed.There is a regarding this feature to be implemented .But cant find any updates there.
Fixed. /close
Closing this issue. <detailsIn response to : Fixed. /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

Discussion:
The `hosts` file content would look like this: ```shell <del> kubectl exec hostaliases-pod -- cat /etc/hosts </del> <ins> kubectl logs hostaliases-pod </ins> ``` ```none
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--The FeatureGate "IPv6DualStack" does not exist in the feature gate reference page. There is no way to clearly track the support for dual stack as Alpha/Beta/GA.. Proposed Solution: Please add the feature gate referenced in "" in the feature gate reference page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--version v1.18 <!--Additional Information:--
/assign /kind bug
/sig network

Discussion:
| `HugePageStorageMediumSize` | `false` | Alpha | 1.18 | | | `HyperVContainer` | `false` | Alpha | 1.10 | | | `ImmutableEphemeralVolumes` | `false` | Alpha | 1.18 | | <ins> | `IPv6DualStack` | `false` | Alpha | 1.16 | | </ins> | `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 | | `KubeletPodResources` | `true` | Beta | 1.15 | | | `LegacyNodeRoleBehavior` | `true` | Alpha | 1.16 | |
Change:
Note shortcode with html comment wont be parsed correctly Problem: After has been updated since , the HTML comment inside will result in markdownify not working correctly. English version docs: ! Chinese version docs: ! Proposed Solution: Move the HTML comment outside the shortcode, it does work correctly. Just like this.
This partially duplicates issue

Discussion:
要确认 hypervisor 和 Minikube 均已成功安装，可以运行以下命令来启动本地 Kubernetes 集群： <del> {{< note >}} </del> <!-- For setting the `--vm-driver` with `minikube start`, enter the name of the hypervisor you installed in lowercase letters where `<driver_name>` is mentioned below. A full list of `--vm-driver` values is available in [specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver). --> <del> 通过 `minikube start` 设置 `--vm-driver`。在下面提到 `<driver_name>` 的地方，用小写字母，输入你安装的 hypervisor 的名称。 [指定 VM 驱动程序](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver) 列举了 `--vm-driver` 值的完整列表 </del> <ins> {{< note >}} 若要为 `minikube start` 设置 `--vm-driver`，在下面提到 `<driver_name>` 的地方，用小写字母输入你安装的 hypervisor 的名称。 [指定 VM 驱动程序](/docs/setup/learning-environment/minikube/#specifying-the-vm-driver) 列举了 `--vm-driver` 值的完整列表。 </ins> {{< /note >}} ```shell
Change:
Follow PR
/language ja
/assign
We can close this issue by
/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

Discussion:
Kubernetesプロジェクトでは、最新の3つのマイナーリリースについてリリースブランチを管理しています。 <del> セキュリティフィックスを含む適用可能な修正は、重大度や実行可能性によってはこれら3つのリリースブランチにバックポートされることもあります。パッチリリースは、定期的または必要に応じてこれらのブランチから分岐されます。[パッチリリースマネージャー](https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/patch-release-manager/README.md#release-timing)がこれを決定しています。パッチリリースマネージャーは[各リリースのリリースチーム](https://github.com/kubernetes/sig-release/tree/master/releases/)のメンバーです。 </del> <ins> セキュリティフィックスを含む適用可能な修正は、重大度や実行可能性によってはこれら3つのリリースブランチにバックポートされることもあります。パッチリリースは、[定期的](https://git.k8s.io/sig-release/releases/patch-releases.md#cadence)または必要に応じてこれらのブランチから分岐されます。[リリースマネージャー](https://git.k8s.io/sig-release/release-managers.md)グループがこれを決定しています。 </ins> <del> マイナーリリースは約3ヶ月ごとに行われるため、それぞれのリリースブランチは約9ヶ月間メンテナンスされます。 </del> <ins> 詳細は、Kubernetes[パッチリリース](https://git.k8s.io/sig-release/releases/patch-releases.md)ページを参照してください。 </ins> ## サポートされるバージョンの差異
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: isn't rendering correctly. Proposed Solution: Fix the Markdown for this page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language it /kind bug /priority important-longterm

Discussion:
<del> „--- </del> <ins> --- </ins> title: I componenti di Kubernetes content_type: concept weight: 20
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: Docker installation instructions are missing step for enabling service, so after host reboot docker is not running Proposed Solution: Add below command Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Thanks, good spot /kind bug /priority important-longterm
/assign

Discussion:
{{% /tab %}} {{< /tabs >}} <ins> If you want the docker service to start on boot, run the following command: ```shell sudo systemctl enable docker ``` </ins> Refer to the [official Docker installation guides](https://docs.docker.com/engine/installation/) for more information.
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: apiVersion: v1 kind: ConfigMap metadata: Name: game-demo data: # playerinitiallives: 3 uipropertiesfile_name: "user-interface.properties" # # game.properties: | ,monsters player.maximum-lives=5 user-interface.properties: | allow.textmode=true Name: game-demo. name should be lower case Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /priority backlog /language zh is incorrect in the manifest on it should be
/assign

Discussion:
apiVersion: v1 kind: ConfigMap metadata: <del> Name: game-demo </del> <ins> name: game-demo </ins> data: # 类属性键；每一个键都映射到一个简单的值 player_initial_lives: 3
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: There is a broken link to "CustomResourceDefinition" in concepts/overview/kubernetes-api/ URL: The linked page receives a 404 error: Proposed Solution: The link should be updated to link to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/assign

Discussion:
There are two paths to extending the API with [custom resources](/docs/concepts/api-extension/custom-resources/): <del> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resource-definitions/) </del> <ins> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/) </ins> lets you declaratively define how the API server should provide your chosen resource API. 1. You can also [implement your own extension API server](/docs/tasks/extend-kubernetes/setup-extension-api-server/) and use the [aggregator](/docs/tasks/extend-kubernetes/configure-aggregation-layer/)
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: There is an error in the command to Install Docker CE for Ubuntu 16.04+ Proposed Solution: Update the command whicht tells to Install Docker CE for Ubuntu. The command sais: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0ubuntu-$(lsbrelease -cs) But it should be: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0~ubuntu-$(lsbrelease -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) so it should be only 1 character of ~ instead of 2 ~~ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign

Discussion:
# Install Docker CE apt-get update && apt-get install -y  containerd.io=1.2.13-2  <del> docker-ce=5:19.03.11~3-0~~ubuntu-$(lsb_release -cs)  docker-ce-cli=5:19.03.11~3-0~~ubuntu-$(lsb_release -cs) </del> <ins> docker-ce=5:19.03.11~3-0~ubuntu-$(lsb_release -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) </ins> ``` ```shell
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 paragraph: The line is confusing at the page goes on to say later that K8S does not provide these solutions. Proposed Solution: I would suggest that the line be modified to be clear that . rather than saying that it provides those features. It is easier to understand for novice learners who are just getting started with K8S. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
That sounds like a good clarification /kind cleanup /language en /priority awaiting-more-evidence
/assign

Discussion:
## What Kubernetes is not <del> Kubernetes is not a traditional, all-inclusive PaaS (Platform as a Service) system. Since Kubernetes operates at the container level rather than at the hardware level, it provides some generally applicable features common to PaaS offerings, such as deployment, scaling, load balancing, logging, and monitoring. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable. Kubernetes provides the building blocks for building developer platforms, but preserves user choice and flexibility where it is important. </del> <ins> Kubernetes is not a traditional, all-inclusive PaaS (Platform as a Service) system. Since Kubernetes operates at the container level rather than at the hardware level, it provides some generally applicable features common to PaaS offerings, such as deployment, scaling, load balancing, and lets users integrate their logging, monitoring, and alerting solutions. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable. Kubernetes provides the building blocks for building developer platforms, but preserves user choice and flexibility where it is important. </ins> Kubernetes: