jiebi/CodeConvo huggingface dataset:
Change:
{{% tab name="Linux" %}} <!-- <del> {{< table >}} </del> | Runtime                            | Path to Unix domain socket                   | |------------------------------------|----------------------------------------------| | containerd                         | `unix:///var/run/containerd/containerd.sock` | | CRI-O                              | `unix:///var/run/crio/crio.sock`             | | Docker Engine (using cri-dockerd)  | `unix:///var/run/cri-dockerd.sock`           | <del> {{< /table >}} </del> --> {{< table >}} | 运行时                              | Unix 域套接字                                     |

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/). <del> It is enabled by default. </del> When enabled, the control plane tracks new Jobs using the behavior described below. Jobs created before the feature was enabled are unaffected. As a user,

Discussion:
Update , job-tracking-with-finalizers section, as k/k PR is disabling by default due to an unresolved bug.
Specifically the note () says that "it is enabled by default."
this feature is currently enabled by default in v1.23 and will be disabled in v1.24, right?
/sig apps /language en
I also proposed to disable it by default in 1.23 , but the release managers haven't approved it yet.
/triage accepted /sig apps
/assign
Thanks
Change:
- `nodefs.available<10%` - `imagefs.available<15%` - `nodefs.inodesFree<5%` (Linux nodes) <ins> - `imagefs.inodesFree<5%` (Linux nodes) </ins> These default values of hard eviction thresholds will only be set if none of the parameters is changed. If you changed the value of any parameter,

Discussion:
This is a Feature Request As this is merged now, the EvictionHard docs should be updated to include imagefs.inodesFree What would you like to be Adding default settings of imagefs.inodesFree in Page to update: Why is this needed If the user is using separate filesystem for images, it helps to monitor disk pressure if inodes run out on the ImageFs.
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
/sig node /language en
/assign
/retitle Document default settings for in EvictionHard
This issue is fixed by the PR and hence we can close this one
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
env: - name: DEMO_GREETING value: "Hello from the environment" <ins> - name: DEMO_FAREWELL value: "Such a sweet sorrow" </ins>

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: Documentation example for environment variables only shows one variable, so it is not clear to users how to add a second or subsequent variables Proposed Solution: Add a second variable to the example. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
<!-- In Kubernetes, _namespaces_ provides a mechanism for isolating groups of resources within a single cluster. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced objects _(e.g. Deployments, Services, etc)_ and not for cluster-wide objects _(e.g. StorageClass, Nodes, PersistentVolumes, etc)_. --> <del> 在 Kubernetes 中，**名字空间（Namespace）**提供一种机制，将同一集群中的资源划分为相互隔离的组。 </del> <ins> 在 Kubernetes 中，**名字空间（Namespace）** 提供一种机制，将同一集群中的资源划分为相互隔离的组。 </ins> 同一名字空间内的资源名称要唯一，但跨名字空间时没有这个要求。 名字空间作用域仅针对带有名字空间的对象，例如 Deployment、Service 等， 这种作用域对集群访问的对象不适用，例如 StorageClass、Node、PersistentVolume 等。

Discussion:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace
Change:
{{< tabs name="kubectl_retainkeys2_example" >}} {{{< tab name="Bash" codelang="bash" >}} <del> kubectl patch deployment retainkeys-demo --patch "$(cat patch-file-retainkeys.yaml)" </del> <ins> kubectl patch deployment retainkeys-demo --type merge --patch "$(cat patch-file-retainkeys.yaml)" </ins> {{< /tab >}} {{< tab name="PowerShell" codelang="posh" >}} <del> kubectl patch deployment retainkeys-demo --patch $(Get-Content patch-file-retainkeys.yaml -Raw) </del> <ins> kubectl patch deployment retainkeys-demo --type merge --patch $(Get-Content patch-file-retainkeys.yaml -Raw) </ins> {{< /tab >}}} {{< /tabs >}}

Discussion:
example commands are missing Resulting in: I will prepare a patch for this.
/triage accepted /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 : /triage accepted /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
Change:
Administrators can specify a default StorageClass just for PVCs that don't request any particular class to bind to: see the <del> [PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#class-1) </del> <ins> [PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) </ins> for details. ```yaml

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The following documents contain the broken link which points to the wrong section name: concepts/storage/storage-[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#class-1) tasks/administer-cluster/change-default-storage-[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#class-1) Proposed Solution: Fix the wrong section name as the below: concepts/storage/storage-[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) tasks/administer-cluster/change-default-storage-[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
/kind bug
Change:
## {{% heading "whatsnext" %}} <del> * [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) </del> <ins> * [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) </ins>  No newline at end of file

Discussion:
This is a Bug Report Problem: The versions of the cri-tools and cni-plugins dependencies was updated in packages, but not in the documentation: Proposed Solution: Update the versions, to match what is in the deb/rpm packages. Currently they are not pinned, but installs the latest: Compared with the deb installation: Page to Update: Kubernetes Version: 27.0 <!--Additional Information:--Related:
/sig cluster-lifecycle /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 : /sig cluster-lifecycle /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
/triage accepted /priority backlog
/assign
/unassign
Change:
OpenStack Heat       | Saltstack    | CentOS | Neutron + flannel hostgw | [docs](/docs/getting-started-guides/openstack-heat)            |  Community ([@FujitsuEnablingSoftwareTechnologyGmbH](https://github.com/FujitsuEnablingSoftwareTechnologyGmbH)) Rackspace            | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/rackspace)                              |  Community ([@doublerr](https://github.com/doublerr)) any                  | any          | any    | any         | [docs](/docs/getting-started-guides/scratch)                                |  Community ([@erictune](https://github.com/erictune)) <ins> any                  | any          | any    | any         | [docs](http://docs.projectcalico.org/v2.2/getting-started/kubernetes/installation/)                                |  Commercial and Community </ins> **Note**: The above table is ordered by version test/used in nodes, followed by support level.

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The Table of Solutions should mention Calico with a pointer into the Calico docs. Probably with one pretty general row. Proposed Solution: Add one row with IaaS-Provider=any, Config-Mgmt=any, OS=any, Networking=any, , Support=Commercial and Community Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
CC
should we close this ?
Yeah, it looks resolved.
Change:
object to make actual Pods. The `PodTemplate` is part of the desired state of whatever workload resource you used to run your app. <ins> When you create a Pod, you can include [environment variables](/docs/tasks/inject-data-application/define-environment-variable-container/) in the Pod template for the containers that run in the Pod. </ins> The sample below is a manifest for a simple Job with a `template` that starts one container. The container in that Pod prints a message then pauses.

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 In , briefly mention that you can set environment variables for containers in Pods, and link to our pages about that. No need to add an explanation; this is about helping people discover the feature. Why is this needed This is about helping people discover the feature. Comments /sig node /language en
Relevant to
Potential improvement, worth doing. /priority backlog /triage accepted
I would like to assist in resolving this issue. Thanks! /assign
PRs are welcome!
Change:
A node is eligible for exclusion if labelled with "`node.kubernetes.io/exclude-from-external-load-balancers`". - `ServiceTopology`: Enable service to route traffic based upon the Node topology of the cluster. <del> See [ServiceTopology](/docs/concepts/services-networking/service-topology/) for more details. </del> - `SetHostnameAsFQDN`: Enable the ability of setting Fully Qualified Domain Name(FQDN) as the hostname of a pod. See

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: Topology-aware traffic routing with topology keys is deprecated since 1.21 Confirm if it's removed and remove the related documentation if feature is removed Proposed Solution: Remove Service Topology page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Deprecated since 1.21 <!--Additional Information:--
/kind cleanup /language en
I can look into this. /assign
/sign network /triage accepted /priority important-longterm
Thanks
Change:
nohup.out # Hugo output <del> public/ resources/ </del> <ins> /public/ /resources/ </ins> .hugo_build.lock # Netlify Functions build output package-lock.json <del> functions/ node_modules/ </del> <ins> /functions/ /node_modules/ </ins> # Generated files when building with make container-build .config/

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 Update the to only ignore the directories and at the top level of the repository. Why is this needed If somebody wants to create a content directory named , that ignore will conflict. We should tidy it so it wouldn't. Comments /kind cleanup Docs for : https://git-
Can you assign it to me..??
/assign
/triage accepted
/priority backlog
Change:
is running the Redis server. With this connection in place you can use your local workstation to debug the database that is running in the pod. <ins> **Warning**: Due to known limitations, port forward today only works for TCP protocol. The support to UDP protocol is being tracked in [issue 47862](https://github.com/kubernetes/kubernetes/issues/47862). {: .warning} </ins> {% endcapture %}

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This works only for TCP ports, documentation should mention it. Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
Or if you have `curl` installed, use this command: ```powershell <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe" </ins> ``` {{< note >}}

Discussion:
Very basic step "Install kubectl binary with curl on Windows" Response seems good: But .exe is actually XML, giving download error: Hard to realize and quite unfriendly! Thanks
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
/kind bug There are multiple broken links on this page. It seems the links on this page is missing the version from it
/assign
Change:
<ins> apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-approver rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - get - list - watch - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests/approval verbs: - update - apiGroups: - certificates.k8s.io resources: - signers resourceNames: - example.com/my-signer-name # example.com/* can be used to authorize for all signers in the 'example.com' domain verbs: - approve </ins>

Discussion:
/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
Change:
[build] # This default build command adds the robots noindex directive to the site headers. # It is turned off for only for the production site by using [context.master] below <del> # DO NOT REMOVE THIS (contact @chenopis or @sig-docs-maintainers) </del> <ins> # DO NOT REMOVE THIS (contact @kubernetes/sig-docs-leads) </ins> publish = "public" functions = "functions" command = "make non-production-build"

Discussion:
The  group in OWNERSALIASES is a historical artifact with no permissions associated with it. Remove the team from OWNERS_ALIASES. I'm also proposing to update the description of from "Website admins" to "Website chairs and tech leads" and add and to the group. For more information, see We need to update the to replace with I propose continuing to limit repo admin access to current chairs. /assign
Change:
* 如果你正在使用 `hack/local-up-cluster.sh`，请确保设置了 `KUBE_ENABLE_CLUSTER_DNS` 环境变量，然后运行安装脚本。 * [安装和设置 v1.7 或更高版本的 kubectl](/zh/docs/tasks/tools/install-kubectl/)，确保将其配置为连接到 Kubernetes 集群。 * 安装 v2.7.0 或更高版本的 [Helm](https://helm.sh/)。 <del> * 遵照 [Helm 安装说明](https://github.com/kubernetes/helm/blob/master/docs/install.md)。 </del> <ins> * 遵照 [Helm 安装说明](https://helm.sh/docs/intro/install/)。 </ins> * 如果已经安装了适当版本的 Helm，请执行 `helm init` 来安装 Helm 的服务器端组件 Tiller。 <!-- steps -->

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: Helm install URL is Wrong ! Proposed Solution: Change it to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language zh /assign
Change:
reviewers: - thockin - bowei <del> content_type: concept </del> <ins> content_type: task </ins> title: Debug Services weight: 20 ---

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: In , is broken. Proposed Solution: In , Page to Update: Problem: The of these pages is , but it seems that it should be . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
GitHub didn't allow me to assign the following users: PrajwalBorkar. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
already opened 4 days before this issue filed, please take a look.
/assign
Hey are you trying to help with this issue? There is already another PR done this, please take a look at above comments.
The first part is solved by . Sorry for missed the second part of this issue about wrong . Hey would you still like to give a try?
Change:
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).

Discussion:
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
Change:
<del> <section id="katacoda-removal-warning"> <div class="content warning pageinfo pageinfo-warning"> <p> {{ T "katacoda_removal_warning" | markdownify }} </p> </div> </section> </del>

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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted