jiebi/CodeConvo huggingface dataset:
Change:
[1]: https://docs.mesosphere.com/latest/usage/service-guides/hdfs/ [2]: https://docs.mesosphere.com/latest/usage/service-guides/spark/ <del> [3]: https://docs.mesosphere.com/latest/usage/service-guides/chronos/ </del> <ins> [3]: https://mesos.github.io/chronos/docs/getting-started.html </ins> [4]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md [5]: https://dcos.io/docs/latest/administration/installing/cloud/gce/ [6]: http://mesos.apache.org/

Discussion:
I wrote a crawl to fetch all the invalid herf in website: This is my Run this command: go run Then we can find some invalid herf. I fixes part of them: But I found that there are so many invalid herf. (part of them) I opened this issue to trace the invalid herf.
may have interest to this issue.
Thanks , We have a similar tool, right? . This would be a good supplement.
We do have a tool, but it might be good to also have a published script that anyone else can run too.
Change:
### LIST and WATCH filtering <del> LIST and WATCH operations may specify label selectors to filter the sets of objects returned using a query parameter. Both requirements are permitted </del> <ins> For **list** and **watch** operations, you can specify label selectors to filter the sets of objects returned; you specify the filter using a query parameter. (To learn in detail about watches in Kubernetes, read [efficient detection of changes](/docs/reference/using-api/api-concepts/#efficient-detection-of-changes)). Both requirements are permitted </ins> (presented here as they would appear in a URL query string): * _equality-based_ requirements: `?labelSelector=environment%3Dproduction,tier%3Dfrontend`

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 include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.
Change:
ifconfig docker0 down yum -y -q install bridge-utils && brctl delbr docker0 && service docker restart ;; <del> centos) </del> <ins> centos|fedora) </ins> DOCKER_CONF="/etc/sysconfig/docker" sed -i "/^OPTIONS=/ s|( --mtu=.*)?'$| --mtu=${FLANNEL_MTU} --bip=${FLANNEL_SUBNET}'|" ${DOCKER_CONF} if ! command_exists ifconfig; then

Discussion:
In there is initial check for but then it is not put in checks. I mean there are checks like but then in consecutive code there are things like following where is not mentioned.
Change:
`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}

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:
- `ServiceLoadBalancerFinalizer`: Enable finalizer protection for Service load balancers. - `ServiceNodeExclusion`: Enable the exclusion of nodes from load balancers created by a cloud provider. A node is eligible for exclusion if labelled with "`alpha.service-controller.kubernetes.io/exclude-balancer`" key or `node.kubernetes.io/exclude-from-external-load-balancers`. <del> - `ServiceTopology`: Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology](https://kubernetes.io/docs/concepts/services-networking/service-topology/) for more details. </del> <ins> - `ServiceTopology`: Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology](/docs/concepts/services-networking/service-topology/) for more details. </ins> - `StartupProbe`: Enable the [startup](/docs/concepts/workloads/pods/pod-lifecycle/#when-should-you-use-a-startup-probe) probe in the kubelet. - `StorageObjectInUseProtection`: Postpone the deletion of PersistentVolume or PersistentVolumeClaim objects if they are still being used.

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: link At 435 line: See [Support Device Monitoring]() for more details. from link At 479 line: - : Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology]() for more details. Proposed Solution: with correct link from link /docs/concepts/services-networking/service-topology/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
--> `StorageObjectInUseProtection` 插件将 `kubernetes.io/pvc-protection` 或 `kubernetes.io/pv-protection` finalizers 添加到新创建的持久化卷声明（PVC）或持久化卷（PV）中。 如果用户尝试删除 PVC/PV，除非 PVC/PV 的保护控制器移除 finalizers，否则 PVC/PV 不会被删除。有关更多详细信息，请参考[保护使用中的存储对象](/docs/concepts/storage/persistent-volumes/#storage-object-in-use-protection)。 <del> ### TaintNodesByCondition {#taintnodesbycondition} {{< feature-state for_k8s_version="v1.12" state="beta" >}} </del> <ins> ### TaintNodesByCondition {#taintnodesbycondition} {{< feature-state for_k8s_version="v1.12" state="beta" >}} </ins> <!-- This admission controller {{< glossary_tooltip text="taints" term_id="taint" >}} newly created Nodes as `NotReady` and `NoSchedule`. That tainting avoids a race condition that could cause Pods to be scheduled on new Nodes before their taints were updated to accurately reflect their reported conditions.

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
when localizing, that's even better. {{< /comment >}} <del> The CNCF [white paper](https://github.com/cncf/tag-security/tree/main/security-whitepaper) </del> <ins> The CNCF [white paper](https://github.com/cncf/tag-security/blob/main/community/resources/security-whitepaper/v2/CNCF_cloud-native-security-whitepaper-May2022-v2.pdf) </ins> on cloud native security defines security controls and practices that are appropriate to different _lifecycle phases_.

Discussion:
The CNCF on cloud native security defines security controls and practices that are appropriate to different lifecycle phases 404 link
/language en
/assign
/retitle Broken link to CNCF white paper in "Cloud Native Security" page /kind bug Page reported in issue (based on initial title):
/priority backlog /triage accepted
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: with-affinity-anti-affinity spec: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/os operator: In values: - linux preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference: matchExpressions: - key: label-1 operator: In values: - key-1 - weight: 50 preference: matchExpressions: - key: label-2 operator: In values: - key-2 containers: - name: with-node-affinity image: registry.k8s.io/pause:2.0 </ins>  No newline at end of file

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
the slightly simpler syntax: ```shell <del> kubectl port-forward deployment/redis-master :6379 </del> <ins> kubectl port-forward deployment/mongo :27017 ``` The output is similar to this: ``` Forwarding from 127.0.0.1:63753 -> 27017 Forwarding from [::1]:63753 -> 27017 </ins> ``` The `kubectl` tool finds a local port number that is not in use (avoiding low ports numbers, because these might be used by other applications). The output is similar to: ``` <del> Forwarding from 127.0.0.1:62162 -> 6379 Forwarding from [::1]:62162 -> 6379 </del> <ins> Forwarding from 127.0.0.1:63753 -> 27017 Forwarding from [::1]:63753 -> 27017 </ins> ```

Discussion:
uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /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 /kind bug /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
/remove-triage needs-information
/assign
Change:
- 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>

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 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
Change:
### Linux ```shell <del> export KUBECONFIG=$KUBECONFIG:$HOME/.kube/config </del> <ins> export KUBECONFIG="${KUBECONFIG}:${HOME}/.kube/config" </ins> ``` ### Windows Powershell

Discussion:
Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:
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
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]:
Thanks for reporting, I can open a PR to fix this! /remove-lifecycle stale /assign
Change:
{{ end }} <div class="td-outer"> <main role="main" class="td-main"> <del> <section class="row td-search-result"> <div class="col-12 col-md-4 offset-md-2"> <form class="td-sidebar__search d-flex align-items-center"> {{ partial "search-input.html" . }} <button class="btn btn-link td-sidebar__toggle d-md-none p-0 ml-3 fas fa-bars" type="button" data-toggle="collapse" data-target="#td-section-nav" aria-controls="td-docs-nav" aria-expanded="false" aria-label="Toggle section navigation"> </button> </form> </div> <div class="col-12 col-md-8 offset-md-2"> <h2 class="ml-4">{{ .Title }}</h2> {{ if .Site.Params.gcs_engine_id }} <script> (function() { var cx = '{{ . }}'; var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true; gcse.src = 'https://cse.google.com/cse.js?cx=' + cx; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s); })(); </script> <gcse:searchresults-only></gcse:searchresults-only> {{ else if .Site.Params.k8s_search }} <script src="{{ "js/search.js" | relURL }}"></script> <gcse:searchresults-only linktarget="_parent"> <div id="bing-results-container">{{ T "layouts_docs_search_fetching" }}</div> <div id="bing-pagination-container"></div> </gcse:searchresults-only> {{ end }} </div> </section> </del> <ins> <section class="row td-search-result"> <div class="col-12 col-md-4 offset-md-2"> <form class="td-sidebar__search d-flex align-items-center"> {{ partial "search-input.html" . }} </form> </div> <div class="col-12 col-md-8 offset-md-2"> <h2 class="ml-4">{{ .Title }}</h2> {{ if .Site.Params.gcs_engine_id }} <script> (function() { var cx = '{{ . }}'; var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true; gcse.src = 'https://cse.google.com/cse.js?cx=' + cx; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s); })(); </script> <gcse:searchresults-only></gcse:searchresults-only> {{ else if .Site.Params.k8s_search }} <script src="{{ "js/search.js" | relURL }}"></script> <gcse:searchresults-only linktarget="_parent"> <div id="bing-results-container">{{ T "layouts_docs_search_fetching" }}</div> <div id="bing-pagination-container"></div> </gcse:searchresults-only> {{ end }} </div> </section> </ins> </main> {{ partial "footer.html" . }} </div>

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: Navbar prevents search input field from being clicked on Can reproduce on Firefox, Chrome on latest builds Proposed Solution: Remove navbar from search page Page to Update: !
is not supposed to look like that screenshot /kind bug /priority critical-urgent /area web-development Thanks for reporting this.
/triage accepted
/retitle Navbar prevents search inputfield from being clicked
Actually /retitle Search page rendering incorrectly
Change:
38s        37s        2    {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}                Warning        FailedSync    Error syncing pod, skipping: failed to "StartContainer" for "main" with RunContainerError: "PostStart handler: Error executing in Docker Container: 1" 1m         22s         2     {kubelet gke-test-cluster-default-pool-a07e5d30-siqd}    spec.containers{main}    Warning        FailedPostStartHook ``` <ins> ## What's Next - See an example of [using container lifecycle hooks](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/) </ins>

Discussion:
It's a nice description of what hooks are and options the user has. But where to configure it? How about an example?
you can find examples of container lifecycle hooks here: I am afraid it is currently a bit hard to find. Thanks for reporting. We should add a link to this /task from the /concept.
That's awesome, thanks a lot!
Change:
description: > Learn about ServiceAccount objects in Kubernetes. content_type: concept <del> weight: 10 </del> <ins> weight: 25 </ins> --- <!-- overview -->

Discussion:
This is a Refactor request <!-- 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 overview page at is a bit out of date: no reference to I'm not convinced that the “Four Cs of cloud native security” model is useful for readers to learn Does not align with other CNCF documents, such as Proposed Solution: Either: remove outright migrate content from into several destinations (keep this brief but on-point) &hellip;and then redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig docs /sig security /language en
If we keep the link to then we should update it to be as this is the English docs.
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 /triage accepted
Also see
/assign
I'd appreciate a (fresh) review on .
Change:
<ins> apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-signer rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - get - list - watch - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests/status verbs: - update - apiGroups: - certificates.k8s.io resources: - signers resourceName: - example.com/my-signer-name # example.com/* can be used to authorize for all signers in the 'example.com' domain verbs: - sign </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:
<!-- overview --> <img src="https://raw.githubusercontent.com/kubernetes/kubeadm/master/logos/stacked/color/kubeadm-stacked-color.png" align="right" width="150px">This page shows how to install the `kubeadm` toolbox. <del> For information how to create a cluster with kubeadm once you have performed this installation process, see the [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) page. </del> <ins> For information on how to create a cluster with kubeadm once you have performed this installation process, see the [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) page. </ins>

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 statement seems grammatically incorrect due to missing "on" after "information". Proposed Solution: -Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--/language en /good-first-issue <!--Kubernetes Version:--<!--Additional Information:--
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 Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The statement seems grammatically incorrect due to missing "on" after "information". /language en /good-first-issue <!--Kubernetes Version:--</details
/assign
/sig cluster-lifecycle /triage accepted