jiebi/CodeConvo huggingface dataset:
Change:
- The code is not generic enough for users to try out. As an example, you can embed the YAML file for creating a Pod which depends on a specific <del> [FlexVolume](/docs/concepts/storage/volumes#flexvolume) implementation. </del> <ins> [FlexVolume](/docs/concepts/storage/volumes/#flexvolume-deprecated) implementation. </ins> - The code is an incomplete example because its purpose is to highlight a portion of a larger file. For example, when describing ways to customize a [RoleBinding](/docs/reference/access-authn-authz/rbac/#role-binding-examples),

Discussion:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /assign /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
Change:
must be installed on the cluster and the `CSIMigration` and `CSIMigrationAzureDisk` features must be enabled. <ins> #### azureDisk CSI migration complete {{< feature-state for_k8s_version="v1.21" state="alpha" >}} To disable the `azureDisk` storage plugin from being loaded by the controller manager and the kubelet, set the `InTreePluginAzureDiskUnregister` flag to `true`. </ins> ### azureFile {#azurefile} The `azureFile` volume type mounts a Microsoft Azure File volume (SMB 2.1 and 3.0)

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: doesn't mention the feature gate , but it should do. Proposed Solution: Update documentation for migration from in-tree Azure File driver. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig storage /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
Change:
<!-- overview --> This page explains how to add versioning information to <del> [CustomResourceDefinitions](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1beta1-apiextensions), to indicate the stability </del> <ins> [CustomResourceDefinitions](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/), to indicate the stability </ins> level of your CustomResourceDefinitions or advance your API to a new version with conversion between API representations. It also describes how to upgrade an object from one version to another. ## {{% heading "prerequisites" %}}

Discussion:
The link to CustomResourceDefinitions is broken. Rather it should point to
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
The link should actually be to (at least, that's where I recommend linking to) /kind bug /language en
cool, I will update the PR with
Change:
1. Unduh versi terbarunya dengan perintah: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/`curl -LS https://dl.k8s.io/release/stable.txt`/bin/linux/amd64/kubectl </ins> ``` <del> Untuk mengunduh versi spesifik, ganti bagian `curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt` dengan versi yang diinginkan. </del> <ins> Untuk mengunduh versi spesifik, ganti bagian `curl -LS https://dl.k8s.io/release/stable.txt` dengan versi yang diinginkan. </ins> Misalnya, untuk mengunduh versi {{< param "fullversion" >}} di Linux, ketik: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </ins> ``` 2. Jadikan program `kubectl` dapat dieksekusi.

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: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
systemctl daemon-reload systemctl restart docker ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} 부팅 시 도커 서비스를 시작하려면, 다음 명령을 실행한다.

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:
<ins> apiVersion: v1 kind: Service metadata: name: my-service labels: app: MyApp spec: ipFamilyPolicy: PreferDualStack ipFamilies: - IPv6 type: LoadBalancer selector: app: MyApp ports: - protocol: TCP port: 80 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted
Change:
## {{% heading "whatsnext" %}} * Read about the [Prometheus text format](https://github.com/prometheus/docs/blob/master/content/docs/instrumenting/exposition_formats.md#text-based-format) for metrics <del> * See the list of [stable Kubernetes metrics](https://github.com/kubernetes/kubernetes/blob/master/test/instrumentation/testdata/stable-metrics-list.yaml) </del> * Read about the [Kubernetes deprecation policy](/docs/reference/using-api/deprecation-policy/#deprecating-a-feature-or-behavior)

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 monitoring page on the Kubernetes website has a link to in the What's Next section which links to an empty list in GitHub. Proposed Solution: I have been unable to find another list of stable metrics. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Looks wrong to me. /language en /priority backlog /kind bug
Duplicated by issue
I tried to compile the generated content of the file locally, but I didn't get any results. It was generated using , but there are bugs and need to be fixed.
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. 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
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
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /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
/reopen /assign
Reopened this issue. <detailsIn response to : /reopen /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
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
/remove-lifecycle rotten
Change:
</tr> <tr> <ins> <td colspan="2">--one_output</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true, only write logs to their native severity level (vs also writing to each lower severity level)</p></td> </tr> <tr> </ins> <td colspan="2">--oom-score-adj int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: -999</td> </tr> <tr>

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
![Node level logging](/images/docs/user-guide/logging/logging-node-level.png) <del> A container runtime handles and redirects any output generated to a containerized application's `stdout` and `stderr` streams. Different container runtimes implement this in different ways; however, the integration with the kubelet is standardized as the _CRI logging format_. </del> <ins> A container runtime handles and redirects any output generated to a containerized application's `stdout` and `stderr` streams. Different container runtimes implement this in different ways; however, the integration with the kubelet is standardized as the _CRI logging format_. </ins> <del> By default, if a container restarts, the kubelet keeps one terminated container with its logs. If a pod is evicted from the node, all corresponding containers are also evicted, along with their logs. </del> <ins> By default, if a container restarts, the kubelet keeps one terminated container with its logs. If a pod is evicted from the node, all corresponding containers are also evicted, along with their logs. </ins> <del> The kubelet makes logs available to clients via a special feature of the Kubernetes API. The usual way to access this is by running `kubectl logs`. </del> <ins> The kubelet makes logs available to clients via a special feature of the Kubernetes API. The usual way to access this is by running `kubectl logs`. </ins> ### Log rotation

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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs 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 en
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
spec: containers: - name: php-redis <del> image: gcr.io/google_samples/gb-frontend:v5 </del> <ins> image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5 </ins> env: - name: GET_HOSTS_FROM value: "dns"

Discussion:
cannot pull frontend container, it shows ImagePullBackOff !
Page reported in issue: /language zh
/retitle [zh] Deprecated image causes failures in "Deploying PHP Guestbook with Redis" tutorial
/kind bug
/triage accepted /assign
Change:
apiVersion: kubeadm.k8s.io/v1beta4 kind: UpgradeConfiguration </code></pre> <del> <p>To print the defaults for &quot;init&quot; and &quot;join&quot; actions use the following commands:</p> </del> <ins> <p>To print the defaults for <code>init</code> and <code>join</code> actions use the following commands:</p> </ins> <pre style="background-color:#fff">kubeadm config print init-defaults kubeadm config print join-defaults kubeadm config print reset-defaults kubeadm config print upgrade-defaults </pre><p>The list of configuration types that must be included in a configuration file depends by the action you are <del> performing (<code>init or </code>join`) and by the configuration options you are going to use (defaults or advanced customization).</p> </del> <ins> performing (<code>init</code> or <code>join</code>) and by the configuration options you are going to use (defaults or advanced customization).</p> </ins> <p>If some configuration types are not provided, or provided only partially, kubeadm will use default values; defaults provided by kubeadm includes also enforcing consistency of values across components when required (e.g. <code>--cluster-cidr</code> flag on controller manager and <code>clusterCIDR</code> on kube-proxy).</p>

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.
Change:
yum install -y cri-o ``` <del> {{< tab name="openSUSE Tumbleweed" >}} </del> <ins> {{% tab name="openSUSE Tumbleweed" %}} </ins> ```shell sudo zypper install cri-o ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} ### CRI-O 시작

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:
/* DOCS */ .launch-cards { <ins> padding: 0; .launch-card{ padding: 0; display: flex; flex-direction: column; background-color: #DAEAf9; border:2px solid #99B7D3; border-radius: 8px; h2 { text-align: center; font-size: 1.75em; padding: .5em; a{ display: none; } } p { padding: .5em; text-align: center; } ul { list-style: disc; color: #99B7D3; margin: 0 auto; margin-block-end: auto; } </ins> button { <ins> height: min-content; margin: 0 auto; padding: .5em .75em; </ins> cursor: pointer; box-sizing: border-box; <del> background: none; margin: 0; border: 0; } ul, li { list-style: none; padding-left: 0; </del> } } <ins> } </ins> // table of contents .td-toc {

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 /enhanced? As it can be clearly seen at that the layout of this page is looking somewhat inconsistent due to this visible big-small difference in 'Cards' at 2nd and 3rd row. ! ! Solution: I think this issue can be easily resolved by replacing the 'Card' of (3rd Column, 2nd Row) with (1st Row, 3rd Column) like this:- ! ! As 'Cards' of 2nd row are all vertically tall and 'Cards' of 3rd row are all vertically small. So, replacing these 2nd 'Cards' with each other will possibly solve the problem. By Card, i mean that whole thing inside yellow line (Heading, description, hyperlinks and button)
/area web-development
/assign
A was previously filed. See and for more context.
/retitle Poor alignment for tiles and buttons on home page for docs
/triage accepted /priority backlog
/assign
/retitle Poor alignment for tiles on home page for docs
Change:
This document outlines the various components you need to have for a complete and working Kubernetes cluster. <del> {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" >}} </del> <ins> {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" clicktozoom="true" >}} </ins> <!-- body --> ## Control Plane Components

Discussion:
This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:
/area web-development /kind feature
/area web-development Something similar to https://medium- ?
/retitle Enable click-to-zoom for some diagrams and other images
/triage accepted /priority backlog /lifecycle frozen
Thanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.
For now I'll investigate more and try to find out what can work so assigning it to myself /assign
A couple of hints:
There is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code
one is a good reference for same functionality with example. I'll try both and raise a PR after that.
We using vector images.
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
My apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.
This could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen
Let me see if I can assist with this. Edit: I request review and feedback on pull request