jiebi/CodeConvo huggingface dataset:
Change:
## {{% heading "prerequisites" %}} <del> {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} </del> <ins> You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this task on a cluster with at least two nodes that are not acting as control plane nodes . If you do not already have a cluster, you can create one by using [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/). </ins> <!-- steps -->

Discussion:
This is a... [x] Feature Request [ ] Bug Report Study this topic and related topics: . Bring all of the etcd content into a coherent set of topics. Check for accuracy, and update as needed. Put topics into the appropriate templates. Edit topics to comply with our style guide.
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
/remove-lifecycle rotten /lifecycle frozen /reopen
/language en
/priority backlog Is that OK?
Actually where exactly are the deviations from the style guide?
/triage accepted I don't see any obvious style concerns.
is wrong: you can't practice operating an etcd cluster for Kubernetes within a Katacoda playground, at least not unless you get very technical.
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
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:
<!-- {{< table caption="Local machine solutions table that lists the tools supported by the community and the ecosystem to deploy Kubernetes." >}} |Community           |Ecosystem     | <del> |社区           |生态系统     | </del> <ins> | ------------       | --------     | | [Minikube](/docs/setup/learning-environment/minikube/) | [Docker Desktop](https://www.docker.com/products/docker-desktop)| | [kind (Kubernetes IN Docker)](/docs/setup/learning-environment/kind/) | [Minishift](https://docs.okd.io/latest/minishift/)| |                     | [MicroK8s](https://microk8s.io/)| </ins> --> {{< table caption="本地机器解决方案表，其中列出了社区和生态系统支持的用于部署 Kubernetes 的工具。" >}} |社区           |生态系统     | | ------------       | --------     | <del> | [Minikube](/docs/setup/learning-environment/minikube/) | [CDK on LXD](https://www.ubuntu.com/kubernetes/docs/install-local) | | [kind (Kubernetes IN Docker)](https://github.com/kubernetes-sigs/kind) | [Docker Desktop](https://www.docker.com/products/docker-desktop)| |                     | [Minishift](https://docs.okd.io/latest/minishift/)| </del> <ins> | [Minikube](/docs/setup/learning-environment/minikube/) | [Docker Desktop](https://www.docker.com/products/docker-desktop)| | [kind (Kubernetes IN Docker)](/docs/setup/learning-environment/kind/) | [Minishift](https://docs.okd.io/latest/minishift/)| </ins> |                     | [MicroK8s](https://microk8s.io/)| <del> |                     | [IBM Cloud Private-CE (Community Edition)](https://github.com/IBM/deploy-ibm-cloud-private) | |                     | [IBM Cloud Private-CE (Community Edition) on Linux Containers](https://github.com/HSBawa/icp-ce-on-linux-containers)| |                     | [k3s](https://k3s.io)| |                     | [Ubuntu on LXD](/docs/getting-started-guides/ubuntu/)| </del> <!--

Discussion:
This is a Feature Request Chinese "Gettting started" page not updated. <!-- 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. -- page is not corresponed to English original page especially the "Learning environment" part and "Production environment" part ! ! Why is this needed Update Chinese "Gettting started" page Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page in English: Page in Chinese:
/language zh
/assign
Change:
Here's an example of a Job with two containers, one of which is a sidecar: {{% code_sample language="yaml" file="application/job/job-sidecar.yaml" %}} <del> By default, this feature is not available in Kubernetes. To avail this feature, you need to enable the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers`. </del> ## Differences from regular containers

Discussion:
This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:
/sig docs /language en
/assign
Beta APIs are off by default with
is not a beta API though /triage accepted
Change:
letter-spacing: 0.03em; } <ins> .youtube-quote-sm { display: inline-block; width: 380px; height: 215px; } .youtube-quote-sm iframe { width: 100%; height: 100%; border: 0; } </ins> @media screen and (max-width: 910px) { h1 { font-size: 32px;

Discussion:
This is a clean up 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 use the  shortcode that is built in to Hugo. Why is this needed Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. Comments /kind cleanup /help /language en If you make this change, and check that the videos still render. Related to
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 : This is a clean up request <!-- See for guidance on writing an actionable issue description. --Update the to use the  shortcode that is built in to Hugo. Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. /kind cleanup /help /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
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
Thanks
Change:
done ``` <del> Then verify the blob by using `cosign`: </del> <ins> Then verify the blob by using `cosign verify-blob`: </ins> ```shell <del> cosign verify-blob "$BINARY" --signature "$BINARY".sig --certificate "$BINARY".cert </del> <ins> cosign verify-blob "$BINARY"  --signature "$BINARY".sig  --certificate "$BINARY".cert  --certificate-identity krel-staging@k8s-releng-prod.iam.gserviceaccount.com  --certificate-oidc-issuer https://accounts.google.com </ins> ``` <del> cosign v1.9.0 is required to be able to use the `--certificate` flag. Please use `--cert` for older versions of cosign. </del> {{< note >}} <del> To learn more about keyless signing, please refer to [Keyless Signatures](https://github.com/sigstore/cosign/blob/main/KEYLESS.md#keyless-signatures). </del> <ins> Cosign 2.0 requires the `--certificate-identity` and `--certificate-oidc-issuer` options. To learn more about keyless signing, please refer to [Keyless Signatures](https://docs.sigstore.dev/cosign/keyless). Previous versions of Cosign required that you set `COSIGN_EXPERIMENTAL=1`. For additional information, plase refer to the [sigstore Blog](https://blog.sigstore.dev/cosign-2-0-released/) </ins> {{< /note >}} ## Verifying image signatures

Discussion:
This is a Feature Request After release, we don't need . We should update the instructions on the task to include verification using cosign 2.0 <!-- 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 <details<summaryverification using cosign 2.0</summaryAdd a note if cosign version < 2.0 </details<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed There are some breaking changes in cosign 2.0 and we should update the instruction for the verification of images. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/sig release /sig security /retitle Update page Verify Signed Kubernetes Artifacts for cosign 2.0 /kind bug /remove-kind feature /language en /triage accepted Thanks
:+1:
I can work on this /assign
Hey Are you still working on this issue? If not, can I work on this?
Haven't gotten to it as I expected to. Please feel free to work on it /unassign
/assign
FYI
Apologies for not being able to review the PR. I am going through University exams which is ending tomorrow. I just rushed through the changes that you made and you really did awesome work on this. I'll look more into this after the exams. Thanks for working on this.
Change:
<ins> --- title: "Migrating from dockershim" weight: 10 content_type: task --- <!-- overview --> This section presents information you need to know when migrating from dockershim to other container runtimes. Since the announcement of [dockershim deprecation](/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation) in Kubernetes 1.20, there were questions on how this will affect various workloads and Kubernetes installations. You can find this blog post useful to understand the problem better: [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/) It is recommended to migrate from dockershim to alternative container runtimes. Check out [container runtimes](/docs/setup/production-environment/container-runtimes/) section to know your options. Make sure to [report issues](https://github.com/kubernetes/kubernetes/issues) you encountered with the migration. So the issue can be fixed in a timely manner and your cluster would be ready for dockershim removal. </ins>

Discussion:
This is a Feature Request I want to ask a new documentation section under describing various aspects of moving away from Dockershim to other runtimes. One document I am working with is: There are more sub-topics will be there. Is there any concerns with creating this section? It will be relatively short-lived, but definitely beneficial for k8s users. What would you like to be Section under regarding migrating away from Dockershim. Why is this needed Since this announcement: there are a still things needed clarification which raise questions. /sig node
A Task page is the right kind of content to add. Are you considering adding a section inside ? I would add that rather than one inside - the deeper structure can be OK so long as we make sure there are lots of links to it. When that content disappears, where will we redirect to? I assume we'd want to add redirects
what do you think of this: Is it the right structure?
Hi . I started to read through PR . The location under tasks seems fine, though, you could create a new sub-directory () under tasks so that the content is not lost in the section. The new section could be titled something like: "Manage Dockershim migration" or "Migrate from Dockershim". What do you think about creating an outline (in this issue) of the sub-tasks to include in this section?
this was my original idea of a location, but suggested to place it under the administer section. looking at the content, should it be moved to it's own section? Some topics like monitoring agents is more of an application management than administering of a cluster.
My concerns from before stand, but they're not hard don't-do-this objections.
/triage accepted anyway
Hi . I'll spend some time to read the PR and doc. After a quick read, I think it probably make sense to separate the content from the tasks. Again, it is a good idea to write an outline of the content. This may help to determine where to put the content once the content is created.
Hope this is okay: /assign
Change:
<del> <tr><td><code>format</code> <B>[Required]</B><br/> <code>string</code> </del> <ins> <tr><td><code>numaNode</code> <B>[Required]</B><br/> <code>int32</code> </ins> </td> <td> <del> Format Flag specifies the structure of log messages. default value of format is `text`</td> </del> <ins> <span class="text-muted">No description provided.</span> </td> </ins> </tr> <del> <tr><td><code>sanitization</code> <B>[Required]</B><br/> <code>bool</code> </del> <ins> <tr><td><code>limits</code> <B>[Required]</B><br/> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#resourcelist-v1-core"><code>core/v1.ResourceList</code></a> </ins> </td> <td> <del> [Experimental] When enabled prevents logging of fields tagged as sensitive (passwords, keys, tokens). Runtime log sanitization may introduce significant computation overhead and therefore should not be enabled in production.`)</td> </del> <ins> <span class="text-muted">No description provided.</span> </td> </ins> </tr> </tbody> </table> <ins> ## `ResourceChangeDetectionStrategy`     {#kubelet-config-k8s-io-v1beta1-ResourceChangeDetectionStrategy} (Alias of `string`) **Appears in:** - [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) ResourceChangeDetectionStrategy denotes a mode in which internal managers (secret, configmap) are discovering object changes. </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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. Page to Update:
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
I would like to take up this ticket.
Change:
<p>Speed of delivery increased. Some of the legacy VM-based deployments took 45 minutes; with Kubernetes, that time was "just a few seconds to a couple of minutes," says Engineering Manager Brian Balser. Adds Li: "Teams that used to deploy on weekly schedules or had to coordinate schedules with the infrastructure team now deploy their updates independently, and can do it daily when necessary." Adopting Cloud Native Computing Foundation technologies allows for a more unified approach to deployment across the engineering staff, and portability for the company.</p> <del> {{< case-studies/quote author="Deep Kapadia, Executive Director, Engineering at The New York Times">}} <iframe style="padding:1%:" width="380" height="215" src="https://www.youtube.com/embed/DqS_IPw-c6o" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe> <iframe style="padding:1%:" width="380" height="215" src="https://www.youtube.com/embed/Tm4VfJtOHt8" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe> <br> </del> <ins> {{< case-studies/quote author="Deep Kapadia, Executive Director, Engineering at The New York Times" >}} {{< youtube DqS_IPw-c6o youtube-quote-sm >}} {{< youtube Tm4VfJtOHt8 youtube-quote-sm >}} </ins> "I think once you get over the initial hump, things get a lot easier and actually a lot faster." {{< /case-studies/quote >}}

Discussion:
This is a clean up 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 use the  shortcode that is built in to Hugo. Why is this needed Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. Comments /kind cleanup /help /language en If you make this change, and check that the videos still render. Related to
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 : This is a clean up request <!-- See for guidance on writing an actionable issue description. --Update the to use the  shortcode that is built in to Hugo. Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. /kind cleanup /help /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
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
Thanks
Change:
Session Affinity:   None Events:         <none> <del> Make a note of the external IP address exposed by your service. In this example, the external IP address is 104.198.205.71. Also note the value of Port. In this example, the port is 8080. </del> <ins> Make a note of the external IP address (`LoadBalancer Ingress`) exposed by your service. In this example, the external IP address is 104.198.205.71. Also note the value of `Port` and `NodePort`. In this example, the `Port` is is 8080 and the `NodePort` is 32377. </ins> 1. In the preceding output, you can see that the service has several endpoints: 10.0.0.6:8080,10.0.1.6:8080,10.0.1.7:8080 + 2 more. These are internal

Discussion:
This is a Bug Report Problem: does not have correct instructions. Proposed Solution: In , Make a note of the external IP address exposed by your service should be Make a note of the external IP address () exposed by your service Also note the value of Port. In this example, the port is 8080 should be Also note the value of and . In this example, the port is 8080 and NodePort is Use the external IP address to access the Hello World application should be Use the external IP address () to access the Hello World application where is the external IP address of your Service, and is the value of in your Service description should be where is the external IP address () of your Service, and is the value of in your Service description. If you are using minukube, typing will automatically open the Hello World application in a browser. Page to Update: Kubernetes Version: Additional Information: These corrections will really help new k8s/minikube users. Thanks!
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:
standardized. See the documentation of each CSI driver for further instructions. <ins> ### CSI driver restrictions {{< feature-state for_k8s_version="v1.21" state="deprecated" >}} </ins> As a cluster administrator, you can use a [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) to control which CSI drivers can be used in a Pod, specified with the [`allowedCSIDrivers` field](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podsecuritypolicyspec-v1beta1-policy). <ins> {{< note >}} PodSecurityPolicy is deprecated and will be removed in the Kubernetes v1.25 release. {{< /note >}} </ins> ### Generic ephemeral volumes {{< feature-state for_k8s_version="v1.23" state="stable" >}}

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 "Ephemeral Volumes" page, some -related contents exist. But according to the : Proposed Solution: Update -related contents in "Ephemeral Volumes", as PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be removed in v1.25. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign