jiebi/CodeConvo huggingface dataset:
Change:
即使你已经删除了 StatefulSet 和它的全部 Pod，这些 Pod 将会被重新创建并挂载它们的 PersistentVolumes，并且 `web-0` 和 `web-1` 将仍然使用它们的主机名提供服务。 <del> 最后删除 `web` StatefulSet 和 `nginx` service。 </del> <ins> 最后删除 `nginx` service... </ins> ```shell kubectl delete service nginx <ins> ``` ``` </ins> service "nginx" deleted <ins> ``` ... 并且删除 `web` StatefulSet: ```shell </ins> kubectl delete statefulset web <ins> ``` ``` </ins> statefulset "web" deleted ```

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: ! ! 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
/language zh
/kind bug
/assign
Change:
* AzureFile * AzureDisk * FC (Fibre Channel) <ins> * FlexVolume </ins> * Flocker * NFS * iSCSI

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: is inconsistent about whether a persistent volume can be of the FlexVolume type. The table in omits FlexVolume, but the table at the end of the Access Modes subsection in includes FlexVolume. Proposed Solution: Fix the doc to be consistent and correct. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
`kubeadm kubeconfig` provides utilities for managing kubeconfig files. <ins> For examples on how to use `kubeadm kubeconfig user` see [Generating kubeconfig files for additional users](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs#kubeconfig-additional-users). </ins> ## kubeadm kubeconfig {#cmd-kubeconfig} {{< tabs name="tab-kubeconfig" >}}

Discussion:
The command only has Cobra (CLI) documentation and there are no pointers on what fields are relevant in the configuration passed with --config to it: Add a minimal example + config for the command usage on this page: /sig cluster-lifecycle /kind feature xref
/triage accepted
/language en
Change:
If you are running Minikube locally, you can visit hello-world.info from your browser. --> {{< note >}} <del> 如果你在使用本地 Minikube 环境，你可以从浏览器中访问 hellow-world.info。 </del> <ins> 如果你在使用本地 Minikube 环境，你可以从浏览器中访问 hello-world.info。 </ins> {{< /note >}} <!--

Discussion:
Ingress Ingress Minikube hellow- hellow- typohellow
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:
Alibaba Cloud | https://www.alibabacloud.com/trust-center | Amazon Web Services | https://aws.amazon.com/security | Google Cloud Platform | https://cloud.google.com/security | <del> Huawei Cloud | https://www.huaweicloud.com/securecenter/overallsafety | </del> <ins> Huawei Cloud | https://www.huaweicloud.com/intl/en-us/securecenter/overallsafety | </ins> IBM Cloud | https://www.ibm.com/cloud/security | Microsoft Azure | https://docs.microsoft.com/en-us/azure/security/azure-security | Oracle Cloud Infrastructure | https://www.oracle.com/security |

Discussion:
<brConsider using the English-language version of the link for Huawei Cloud: The current link is Chinese.
Page related to issue: /language en
/assign
/kind bug /good-first-issue /triage accepted
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 : /kind bug /good-first-issue /triage accepted 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
Anyone is welcome to work on this. it sounds like you plan to open a pull request? (other contributors: it's polite to try to liaise with ahead of starting work)
, yes i would like to work on this and going to open a pull request.
/assign
Hey Please assign this issue to me, I am a new contributor
Anyone is welcome to work on this. (it's polite to try to liaise with contributors who've previously expressed an interest in working on this, and ideally to consider collaborating)
, Kindly next time liaise with previous assigned user first before you assign youself and start work. This will show some courtesy.
Change:
## Objectives * Configure an example deployment to run Windows containers on the Windows node <del> * Highlight Windows specific funcationality in Kubernetes </del> <ins> * Highlight Windows specific functionality in Kubernetes </ins> ## Before you begin

Discussion:
The spelling of the functionality i.e funcationality is wrong, I'm attaching the screenshot for the same. May I open a new PR correcting the spelling? !
Hi you can raise a PR for that but also make sure to check for other errors on that same doc, also you can provide a link to that error instead of attaching a screenshot. /language en
Hey I was working on this issue but has made a PR, I have given a lot of o time to finding the bug and she has raised a PR, Is it not wrong?
Hey I did not check the comments here, you can Raise a PR if you want. I can close it. The issue was clear from the PR description. Let me know if you want me to close it. It wasn't assigned to anyone.
Hey Yes please close your PR, I had given time to find the bug. I'll be grateful to you.
Hi thanks for your response also you can review the previous comments made on any issues and check if there is someone who already mentioned that they want to work on it and if you want to work on it you can ask the author of the issue.
Yeah sure, I will close the PR. Not an issue. Thanks!!
/triage accepted /assign
(nit) /retitle Typo on Guide for scheduling Windows containers in Kubernetes page
Change:
font-size: 0.7em !important; } }  No newline at end of file

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: (Despite the PR has been merged, it seems that the error still exists. So opening an issue here. ) From the PR : [As-is] ! ! [To-be] ! ! Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--CC /area web-development
/triage accepted
Hello Thanks for reporting this issue. May i kindly know some more details to reproduce the issue. 1) Browser & Version ? 2) Resolution of your display ? I'm trying to reproduce it on wide viewport !
Hello Here is the info of my env: Windows 10 Enterprise 20H2 Google Chrome 97.0.4692.99 (64bit) Monitor resolution: 3840 1600 Chrome window size: [1868 1592] ! [1868 1592] [3767 1600] ! [3767 * 1600]
I can replicate this with Chromium and with Firefox.
/priority backlog
Thanks for the information. Please can you assign this issue to me.
try this Prow command: /assign ravikiranr26 (reply in a comment with that command on a line by itself)
/assign ravikiranr26
Change:
- PRはページ名、slug/alias、アンカーリンクの変更や削除をしていますか？ その場合、このPRの変更の結果、リンク切れは発生しませんか？ ページ名を変更してslugはそのままにするなど、他の選択肢はありませんか？ - PRは新しいページを作成するものですか？ その場合、次の点に注意してください。 - ページは正しい[page content type](/docs/contribute/style/page-content-types/)と関係するHugoのshortcodeを使用していますか？ <del> - セクションの横のナビゲーション(または全体)にページは正しく表示されますか？ </del> <ins> - セクションの横のナビゲーションにページは正しく表示されますか(または表示されませんか)？ </ins> - ページは[Docs Home](/docs/home/)に一覧されますか？ - Netlifyのプレビューで変更は確認できますか？ 特にリスト、コードブロック、テーブル、備考、画像などに注意してください。 ### その他 <del> PRに関して誤字や空白などの小さな問題を指摘する場合は、コメントの前に`nit:`と書いてください。こうすることで、PRの作者は問題が深刻なものではないことが分かります。 </del> <ins> - [些細な編集](https://www.kubernetes.dev/docs/guide/pull-requests/#trivial-edits)に注意してください。些細な編集だと思われる変更を見つけた場合は、そのポリシーを指摘してください (それが本当に改善である場合は、変更を受け入れても問題ありません)。 - 空白の修正を行っている作成者には、PRの最初のコミットでそれを行い、その後に他の変更を加えるよう促してください。これにより、マージとレビューの両方が容易になります。特に、大量の空白文字の整理と共に1回のコミットで発生する些細な変更に注意してください(もしそれを見つけたら、作成者に修正を促してください)。 レビュアーが誤字や不適切な空白など、PRの本質でない小さな問題を発見した場合は、コメントの先頭に`nit:`を付けてください。これにより、作成者はこのフィードバックが重要でないことを知ることができます。 Pull Requestの承認を検討する際、残りのすべてのフィードバックがnitとしてマークされていれば、残っていたとしてもPRをマージできます。その場合、残っているnitに関するIssueをオープンすると役立つことがよくあります。その新しいIssueを[Good First Issue](https://www.kubernetes.dev/docs/guide/help-wanted/#good-first-issue)としてマークするための条件を満たすことができるかどうか検討してください。それができたら、これらは良い情報源になります。 </ins>

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. It contains important information for contributors. Comments /language ja /assign
/triage accepted
Change:
{{< note >}} To learn more about contributing to Kubernetes in general, see the [contributor documentation](https://www.kubernetes.dev/docs/). <ins> You can also read the {{< glossary_tooltip text="CNCF" term_id="cncf" >}} [page](https://contribute.cncf.io/contributors/projects/#kubernetes) about contributing to Kubernetes. </ins> {{< /note >}} <ins> --- </ins> This website is maintained by [Kubernetes SIG Docs](/docs/contribute/#get-involved-with-sig-docs). Kubernetes documentation contributors:

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 so that early in the page there is a link to You should decide on some suitable text for the hyperlink. Read to get ideas about what to write, if you're not sure. :information_source: Don't remove any of the existing links; this is an addition. Why is this needed This change will help signpost readers to the CNCF contributor site. Comments /kind feature /language en /triage accepted /priority backlog Exceptionally, due to a previous issue where different folks claimed to work on this, I will assign this to myself and work on it.
(please don't assign this issue to yourself unless your GitHub username is /assign
Change:
--certificate-identity krel-staging@k8s-releng-prod.iam.gserviceaccount.com  --certificate-oidc-issuer https://accounts.google.com  "$VERSION.spdx" <del> ``` </del>  No newline at end of file <ins> ``` </ins>

Discussion:
in this page the link about Verify Signed Kubernetes Artifacts for install cosign changed --- !
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
It is a documentation issue, Docs issues are implemented in . Please open in this repo.
/transfer website
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig doc 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
/kind bug /kind documentation
Change:
| Docker Engine (使用 cri-dockerd)  | `unix:///var/run/cri-dockerd.sock`           | {{< /table >}} <del> <!-- </del> <ins> {{% /tab %}} </ins> {{% tab name="Windows" %}} <del> {{< table >}} </del> <ins> <!-- </ins> | Runtime                            | Path to Windows named pipe                   | |------------------------------------|----------------------------------------------| | containerd                         | `npipe:////./pipe/containerd-containerd`     | | Docker Engine (using cri-dockerd)  | `npipe:////./pipe/cri-dockerd`               | <del> {{< /table >}} </del> --> <del> {{% tab name="Windows" %}} </del> {{< table >}} | 运行时                              |  Windows 命名管道路径                         |

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
1. Download the latest release with the command: ```powershell <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe </del> <ins> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe" </ins> ``` 1. Validate the binary (optional)

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:
EOF apt-get update # Install docker if you don't have it already. <del> apt-get install -y docker.io </del> <ins> apt-get install -y docker-engine </ins> apt-get install -y kubelet kubeadm kubectl kubernetes-cni ```

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: On Ubuntu in addition to installing Docker one need to install package "aufs-tools" as dockerd may call aufs tools like "auplink" up on need. This may be relevant for Docker on CentOS 7 too, I do not know with certainty. Proposed Solution: Replace line apt-get install -y with the line apt-get install -y aufs-tools Page to Update: Kubernetes Version: Kubernetes 1.5.1 Additional Information: Ubuntu 16.10
The root problem may be a missing dependency in the docker package on Ubuntu and derivatives. But needs to be addressed for kubeadm until it is resolved up stream by OS vendor.
cc:
Change:
secret "prod-db-secret" created ``` <ins> You can also create a secret for test environment credentials. </ins> ```shell kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests ```

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: Line 355: There is no description before the code. Line 1005: There is no description before the code. Proposed Solution: Line 355: You can view a description of the secret: Line 1005: You can also create a secret for test environment credentials. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
<p>If you haven't worked through the earlier sections, start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">Using minikube to create a cluster</a>.</p> <p><em>Scaling</em> is accomplished by changing the number of replicas in a Deployment</p> <del> <p> <b> NOTE </b> If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, you may need to start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">creating a cluster</a> as the services may have been deleted </p> </del> <ins> {{< note >}} <p>If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section</a>, you may have deleted the Service exposing the Deployment. In that case, please expose the Deployment again using the following command:</p><p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080</b></code></p> {{< /note >}} </ins> </div> <div class="col-md-4"> <div class="content__box content__box_lined">

Discussion:
Hello I found an inconsistency in the Kubernetes Tutorial. When following the steps for exposing an app it deletes the service in the end. When following up on the next page: "Once you're ready, move on to ." There seems to be the expectancy of an existing service, which got deleted in the previous steps. Step 3: Deleting a service: You deleted the service associated with the deployment. Following step: Load Balancing: The tutorial then expects you to use the deleted service to check load balancing, which is not possible. The $NODE_PORT variable is set using the deleted service. First the service should be re-created. Kind regards. Daisy
Page reported in issue: /language en
/retitle Tutorial Inconsistency: Deletion of service in "Using a Service to Expose Your App" hinders progression in "Running Multiple Instances of Your App" tutorial
the documentation does mention a note at the start of the page NOTE If you are trying this after , you may need to start from as the services may have been deleted Would adding more emphasis to this note address your request?
Modifying the note accordingly would help to address the issue.
/triage accepted Fixes are welcome
/assign I will submit a PR.
I won't say the documentation is wrong here, but things can be improved /kind feature
/priority backlog
My mistake, apologies. The note is actually pretty clear like mentioned. Perhaps a small modification to make the instruction more clear would be enough. Thankyou. NOTE If you are trying this after , you may need to start from as the services may have been deleted
Change:
```shell sudo apt-get install cri-o-1.17 ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> <del> {{< tab name="Ubuntu 18.04, 19.04 and 19.10" >}} </del> <ins> {{% tab name="Ubuntu 18.04, 19.04 and 19.10" %}} </ins> ```shell #  패키지 리포지터리 설정

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: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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
Hey folks, I'm happy to help you with this /assign
Change:
an existing StorageClass that is marked as default. This default StorageClass is then used to dynamically provision storage for PersistentVolumeClaims that do not require any specific storage class. See <del> [PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#class-1) </del> <ins> [PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) </ins> for details. The pre-installed default StorageClass may not fit well with your expected workload;

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 "prerequisites" %}} <del> {{% version-check %}} This task also assumes that you have met the following prerequisites: </del> <ins> This task assumes that you have met the following prerequisites: </ins> 1. You do not require your applications to be highly available during the node drain, or 1. You have read about the [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) concept,

Discussion:
The PR improperly set the minim version to 1.5 when there is no such version. Public link: Markdown file: ! !
/assign
kubernetes 1.5 release end of life (1 October 2017) already passed so this page needs updation
/kind bug
I guess it is mentioned because in v1.5: As per release It totally depends upon the docs and /sig node what they want to mention. If it is mentioned because of the time this feature went beta this page might be right.
/retitle “Safely Drain a Node” states that you need Kubernetes 1.5 or later /language en That statement is correct and its inclusion does not, to me, feel misleading. /priority awaiting-more-evidence
Just to confirm the version indicates the complete functionality is not available until v1.5 is released? PDB is . Only confusing area is what functionality in the document is for 1.5 and what is available now?
Try this: The page does not say you need to wait for an upcoming release. I think you have misunderstood what is actually a clear statement We could drop the shortcode as we assume everyone is using Kubernetes 1.21 or later.
/triage accepted Drop the version-check would be desireable.
/priority important-longterm
For SIG Docs, this is only a backlog priority I think. We've other work that we'd want to prioritize. Help here is still very welcome!