jiebi/CodeConvo huggingface dataset:
Change:
The response to a successful request is a hello message: <del> Hello Kubernetes! </del> <ins> ```shell Hello Kubernetes! ``` </ins> ## {{% heading "cleanup" %}} To delete the Service, enter this command: <del> kubectl delete services my-service </del> <ins> ```shell kubectl delete services my-service ``` </ins> To delete the Deployment, the ReplicaSet, and the Pods that are running the Hello World application, enter this command: <del> kubectl delete deployment hello-world </del> <ins> ```shell kubectl delete deployment hello-world ``` </ins> ## {{% heading "whatsnext" %}} Learn more about [connecting applications with services](/docs/concepts/services-networking/connect-applications-service/).

Discussion:
This is a Bug Report There are some commands in the tutorial that are missing code formatting. This is a request to update those commands and remove any extra lines in the page. <!--Required Information--Problem: The tutorial has commands that are not formatted as code. For example, kubectl get deployments hello-world Add code formatting: Proposed Solution: Identify the commands that are missing code formatting. Add the code formatting to the commands. Clean up any extra lines in the page. Page to Update: This is a good issue for a first time contributor. If you need more information, feel free to ask in this issue. It is a good idea to build your changes locally.
/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
/triage accepted /language en Thanks - another good spot
Is this PR currently being worked on?
it seems already formatted, right?
I don't see any issues with the page as well, and it looks like it was last modified July 27, 2020 at 4:18. Are we missing something?
Let me look. I'd like a first time contributor to work on this issue.
The page renders correctly, however, it would be helpful to clean up the formatting of the page such as extra lines and spaces. Also, the page should use code blocks around any commands (instead of indentation). Let me know if you need more information. Thanks!
i'm a first timer in kubernetes. But i saw nothing wrong in formatting code nor indentation. Only i think there is missing some instruction in creating apps. Should be better to follow Just my 2cent. wdyt?
/assign
Change:
#### Network traffic is not forwarded <del> Please see [debugging service](/docs/tasks/debug/debug-applications/debug-service/) for more information. </del> <ins> Please see [debugging service](/docs/tasks/debug/debug-application/debug-service/) for more information. </ins> ## {{% heading "whatsnext" %}} If none of the above solves your problem, follow the instructions in <del> [Debugging Service document](/docs/tasks/debug/debug-applications/debug-service/) </del> <ins> [Debugging Service document](/docs/tasks/debug/debug-application/debug-service/) </ins> to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are actually serving; you have DNS working, iptables rules installed, and kube-proxy does not seem to be misbehaving.

Discussion:
Links to "Debugging Service" documents are not working. It is currently linking to when it should be
/triage accepted
Change:
### Local <del> {{< feature-state for_k8s_version="v1.14" state="stable" >}} </del> ```yaml apiVersion: storage.k8s.io/v1 kind: StorageClass

Discussion:
There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted
Change:
kubectl exec -ti cassandra-0 -- nodetool status # cleanup <del> grace=$(kubectl get po cassandra-0 --template '{{.spec.terminationGracePeriodSeconds}}')  </del> <ins> grace=$(kubectl get po cassandra-0 -o=jsonpath='{.spec.terminationGracePeriodSeconds}')  </ins> && kubectl delete statefulset,po -l app=cassandra  && echo "Sleeping $grace"  && sleep $grace 

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: There is a warning during the Netlify preview build process: Looks like liquid is trying to parse in the line: Proposed Solution: Find out how to escape in a code block for Liquid. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Kubernetes 1.6 <!--Additional Information:--
Change:
4. Katacoda environment only: Type `30000`, and then click **Display Port**. <ins> {{< note >}} The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. If you are running in an environment as root, see [Open Dashboard with URL](/docs/tutorials/hello-minikube#open-dashboard-with-url). To stop the proxy, run `Ctrl+C` to exit the process. The dashboard remains running. {{< /note >}} ## Open Dashboard with URL If you don't want to open a web browser, run the dashboard command with the url flag to emit a URL: ```shell minikube dashboard --url ``` </ins> ## Create a Deployment A Kubernetes [*Pod*](/docs/concepts/workloads/pods/) is a group of one or more Containers,

Discussion:
After issuing the command "minikube dashboard" in the "Create a minikube cluster" section, I never get the command prompt back. How, then, am I supposed to issue the commands listed in the following section, "Create a deployment"?
/retitle “Hello Minikube” tutorial runs dashboard subcommand in foreground /kind bug /triage accepted That's a good point. The tutorial doesn't explain what to do here. /priority important-longterm /language en
!
/assign
Change:
min-kubernetes-server-version: v1.22 --- <del> Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). </del> <ins> Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). The three policies [privileged](/docs/concepts/security/pod-security-standards/#privileged), [baseline](/docs/concepts/security/pod-security-standards/#baseline) and [restricted](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted) broadly cover the security spectrum and are implemented by the [Pod Security](/docs/concepts/security/pod-security-admission/) {{< glossary_tooltip text="admission controller" term_id="admission-controller" >}}. </ins> ## {{% heading "prerequisites" %}}

Discussion:
Hello, It's not clear what the meaning of restricted warnings and restricted audit or any combination of them. It seems that you attempt to design in a way that you want to make things more complicated. The aim of your design seems that nobody should be able to understand clearly and one should spend a lot of time for understanding the basics. You can create very complex systems but at the end you will see that nobody uses them. We have seen such attempts in the past from big vendors and after a lot of marketing and spending millions of dollars, those big guys failed miserably. Can someone explain the meaning of all those and possibly more combinations? enforce: baseline, audit: baseline, warn: baseline enforce: baseline, audit: restricted, warn: baseline enforce: baseline, audit: restricted, warn: restricted enforce: restricted, audit: baseline, warn: baseline enforce: restricted, audit: restricted, warn: baseline enforce: restricted, audit: restricted, warn: restricted enforce: privileged, audit: baseline, warn: baseline enforce: privileged, audit: privileged, warn: baseline enforce: privileged, audit: privileged, warn: privileged enforce: baseline, audit: restricted, warn: privileged ... ... ...
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 first sentence in this page is Although this introduction is accurate, we could add more text to avoid the risk of a reader skipping past it and then feeling confused. For example, we could name the three Pod Security Standards and make each of those names a link to the relevant part of ; we could also repeat the table from the top of do you think adding more text to the introduction would help here? /language en
We could also link to in the introduction; I think we should.
Change:
<!-- ## Debugging via a shell on the node {#node-shell-session} <del> If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host, but this should generally not be necessary given tools in the Kubernetes API. Therefore, if you find yourself needing to ssh into a machine, please file a feature request on GitHub describing your use case and why these tools are insufficient. </del> <ins> If none of these approaches work, you can find the Node on which the Pod is running and create a privileged Pod running in the host namespaces. To create an interactive shell on a node using `kubectl debug`, run: </ins> --> <del> ## 在节点上通过 shell 来调试 {#node-shell-session} </del> <ins> ## 在节点上通过 shell 来进行调试 {#node-shell-session} </ins> <del> 如果这些方法都不起作用，你可以找到运行 Pod 的主机并通过 SSH 进入该主机， 但是如果使用 Kubernetes API 中的工具，则通常不需要这样做。 因此，如果你发现自己需要使用 ssh 进入主机，请在GitHub 上提交功能请求， 以描述你的用例以及这些工具不足的原因。 </del> <ins> 如果这些方法都不起作用，你可以找到运行 Pod 的节点，然后在节点上部署一个运行在宿主名字空间的特权 Pod。 你可以通过`kubectl debug` 在节点上创建一个交互式 shell： ```shell kubectl debug node/mynode -it --image=ubuntu ``` ``` Creating debugging pod node-debugger-mynode-pdx84 with container debugger on node mynode. If you don't see a command prompt, try pressing enter. root@ek8s:/# ``` <!-- When creating a debugging session on a node, keep in mind that: * `kubectl debug` automatically generates the name of the new Pod based on the name of the Node. * The container runs in the host IPC, Network, and PID namespaces. * The root filesystem of the Node will be mounted at `/host`. Don't forget to clean up the debugging Pod when you're finished with it: --> 当在节点上创建调试会话，注意以下要点： * `kubectl debug` 基于节点的名字自动生成新的 Pod 的名字。 * 新的调试容器运行在宿主命名空间里（IPC, 网络 还有PID命名空间）。 * 节点的根文件系统会被挂载在 `/host`。 当你完成节点调试时，不要忘记清理调试 Pod： ```shell kubectl delete pod node-debugger-mynode-pdx84 ``` </ins>  No newline at end of file

Discussion:
Recently I am exploring the and found that section of in the Chinese document is outdated so I tried to update it. en: 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
/language zh
Change:
<td colspan="2">--service-account-key-file strings</td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. The specified file can contain multiple keys, and the flag can be specified multiple times with different files. If unspecified, --tls-private-key-file is used. Must be specified when --service-account-signing-key is provided</p></td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. The specified file can contain multiple keys, and the flag can be specified multiple times with different files. If unspecified, --tls-private-key-file is used. Must be specified when --service-account-signing-key-file is provided</p></td> </ins> </tr> <tr>

Discussion:
This is a Bug Report Problem: Documentation for cli tool kube-apiserver ] references flag which doesn't exist. The intended documentation should reference the flag. The cli tool implementation ] also has an incorrect doc-string ]. I'll make cross-referencing issues for both projects Proposed Solution: All references to the should be updated to Page to Update: Kubernetes Versions: Additional Information: Issue and PR on the kubernetes/kubernetes project are:
/assign /triage accepted
/retitle Documentation references --service-account-signing-key flag that doesn't exist
This is now essentially a duplicate of
Change:
## {{% heading "whatsnext" %}} <del> * Read the [kube-scheduler reference](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/) </del> <ins> * Read the [kube-scheduler reference](/docs/reference/command-line-tools-reference/kube-scheduler/) </ins> * Learn about [scheduling](/docs/concepts/scheduling-eviction/kube-scheduler/) * Read the [kube-scheduler configuration (v1beta1)](/docs/reference/config-api/kube-scheduler-config.v1beta1/) reference

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
힙스터에서 메트릭 가져오기는 Kubernetes 1.11에서 사용 중단(deprecated)됨. {{< /note >}} <del> 자세한 사항은 [메트릭 API를 위한 지원](#메트릭-API를-위한-지원)을 참조한다. </del> <ins> 자세한 사항은 [메트릭 API를 위한 지원](#메트릭-api를-위한-지원)을 참조한다. </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: In , the link " API " is broken. Proposed Solution: Page to Update: -- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
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
/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 </details
/assign
Change:
For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like [Minikube](https://minikube.sigs.k8s.io/docs/start/) to be installed first and then re-run the commands stated above. <del> If kubectl cluster-info returns the url response but you can't access your cluster, </del> <ins> If `kubectl cluster-info` returns the url response but you can't access your cluster, </ins> to check whether it is configured properly, use: ```shell

Discussion:
The is a command code but not marked as inline code. I think marking it will help learners
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
Raised PR with fix /assign
Change:
1. Apply the MongoDB Service from the following `mongo-service.yaml` file: <ins> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml --> </ins> ```shell kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml ``` <del> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml --> </del> 1. Query the list of Services to verify that the MongoDB Service is running: ```shell

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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
Change:
The version of Kubernetes that you need depends on which KMS API version you have selected.  Kubernetes recommends using KMS v2. <del> - If you selected KMS API v2, you should use Kubernetes v{{< skew currentVersion >}} (if you are running a different version of Kubernetes that also supports the v2 KMS API, switch to the documentation for that version of Kubernetes). </del> - If you selected KMS API v1 to support clusters prior to version v1.27 or if you have a legacy KMS plugin that only supports KMS v1, any supported Kubernetes version will work.  This API is deprecated as of Kubernetes v1.28.

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 prerequisites for KMS encryption of control plane data are a bit stale given that KMSv2 is now fully stable and all supported releases include some level of KMSv2 support. no longer really applies. Proposed Solution: Revise and reword the start of the page, to focus on recommending KMSv2 rather than recommending specific Kubernetes versions. Page to Update: Additional Information: /sig security /language en
/priority backlog /triage accepted
/assign
Change:
1. This Service specification explicitly defines `IPv6` and `IPv4` in `.spec.ipFamilies` as well as defining `PreferDualStack` in `.spec.ipFamilyPolicy`. When Kubernetes assigns an IPv6 and <del> IPv4 address in `.spec.ClusterIPs`, `.spec.ClusterIP` is set to the IPv6 address because that is the first element in the `.spec.ClusterIPs` array, overriding the default. </del> <ins> IPv4 address in `.spec.clusterIPs`, `.spec.clusterIP` is set to the IPv6 address because that is the first element in the `.spec.clusterIPs` array, overriding the default. </ins> {{% code_sample file="service/networking/dual-stack-preferred-ipfamilies-svc.yaml" %}}

Discussion:
page is plenty of wrong references to the non defined ` instead.
/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
/kind bug
/assign
Thanks for solving this so so quick (you are the best ;-)
Change:
<td colspan="2">--cloud-config string</td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to the cloud provider configuration file. Empty string for no configuration file. (DEPRECATED: will be removed in 1.23, in favor of removing cloud providers code from Kubelet.)</td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;">The path to the cloud provider configuration file. Empty string for no configuration file. (DEPRECATED: will be removed in 1.24 or later, in favor of removing cloud providers code from kubelet.)</td> </ins> </tr> <tr> <td colspan="2">--cloud-provider string</td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;">The provider for cloud services. Set to empty string for running with no cloud provider. If set, the cloud provider determines the name of the node (consult cloud provider documentation to determine if and how the hostname is used). (DEPRECATED: will be removed in 1.23, in favor of removing cloud provider code from Kubelet.)</td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;">The provider for cloud services. Set to empty string for running with no cloud provider. If set, the cloud provider determines the name of the node (consult cloud provider documentation to determine if and how the hostname is used). (DEPRECATED: will be removed in 1.24 or later, in favor of removing cloud provider code from Kubelet.)</td> </ins> </tr> <tr>

Discussion:
As per the Kubernetes documentation option is deprecated and removed in v1.23. The link for the documentation. But this parameter is still valid. I got the confiramation. Kublet code : configured the kubelet with in my test K8s v1.23 environment. validated in the # sig-cloud-provider. Document should reflect the correct details: The link for the documentation. Configure the kubelet with the option. No response <details</details<detailsopenstack </details<details</details<details</details<details</details<details</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
/sig node /sig cloud-provider
This pr has fixed this, waiting website docs to be published.
/kind documentation /remove-kind bug /transfer-issue website
/assign