jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report Problem: Doc is not aligned with latest kubernetes version 1.19.2: With version 1.19.2, is mandatory. Also signer is not supported in the list at: Proposed Solution: Specify in yaml definition Remove section Page to Update:
Just checked, the is a required field since 1.19.0 in group, but it is not required in the group. It makes sense to fix the example so that the YAML works. /sig auth
changed the apiVersion without actually updating required fields for v1
cc
About proposal "Remove section" of this issue, the v1.19 release notes indicates: Ref: Can you create a PR for this?
The documentation should remain until v1beta1 is no longer supported
I am happy to create a PR, but I am not able to push a branch to this repo. I have already signed CLA but still get: Any idea? Did I miss something in contribution doc? I will have a look at that again.
push it to your own clone, then use github to raise a pull request.
Great thanks. PR on the way then. :)

Discussion:
The CertificateSigningRequest object includes a PEM-encoded PKCS#10 signing request in the `spec.request` field. The CertificateSigningRequest denotes the _signer_ (the recipient that the request is being made to) using the `spec.signerName` field. <ins> Note that `spec.signerName` is a required key after api version `certificates.k8s.io/v1`. </ins> Once created, a CertificateSigningRequest must be approved before it can be signed. Depending on the signer selected, a CertificateSigningRequest may be automatically approved

1. Expiration/certificate lifetime - minimum of CSR signer or request. 1. CA bit allowed/disallowed - not allowed. <del> 1. `kubernetes.io/legacy-unknown`:  has no guarantees for trust at all. Some distributions may honor these as client certs, but that behavior is not standard Kubernetes behavior. </del> <ins> 1. `kubernetes.io/legacy-unknown`:  has no guarantees for trust at all. Some third-party distributions of Kubernetes may honor client certificates signed by it. The stable CertificateSigningRequest API (version `certificates.k8s.io/v1` and later) does not allow to set the `signerName` as `kubernetes.io/legacy-unknown`. </ins> Never auto-approved by {{< glossary_tooltip term_id="kube-controller-manager" >}}. 1. Trust distribution: None.  There is no standard trust or distribution for this signer in a Kubernetes cluster. 1. Permitted subjects - any
Change:
/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly 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

Discussion:
### 服务控制器   {#service-controller} {{< glossary_tooltip text="服务（Service）" term_id="service" >}}与受控的负载均衡器、 <del> IP 地址、网络包锅里煮、目标健康检查等云基础设施组件集成。 </del> <ins> IP 地址、网络包过滤、目标健康检查等云基础设施组件集成。 </ins> 服务控制器与云驱动的 API 交互，以配置负载均衡器和其他基础设施组件。 你所创建的 Service 资源会需要这些组件服务。
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 The Kubernetes website generates a sitemap. Let's highlight specific pages using priority weighting: (and any localization that copies the priority weight) (and any localization that copies the priority weight) (and any localization that copies the priority weight) Why is this needed: Making this change helps search engines understand what pages the Kubernetes project sees as important. Comments /kind feature

Discussion:
[permalinks] blog = "/:section/:year/:month/:day/:slug/" <ins> [sitemap] filename = "sitemap.xml" priority = 0.75 </ins> # Be explicit about the output formats. We (currently) only want an RSS feed for the home page. [outputs] home = [ "HTML", "RSS", "HEADERS" ]

title: "Production-Grade Container Orchestration" abstract: "Automated container deployment, scaling, and management" cid: home <ins> sitemap: priority: 1.0 </ins> --- {{< blocks/section id="oceanNodes" >}}

--- linktitle: Kubernetes Documentation title: Documentation <ins> sitemap: priority: 1.0 </ins> ---

title: "Overview" weight: 20 description: Get a high-level outline of Kubernetes and the components it is built from. <ins> sitemap: priority: 0.9 </ins> ---

card: name: concepts weight: 10 <ins> sitemap: priority: 0.9 </ins> --- <!-- overview -->
Change:
proxy --forward .
/assign /language zh
page: below yaml config comes from k8s 1.19

Discussion:
ready kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure <del> upstream </del> fallthrough in-addr.arpa ip6.arpa ttl 30 } prometheus :9153 <del> proxy ./etc/resolv.conf </del> <ins> forward ./etc/resolv.conf </ins> cache 30 loop reload
Change:
could you please be more specific? I cannot find the broken link...
if you enter [], you can see next describtion: Pod PodPreset Secret Pod . and you click ‘’ the link is broken
thank you, I'm fixing it now ~
/assign
/language zh

Discussion:
title: 容器环境变量 id: container-env-variables date: 2018-04-12 <del> full_link: /docs/concepts/containers/container-environment-variables.md </del> <ins> full_link: /zh/docs/concepts/containers/container-environment/ </ins> short_description: > 容器环境变量提供了运行容器化应用所必须的一些重要信息。

title: Container Environment Variables id: container-env-variables date: 2018-04-12 <del> full_link: /docs/concepts/containers/container-environment-variables.md </del> <ins> full_link: /zh/docs/concepts/containers/container-environment/ </ins> short_description: > Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
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. --kubectl reference link to shows 404. and wont redirect to correct page <!--Required Information--Problem: /language zh Reference Link did not update/ not support redirect Proposed Solution: Update link to in document Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--

Discussion:
<!-- {{< note >}}For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/).{{< /note >}} --> <del> {{< note >}}有关 kubectl 命令的更多信息，请参阅 [kubectl 概述](/zh/docs/user-guide/kubectl-overview/)。{{< /note >}} </del> <ins> {{< note >}}有关 kubectl 命令的更多信息，请参阅 [kubectl 概述](/zh/docs/reference/kubectl/overview/)。{{< /note >}} </ins> <!-- ## Create a Service
Change:
This is a Bug Report run : output : my environment: mac version10.14.3 bash: 5.0.11 docker engine19.03.13 Proposed Solution: I try to figure out what's the problem, and I got following clue: line 71 of Makefile: container, list directory of /src/resources : line 32 of Dockerfile: seems it is a permission problem I simply commented out lines 32 of dockerfile , and the problem get solved Page to Update: Makefile Dockerfile
/assign
/cc
/priority important-soon
It seems like the challenge for compatibility is the Docker Desktop product on macOS. The symptoms don't seem to be present on Linux.
/kind bug /triage accepted

Discussion:
--build-arg HUGO_VERSION=$(HUGO_VERSION) container-build: module-check <del> $(CONTAINER_RUN) $(CONTAINER_IMAGE) hugo --minify </del> <ins> $(CONTAINER_RUN) --read-only $(CONTAINER_IMAGE) hugo --minify </ins> container-serve: module-check <del> $(CONTAINER_RUN) --mount type=tmpfs,destination=/src/resources,tmpfs-mode=0777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 </del> <ins> $(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir </ins> test-examples: scripts/test_examples.sh install

# Hindi is disabled because it's currently in development. disableLanguages = ["hi", "no"] <ins> [caches] [caches.assets] dir = ":cacheDir/_gen" maxAge = -1 [caches.getcsv] dir = ":cacheDir/:project" maxAge = "60s" [caches.getjson] dir = ":cacheDir/:project" maxAge = "60s" [caches.images] dir = ":cacheDir/_images" maxAge = -1 [caches.modules] dir = ":cacheDir/modules" maxAge = -1 </ins> [markup] [markup.goldmark] [markup.goldmark.extensions]
Change:
Second sentence of the second paragraph is obviously incomplete. It reads like this . ! It would be good to restore missing bit.
Page is PR introduced the regression; I suggest the second “handles” should instead read “determines what action to take to make the Pod healthy again”. /kind bug /language en /triage accepted /priority backlog Thanks
/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 : /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

Discussion:
Whilst a Pod is running, the kubelet is able to restart containers to handle some kind of faults. Within a Pod, Kubernetes tracks different container <del> [states](#container-states) and handles </del> <ins> [states](#container-states) and determines what action to take to make the Pod healthy again. </ins> In the Kubernetes API, Pods have both a specification and an actual status. The status for a Pod object consists of a set of [Pod conditions](#pod-conditions).

ephemeral (rather than durable) entities. Pods are created, assigned a unique ID ([UID](/docs/concepts/overview/working-with-objects/names/#uids)), and scheduled to nodes where they remain until termination (according to restart policy) or <del> deletion. </del> <ins> deletion. </ins> If a {{< glossary_tooltip term_id="node" >}} dies, the Pods scheduled to that node are [scheduled for deletion](#pod-garbage-collection) after a timeout period.

1. You use the `kubectl` tool to manually delete a specific Pod, with the default grace period (30 seconds). 1. The Pod in the API server is updated with the time beyond which the Pod is considered "dead" <del> along with the grace period. </del> <ins> along with the grace period. </ins> If you use `kubectl describe` to check on the Pod you're deleting, that Pod shows up as <del> "Terminating". </del> <ins> "Terminating". </ins> On the node where the Pod is running: as soon as the kubelet sees that a Pod has been marked as terminating (a graceful shutdown duration has been set), the kubelet begins the local Pod shutdown process.

`SIGKILL` to any processes still running in any container in the Pod. The kubelet also cleans up a hidden `pause` container if that container runtime uses one. 1. The kubelet triggers forcible removal of Pod object from the API server, by setting grace period <del> to 0 (immediate deletion). </del> <ins> to 0 (immediate deletion). </ins> 1. The API server deletes the Pod's API object, which is then no longer visible from any client. ### Forced Pod termination {#pod-termination-forced}
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 I finished the translation of docs/reference/using-api/health-, I found a broken link when clicked the "API ":  Proposed Solution: fix it in
/language zh /assign /kind bug
/triage accepted

Discussion:
title: kube-apiserver id: kube-apiserver date: 2018-04-12 <del> full_link: /docs/reference/generated/kube-apiserver/ </del> <ins> full_link: /zh/docs/reference/command-line-tools-reference/kube-apiserver/ </ins> short_description: > <del> 主节点上负责提供 Kubernetes API 服务的组件；它是 Kubernetes 控制面的前端。 </del> <ins> 提供 Kubernetes API 服务的控制面组件。 </ins> aka: tags:

title: kube-apiserver id: kube-apiserver date: 2018-04-12 <del> full_link: /docs/reference/generated/kube-apiserver/ </del> <ins> full_link: /zh/docs/reference/command-line-tools-reference/kube-apiserver/ </ins> short_description: > <del> Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. </del> <ins> Control plane component that serves the Kubernetes API. </ins> aka: tags:

--> <!-- <del> Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. </del> <ins> The API server is a component of the Kubernetes {{< glossary_tooltip text="control plane" term_id="control-plane" >}} that exposes the Kubernetes API. The API server is the front end for the Kubernetes control plane. </ins> --> <del> 主节点上负责提供 Kubernetes API 服务的组件；它是 Kubernetes 控制面的前端。 </del> <ins> API 服务器是 Kubernetes {{< glossary_tooltip text="控制面" term_id="control-plane" >}}的组件， 该组件公开了 Kubernetes API。 API 服务器是 Kubernetes 控制面的前端。 </ins> <!--more--> <!-- <del> It is designed to scale horizontally - that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/). </del> <ins> The main implementation of a Kubernetes API server is [kube-apiserver](/docs/reference/generated/kube-apiserver/). kube-apiserver is designed to scale horizontally&mdash;that is, it scales by deploying more instances. You can run several instances of kube-apiserver and balance traffic between those instances. </ins> --> <del> kube-apiserver 在设计上考虑了水平扩缩的需要。 换言之，通过部署多个实例可以实现扩缩。 参见[构造高可用集群](/docs/admin/high-availability/)。 </del> <ins> Kubernetes API 服务器的主要实现是 [kube-apiserver](/zh/docs/reference/command-line-tools-reference/kube-apiserver/)。 kube-apiserver 设计上考虑了水平伸缩，也就是说，它可通过部署多个实例进行伸缩。 你可以运行 kube-apiserver 的多个实例，并在这些实例之间平衡流量。 </ins>
Change:
There is a grammatical error, should be "УстановкА
/language ru page is Thanks for reporting this
You are welcome) But, the page, where i found it is here:
Thanks for clarifying
/assign
/triage accepted

Discussion:
* Поддержка CNI (Container Network Interface) * Ingress <del> ## Установке </del> <ins> ## Установка </ins> Посмотрите страницу [Установка Minikube](/ru/docs/tasks/tools/install-minikube/).
Change:
Problem: Wasn't sure how to report this so selected bug as it seemed closest to what to report Running from the directory should return the diff and then close without output. But it shows the diff then outputs that the page is still in sync. Output Proposed Solution: Remove output from showing after the diff is shown when a page is not in sync. Page to Update: N/A Thanks for the script (for whoever wrote this). :]
/triage accepted /assign

Discussion:
# Last commit for the localized file LASTCOMMIT=`git log -n 1 --pretty=format:%h -- $LOCALIZED` <del> git diff $LASTCOMMIT...HEAD $EN_VERSION </del> <ins> git diff --exit-code $LASTCOMMIT...HEAD $EN_VERSION </ins> if [ "$?" -eq 0 ]; then echo "$LOCALIZED is still in sync"
Change:
Please replace the code from to please kindly check the mistake in below link
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
/good-first-issue
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 : /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

Discussion:
指向该域名服务器，而不是 `/etc/resolv.conf`。 ``` <del> proxy .  172.16.0.1 </del> <ins> forward .  172.16.0.1 </ins> ``` <!--
Change:
[UBUNTU 20.04] specifies the following command: This runs into the following error: Update the command to: Or... use the command which is also mentioned on the
Thanks for reporting this. I wonder if we should also recommend that readers ? /kind bug /triage accepted /priority important-longterm /language en /sig node
That is a possibility. But I think it would be logical to take over the official documentation of docker.
Did PR help here? /triage needs-information /remove-triage accepted
/retitle Incorrect commands for adding PGP keys to APT configuration
/triage accepted /remove-triage needs-information

Discussion:
deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ / EOF <del> curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg - curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg - </del> <ins> curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - </ins> sudo apt-get update sudo apt-get install cri-o cri-o-runc

deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ / EOF <del> curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers-cri-o.gpg - </del> <ins> curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers-cri-o.gpg add - </ins> sudo apt-get update sudo apt-get install cri-o cri-o-runc

```shell # Add Docker's official GPG key: <del> curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/docker.gpg - </del> <ins> curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key --keyring /etc/apt/trusted.gpg.d/docker.gpg add - </ins> ``` ```shell
Change:
Maybe its just me, but reading the page first time it is not clear what these volume-snapshots are really good for. Reading it again doesn't help, but it makes one thing clear: Taking a snapshot is just half of the story. Maybe a practical example (e.g. backup and restore of a mysql database, migration to another cluster) would be an improvement.
Thanks for the suggestion /language en /triage accepted /sig storage /priority backlog
/assign

Discussion:
`VolumeSnapshotClass` allows you to specify different attributes belonging to a `VolumeSnapshot`. These attributes may differ among snapshots taken from the same volume on the storage system and therefore cannot be expressed by using the same `StorageClass` of a `PersistentVolumeClaim`. <ins> Volume snapshots provide Kubernetes users with a standardized way to copy a volume's contents at a particular point in time without creating an entirely new volume. This functionality enables, for example, database administrators to backup databases before performing edit or delete modifications. </ins> Users need to be aware of the following when using this feature: * API Objects `VolumeSnapshot`, `VolumeSnapshotContent`, and `VolumeSnapshotClass` are {{< glossary_tooltip term_id="CustomResourceDefinition" text="CRDs" >}}, not part of the core API.

the *dataSource* field in the `PersistentVolumeClaim` object. For more details, see <del> [Volume Snapshot and Restore Volume from Snapshot](/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support). </del> <ins> [Volume Snapshot and Restore Volume from Snapshot](/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support). </ins>  No newline at end of file
Change:
"Ander Installationsmethoden" here should not be a link to github but to this link:
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 de /kind cleanup /priority backlog Actually should either redirect to the (English) page, or it should be a stub that links there and explains that the documentation for Minikube is not localized.
/assign

Discussion:
### Linux {{< note >}} <del> Dieses Dokument zeigt Ihnen, wie Sie Minikube mit einer statischen Binärdatei unter Linux installieren. Für alternative Linux-Installationsmethoden siehe [Andere Installationsmethoden](https://github.com/kubernetes/minikube#other-ways-to-install) im offiziellen Minikube-GitHub-Repository. </del> <ins> Dieses Dokument zeigt Ihnen, wie Sie Minikube mit einer statischen Binärdatei unter Linux installieren. Für alternative Linux-Installationsmethoden siehe [Andere Installationsmethoden](https://minikube.sigs.k8s.io/docs/start/) im offiziellen Minikube-GitHub-Repository. </ins> {{< /note >}} Sie können Minikube unter Linux installieren, indem Sie eine statische Binärdatei herunterladen:
Change:
! ‘ ConfigMap](#create-configmaps-from-files) ’
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

Discussion:
--> ## 将 ConfigMap 数据添加到一个卷中 <del> 如基于文件创建 ConfigMap](#create-configmaps-from-files) 中所述，当你使用 </del> <ins> 如基于文件创建 [ConfigMap](#create-configmaps-from-files) 中所述，当你使用 </ins> `--from-file` 创建 ConfigMap 时，文件名成为存储在 ConfigMap 的 `data` 部分中的键， 文件内容成为键对应的值。
Change:
there is an useless "" character on
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

Discussion:
{{< /table >}} {{< note >}} <del> <!-- Generators other than `run-pod/v1` are deprecated. -->不推荐使用 `run-pod/v1` 以外的其他生成器。 </del> <ins> <!--Generators other than `run-pod/v1` are deprecated.--> 不推荐使用 `run-pod/v1` 以外的其他生成器. </ins> {{< /note >}} <!--