jiebi/CodeConvo huggingface dataset:
Code change:
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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted

Related discussion:
text: [javascript_required] other = "JavaScript must be [enabled](https://www.enable-javascript.com/) to view this content" <del> [katacoda_removal_warning] other = """This online tutorial on this page uses functionality that will [not be available](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html) past <time datetime="2022-06-15">June 15th, 2022</time>.""" </del> [latest_release] other = "Latest Release:"
Code change:
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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted

Related discussion:
text: {{ block "deprecated" . }} {{ partial "deprecation-warning.html" . }} {{ end }} <del> {{ if or ( .HasShortcode "kat-button" ) ( .HasShortcode "katacoda-tutorial" ) }} {{ block "katacoda-removal" . }} {{ partial "katacoda-removal.html" . }} {{ end }} {{ end }} </del> {{ block "main" . }}{{ end }} {{- if .HasShortcode "thirdparty-content" -}} {{ block "thirdparty-disclaimer" . }}
Code change:
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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted

Related discussion:
text: <del> <section id="katacoda-removal-warning"> <div class="content warning pageinfo pageinfo-warning"> <p> {{ T "katacoda_removal_warning" | markdownify }} </p> </div> </section> </del>
Code change:
The and link in the section are broken.
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 don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -

Related discussion:
text: admission controller. To get started with `cosigned` here are a few helpful resources: <del> * [Installation](https://github.com/sigstore/helm-charts/tree/main/charts/cosigned) </del> <ins> * [Installation](https://github.com/sigstore/cosign#installation) </ins> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config)
Code change:
The and link in the section are broken.
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 don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -

Related discussion:
text: resources: * [Installation](https://github.com/sigstore/cosign#installation) <del> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config) </del> <ins> * [Configuration Options](https://github.com/sigstore/cosign/blob/main/USAGE.md#detailed-usage) </ins>
Code change:
This is a Bug Report Problem: Following below hyperlinks are not working under task: and The reason for it is it both redirects to but the is changed to in this PR: Proposed Solution: Changed to for both dedicated CA and custom CA. Page to Update:
Also, the hyperlinks for both dedicated CA and custom CA were in this PR:
/assign /sig auth
Fixed it here:
/language en /triage accepted Thanks for spotting this
you're welcome!

Related discussion:
text: {{< note >}} Certificates created using the `certificates.k8s.io` API are signed by a <del> [dedicated CA](#a-note-to-cluster-administrators). It is possible to configure your cluster to use the cluster root </del> <ins> [dedicated CA](#configuring-your-cluster-to-provide-signing). It is possible to configure your cluster to use the cluster root </ins> CA for this purpose, but you should never rely on this. Do not assume that these certificates will validate against the cluster root CA. {{< /note >}}
Code change:
This is a Bug Report Problem: Following below hyperlinks are not working under task: and The reason for it is it both redirects to but the is changed to in this PR: Proposed Solution: Changed to for both dedicated CA and custom CA. Page to Update:
Also, the hyperlinks for both dedicated CA and custom CA were in this PR:
/assign /sig auth
Fixed it here:
/language en /triage accepted Thanks for spotting this
you're welcome!

Related discussion:
text: ## Trusting TLS in a cluster <del> Trusting the [custom CA](#a-note-to-cluster-administrators) from an application running as a pod usually requires </del> <ins> Trusting the [custom CA](#configuring-your-cluster-to-provide-signing) from an application running as a pod usually requires </ins> some extra application configuration. You will need to add the CA certificate bundle to the list of CA certificates that the TLS client or server trusts. For example, you would do this with a golang TLS config by parsing the certificate
Code change:
pods/pod-with-node-affinity.yaml
Page: /language zh
/triage accepted The YAML file was not sync'ed with English version.
/assign

Related discussion:
text: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: topology.kubernetes.io/zone </del> <ins> - key: kubernetes.io/os </ins> operator: In values: <del> - antarctica-east1 - antarctica-west1 </del> <ins> - linux </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:
Code change:
pods/pod-with-node-affinity.yaml
Page: /language zh
/triage accepted The YAML file was not sync'ed with English version.
/assign

Related discussion:
text: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: kubernetes.io/os </del> <ins> - key: topology.kubernetes.io/zone </ins> operator: In values: <del> - linux </del> <ins> - antarctica-east1 - antarctica-west1 </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:
Code change:
Cloning is only supported within the same Storage Class. Cloning has supported different storage class
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
Hello It sounds like you might want to report that a web page is wrong. If that's right, what's the URL of the webpage? Also, could you quote or point out the text in that page that isn't right? /language en /triage needs-information
/sig storage
Hi i would like to explain this issue if i am not wrong wants to update this . As is merged so now users will be able to clone a volume with a different Storage Class. The destination volume no longer has to be the same storage class as the source. But in current documentation we have the behaviour as. Cloning is only supported within the same Storage Class. Destination volume must be the same storage class as the source
I would like to work on this. /assign
Sorry my bad.. Thanks for pointing it.
/remove-triage needs-information

Related discussion:
text: * Cloning support is only available for dynamic provisioners. * CSI drivers may or may not have implemented the volume cloning functionality. * You can only clone a PVC when it exists in the same namespace as the destination PVC (source and destination must be in the same namespace). <del> * Cloning is only supported within the same Storage Class. - Destination volume must be the same storage class as the source - Default storage class can be used and storageClassName omitted in the spec </del> <ins> * Cloning is supported with a different Storage Class. - Destination volume can be the same or a different storage class as the source. - Default storage class can be used and storageClassName omitted in the spec. </ins> * Cloning can only be performed between two volumes that use the same VolumeMode setting (if you request a block mode volume, the source MUST also be block mode)
Code change:
/kind documentation /sig docs Bash Auto Completion has a missing step to enable autocompletion in current shell session If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. To enable autocompletion in current session of shell, source the file:
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
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /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
/assign
/assign

Related discussion:
text: {{< /note >}} Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. <ins> To enable bash autocompletion in current session of shell, source the ~/.bashrc file: ```bash source ~/.bashrc ``` </ins>
Code change:
I will submit the PR as well Problem: Steps to reproduce this will result in the following error: Proposed Solution: Remove the 1st key which was used for doing repogpgkey check however since the repogpgcheck option got removed so this 1st key is no longer used/needed. So this would be the fix: Page to Update:
/assign
/triage accepted

Related discussion:
text: baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch enabled=1 gpgcheck=1 <del> gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </del> <ins> gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </ins> exclude=kubelet kubeadm kubectl EOF
Code change:
I will submit the PR as well Problem: Steps to reproduce this will result in the following error: Proposed Solution: Remove the 1st key which was used for doing repogpgkey check however since the repogpgcheck option got removed so this 1st key is no longer used/needed. So this would be the fix: Page to Update:
/assign
/triage accepted

Related discussion:
text: baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch enabled=1 gpgcheck=1 <del> gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </del> <ins> gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </ins> EOF sudo yum install -y kubectl ```
Code change:
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: states that kind requires Docker. This isn't right as I understand it; you can actually use with Podman, even if you don't have Docker installed at all. Proposed Solution: check what's right update the docs to match the truth Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
/assign
according to my knowledge we can use Buildah for managing container images and Podman for managing containers if someone is looking for an alternative to docker. But these can be used only on Linux, so for windows or mac a Linux VM will be used to run these and I am thinking to put this in a note. Your suggestions?
(yes) Also see Kubernetes itself doesn't require any of the listed tools (Podman, Docker, Buildah); for example, you might use CRI-O and runsc and the kubelet, but no Docker Engine.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
/triage accepted
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
Podman now has documentation on how to work with the and plug-ins: https://podman-
/assign

Related discussion:
text: ## kind [`kind`](https://kind.sigs.k8s.io/) lets you run Kubernetes on <del> your local computer. This tool requires that you have [Docker](https://docs.docker.com/get-docker/) installed and configured. </del> <ins> your local computer. This tool requires that you have either [Docker](https://www.docker.com/) or [Podman](https://podman.io/) installed. </ins> The kind [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/) page shows you what you need to do to get up and running with kind.
Code change:
Problem: The text on redirects to the correct link should be For the problem, check the page . Proposed Solution: It should resolve this issue by removing the context link and editing the text to enhance the document line. Page to Update: Update the link on text vSphereVolume CSI migration as and not 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 redirects to the correct link should be It should resolve this issue by removing the context link and editing the text to enhance the document line. /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

Related discussion:
text: - [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com` - [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume` <del> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#csi-migration-5). </del> <ins> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration). </ins> #### CSI Provisioner {#vsphere-provisioner-csi}
Code change:
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: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.
/triage accepted
/assign

Related discussion:
text: The value for this annotation must be **true** to take effect. This annotation indicates that pods running as this service account may only reference Secret API objects specified in the service account's `secrets` field. <ins> ### node.kubernetes.io/exclude-from-external-load-balancer Example: `node.kubernetes.io/exclude-from-external-load-balancer` Used on: Node Kubernetes automatically enables the `ServiceNodeExclusion` feature gate on the clusters it creates. With this feature gate enabled on a cluster, you can add labels to particular worker nodes to exclude them from the list of backend servers. The following command can be used to exclude a worker node from the list of backend servers in a backend set- `kubectl label nodes <node-name> node.kubernetes.io/exclude-from-external-load-balancers=true` </ins> ### controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost} Example: `controller.kubernetes.io/pod-deletion-cost: "10"`
Code change:
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: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.
/triage accepted
/assign

Related discussion:
text: Example: `node.kubernetes.io/out-of-service:NoExecute` <del> A user can manually add the taint to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach` </del> <ins> A user can manually add the taint to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach` </ins> [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on <del> `kube-controller-manager`, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. </del> <ins> `kube-controller-manager`, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. </ins> {{< caution >}} Refer to
Code change:
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: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.
/triage accepted
/assign

Related discussion:
text: {{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}} is being created from a VolumeSnapshot. <del> Refer to [Converting the volume mode of a Snapshot](/docs/concepts/storage/volume-snapshots/#convert-volume-mode) </del> <ins> Refer to [Converting the volume mode of a Snapshot](/docs/concepts/storage/volume-snapshots/#convert-volume-mode) </ins> and the [Kubernetes CSI Developer Documentation](https://kubernetes-csi.github.io/docs/) for more information. ## Annotations used for audit