jiebi/CodeConvo huggingface dataset:
Change:
This is a Feature Request What would you like to be should be removed. Why is this needed The reasons are following. In English site, the contents of was to and was deleted. The diff is . () In Japanese site, has been translated. The diff is . () So I think that the page can be removed. Comments /language ja
/triage accepted I can see that the page already contains the contents from . For information: it seems that the page is slightly outdated, compared to the version ( ).
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]:
/remove-lifecycle stale
/assign

Discussion:
<del> --- title: コンテナの概要 content_type: concept weight: 1 --- <!-- overview --> コンテナは、アプリケーションの(コンパイルされた)コードと、実行時に必要な依存関係をパッケージ化するための技術です。実行する各コンテナは再現性があります。依存関係を含めることによる標準化は、どこで実行しても同じ動作が得られることを意味します。 コンテナは、基礎となるホストインフラストラクチャからアプリケーションを切り離します。これにより、さまざまなクラウド環境やOS環境でのデプロイが容易になります。 <!-- body --> ## コンテナイメージ {#container-images} [コンテナイメージ](/docs/concepts/containers/images/)は、アプリケーションを実行するために必要なすべてのものを含んだ、すぐに実行可能なソフトウェアパッケージです。コードとそれが必要とする任意のランタイム、アプリケーションとシステムのライブラリ、および必須の設定のデフォルト値が含まれています。 設計上、コンテナは不変であるため、すでに実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり、変更を加えたい場合は、変更を含む新しいコンテナをビルドし、コンテナを再作成して更新されたイメージから起動する必要があります。 ## コンテナランタイム {#container-runtimes} {{< glossary_definition term_id="container-runtime" length="all" >}} ## {{% heading "whatsnext" %}} * [コンテナイメージ](/docs/concepts/containers/images/)についてお読みください。 * [Pod](/ja/docs/concepts/workloads/pods/)についてお読みください。 </del>
Change:
should be because fieldSelector is intend to filter objects, not fields. Current translation may lead misunderstanding the functions of fieldSelector
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
Page: /language zh
/assign
/close The understanding is incorrect.
Closing this issue. <detailsIn response to : /close The understanding is incorrect. 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:
A selector to restrict the list of returned objects by their fields. Defaults to everything. <hr> --> <del> 根据返回对象的字段限制返回对象列表的选择器。默认为返回所有字段。 </del> <ins> 限制所返回对象的字段的选择器。默认为返回所有字段。 </ins> <hr> ## fieldValidation {#fieldValidation}
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: "Well-Known Labels, Annotations and Taints" says Except it's actually AND (?) cc Proposed Solution: Add Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Filing an issue so I don't forget this. See discussion
/assign
I think and both hold the same meaning.
/triage accepted

Discussion:
<!-- overview --> <del> Kubernetes reserves all labels and annotations in the kubernetes.io namespace. </del> <ins> Kubernetes reserves all labels and annotations in the kubernetes.io and k8s.io namespaces. </ins> This document serves both as a reference to the values and as a coordination point for assigning values.
Change:
Problem: The text on is working properly and redirects to the issue is to remove the URL has unnecessary context from the link as follows is For the problem, check the page . Proposed Solution: It should resolve this issue by removing the link context link and editing the text according to enhance the document line. Page to Update: Remove the text from URL and add suitable content. /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is working properly and redirects to the issue is to remove the URL has unnecessary context /html/AdministrationGuide/part- from the link as follows is It should resolve this issue by removing the link context link and editing the text according to enhance the document line. Remove the text /html/AdministrationGuide/part- from URL [Upgrade path to GA on and add suitable content.]( /assign /language en 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
/retitle Wrong link context on Storage Classes page
/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

Discussion:
* Distribute volume: `volumetype: none` For available volume types and administration options, refer to the <del> [Administration Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html). </del> <ins> [Administration Guide](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/). </ins> For further reference information, see [How to configure Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology).
Change:
On page: Based on the labels I see in the pod, I believe that the line that says: should be changed to:
/assign
/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
/language en

Discussion:
serving the health check at `/healthz`. You can test this: ```shell <del> kubectl get pod -o wide -l run=source-ip-app </del> <ins> kubectl get pod -o wide -l app=source-ip-app </ins> ``` The output is similar to this: ```
Change:
Hello, I noticed some punctuation errors on page /language zh
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:
--> [HostAliases](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core) 是一个包含主机名和 IP 地址的可选列表，配置后将被注入到 Pod 内的 hosts 文件中。 <del> 该选项仅适用于没有配置 hostNetwork 的 Pod. </del> <ins> 该选项仅适用于没有配置 hostNetwork 的 Pod。 </ins>

Minikube 在用户计算机上的一个虚拟机内运行单节点 Kubernetes 集群。 你可以使用 Minikube <del> [在学习环境中尝试 Kubernetes](/zh-cn/docs/setup/learning-environment/). </del> <ins> [在学习环境中尝试 Kubernetes](/zh-cn/docs/setup/learning-environment/)。 </ins>

design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom resources. --> <del> [operator 模式](/zh-cn/docs/concepts/extend-kubernetes/operator/) 是一种系统设计, </del> <ins> [operator 模式](/zh-cn/docs/concepts/extend-kubernetes/operator/) 是一种系统设计， </ins> 将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。 <!--more-->

The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is defined by the states or phases of a Pod. There are five possible Pod phases: Pending, Running, Succeeded, Failed, and Unknown. A high-level description of the Pod state is summarized in the [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` field. --> [Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod <del> 处于哪个阶段的概述。包含了下面 5 种可能的阶段: Running、Pending、Succeeded、 </del> <ins> 处于哪个阶段的概述。包含了下面 5 种可能的阶段：Running、Pending、Succeeded、 </ins> Failed、Unknown。关于 Pod 的阶段的更高级描述请查阅 [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` 字段。
Change:
Hello, I noticed some punctuation errors on page /language zh
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
/retitle Punctuation errors on /remove-kind feature /kind bug

Discussion:
<hr> <del> - **fieldPath** (string), 必需的 </del> <ins> - **fieldPath** (string)，必需的 </ins> 在指定 API 版本中要选择的字段的路径。

<hr> <del> - **resource** (string), 必选 </del> <ins> - **resource** (string)，必选 </ins> <!-- Required: resource to select --> 必选：选择的资源

<hr> <del> - **kind** (string), 必需 </del> <ins> - **kind** (string)，必需 </ins> Kind 是被引用的资源的类型 <del> - **name** (string), 必需 </del> <ins> - **name** (string)，必需 </ins> Name 是被引用的资源的名称
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 (but check with the author, before you do) Make it obvious that your change is an update to an existing article. Hyperlink to Why is this needed PodSecurityPolicy is no longer deprecated; it is actually removed. It helps to amplify that story. Comments /area blog Follows on from
/language en
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
/retitle Update PSP deprecation blog article to link to v1.25 release blog
/assign
Any suggestion from your end?
??
This seems like a good idea. Perhaps add something like this, up at the top of the document?

Discussion:
date: 2021-04-06 slug: podsecuritypolicy-deprecation-past-present-and-future --- **Author:** Tabitha Sable (Kubernetes SIG Security) <ins> {{% pageinfo color="primary" %}} **Update:** *With the release of Kubernetes v1.25, PodSecurityPolicy has been removed.* *You can read more information about the removal of PodSecurityPolicy in the [Kubernetes 1.25 release notes](/blog/2022/08/23/kubernetes-v1-25-release/#pod-security-changes).* {{% /pageinfo %}} </ins> PodSecurityPolicy (PSP) is being deprecated in Kubernetes 1.21, to be released later this week. This starts the countdown to its removal, but doesn’t change anything else. PodSecurityPolicy will continue to be fully functional for several more releases before being removed completely. In the meantime, we are developing a replacement for PSP that covers key use cases more easily and sustainably. What are Pod Security Policies? Why did we need them? Why are they going away, and what’s next? How does this affect you? These key questions come to mind as we prepare to say goodbye to PSP, so let’s walk through them together. We’ll start with an overview of how features get removed from Kubernetes.
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 Markdown error. renders like that, but should be a hyperlink: Proposed Solution: Update the Markdown source Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /help /triage accepted
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: has a Markdown error. renders like that, but should be a hyperlink: Update the Markdown source <!--Kubernetes Version:--/language en /help /triage accepted </details
/assign
/assign

Discussion:
gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled by default to validate custom resource based on _validation rules_. You can disable this feature by explicitly setting the `CustomResourceValidationExpressions` feature gate to `false`, <del> for the `[kube-apiserver](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/)` component. </del> <ins> for the [kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/) component. </ins> This feature is only available if the schema is a [structural schema](#specifying-a-structural-schema).
Change:
Updated with new strings from Didn't remove any strings from , even if they're missing from
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/language hi
Completed.

Discussion:
other = " प्रलेखन अब सक्रिय रूप से मेंटेन नहीं है। वर्तमान में आप जो संस्करण देख रहे हैं वह एक स्टैटिक स्नैपशॉट है। अप-टू-डेट प्रलेखन के लिए, देखें " [deprecation_file_warning] <del> other = "डेप्रिकॉटेड" </del> <ins> other = "डेप्रिकेटेड" [dockershim_message] other = """1.24 संस्करण के बाद से Dockershim को कुबेरनेट्स परियोजना से हटा दिया गया हैं। अधिक जानकारी के लिए <a href="/dockershim">Dockershim रिमूवल एफएक्यू</a> पढ़ें।""" </ins> [docs_label_browse] other = "प्रलेखन ब्राउज़ करें"

[examples_heading] other = "उदाहरण" <ins> [feature_state] other = "फ़ीचर स्थिति:" </ins> [feedback_heading] other = "प्रतिक्रिया"

[input_placeholder_email_address] other = "ईमेल ऐड्रेस" <ins> [javascript_required] other = "इस विषय को देखने के लिए जावास्क्रिप्ट [सक्रिय](https://www.enable-javascript.com/) होना चाहिए।" </ins> [latest_release] other = "नवीनतम रिलीज़:"

other = "उद्देश्य" [options_heading] <del> other = "विकल्प" </del> <ins> other = "विकल्प" [outdated_blog__message] other = "यह लेख एक वर्ष से अधिक पुराना है। पुराने लेखों में पुरानी सामग्री हो सकती है। जाँच करें कि प्रकाशन के बाद से पृष्ठ पर दी गई जानकारी गलत तो नहीं है।" </ins> [post_create_issue] other = "issue बनाएं"

other = "चेतावनी:" [whatsnext_heading] <del> other = "आगे क्या है" </del>  No newline at end of file <ins> other = "आगे क्या है" </ins>
Change:
This is a Bug Report In the file: find two hits: with broken links to 404. /language en
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 en
Below is the correct link for Traces for Kubernetes System Components:
/assign

Discussion:
- `APIResponseCompression`: Compress the API responses for `LIST` or `GET` requests. - `APIServerIdentity`: Assign each API server an ID in a cluster. - `APIServerTracing`: Add support for distributed tracing in the API server. <del> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/traces-for-kubernetes-system-components) for more details. </del> <ins> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details. </ins> - `Accelerators`: Provided an early form of plugin to enable Nvidia GPU support when using Docker Engine; no longer available. See [Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) for

- `KubeletTracing`: Add support for distributed tracing in the kubelet. When enabled, kubelet CRI interface and authenticated http servers are instrumented to generate OpenTelemetry trace spans. <del> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/traces-for-kubernetes-system-components) for more details. </del> <ins> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details. </ins> - `LegacyServiceAccountTokenNoAutoGeneration`: Stop auto-generation of Secret-based [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens). - `LocalStorageCapacityIsolation`: Enable the consumption of
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: Someone reading was not able to discern the intended meaning of the term "isolation class". See . This term is only used twice, and is used in a way that is synonymous with another term already introduced ("priority level"). I think it would be clearer to replace "isolation class" with "priority level". Proposed Solution: Replace "isolation class" with "priority level". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--This has been there for a while. <!--Additional Information:--
/assign
/triage accepted
This is what I originally posted in the #api-priority-and-fairness Slack channel. Thanks for filing this on GitHub, Mike. !

Discussion:
The flow control API involves two kinds of resources. [PriorityLevelConfigurations](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io) <del> define the available isolation classes, the share of the available concurrency </del> <ins> define the available priority levels, the share of the available concurrency </ins> budget that each can handle, and allow for fine-tuning queuing behavior. [FlowSchemas](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#flowschema-v1beta2-flowcontrol-apiserver-k8s-io) are used to classify individual inbound requests, matching each to a

### PriorityLevelConfiguration <del> A PriorityLevelConfiguration represents a single isolation class. Each </del> <ins> A PriorityLevelConfiguration represents a single priority level. Each </ins> PriorityLevelConfiguration has an independent limit on the number of outstanding requests, and limitations on the number of queued requests.
Change:
stay In the page, the link at the text "vSphereVolume CSI " should be -csi-migration
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/language zh
Are you still working on it?
I submitted PR to solve this issue and put you as the co-author.

Discussion:
* Distribute volume: `volumetype: none` For available volume types and administration options, refer to the <del> [Administration Guide](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html). </del> <ins> [Administration Guide](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/). </ins> For further reference information, see [How to configure Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology).

* 'Distribute volume': `volumetype: none` 有关可用的卷类型和管理选项， <del> 请参阅[管理指南](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html)。 </del> <ins> 请参阅[管理指南](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/)。 </ins> 更多相关的参考信息， 请参阅[如何配置 Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology)。

- [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com` - [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume` <del> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#csi-migration-5). </del> <ins> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration). </ins> --> vSphere 存储类有两种制备器

[弃用](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi)。 更多关于 CSI 制备器的详情，请参阅 [Kubernetes vSphere CSI 驱动](https://vsphere-csi-driver.sigs.k8s.io/) <del> 和 [vSphereVolume CSI 迁移](/zh-cn/docs/concepts/storage/volumes/#csi-migration-5)。 </del> <ins> 和 [vSphereVolume CSI 迁移](/zh-cn/docs/concepts/storage/volumes/#vsphere-csi-migration)。 </ins> <!-- #### CSI Provisioner {#vsphere-provisioner-csi}