jiebi/CodeConvo huggingface dataset:
Change:
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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed mentions: (it's also OK to change to the correct case) Comments /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
/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
/assign

Discussion:
The exact versions for below mapping table are for docker cli v1.40 and crictl v1.19.0. Please note that the list is not exhaustive. For example, it doesn't include experimental commands of docker cli. <ins> {{< note >}} </ins> Warn: the output format of CRICTL is similar to Docker CLI, despite some missing columns for some CLI. Make sure to check output for the specific command if your script output parsing. <ins> {{< /note >}} </ins> ### Retrieve Debugging Information
Change:
Out of tree developing instructions are now out of date. reference leads to a 404.
The fix, I think, is to change the hyperlink to be /kind bug /priority backlog /triage accepted /language en /sig api-machinery /sig cloud-provider
/assign

Discussion:
To build an out-of-tree cloud-controller-manager for your cloud: 1. Create a go package with an implementation that satisfies [cloudprovider.Interface](https://github.com/kubernetes/cloud-provider/blob/master/cloud.go). <del> 2. Use [`main.go` in cloud-controller-manager](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/controller-manager.go) from Kubernetes core as a template for your `main.go`. As mentioned above, the only difference should be the cloud package that will be imported. </del> <ins> 2. Use [`main.go` in cloud-controller-manager](https://github.com/kubernetes/kubernetes/blob/master/cmd/cloud-controller-manager/main.go) from Kubernetes core as a template for your `main.go`. As mentioned above, the only difference should be the cloud package that will be imported. </ins> 3. Import your cloud package in `main.go`, ensure your package has an `init` block to run [`cloudprovider.RegisterCloudProvider`](https://github.com/kubernetes/cloud-provider/blob/master/plugins.go). Many cloud providers publish their controller manager code as open source. If you are creating
Change:
RuntimeClass feature gate is GA in 1.20. According to , a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.
triage/accepted
/language en
/triage accepted
/assign

Discussion:
## Setup <del> Ensure the RuntimeClass feature gate is enabled (it is by default). See [Feature Gates](/docs/reference/command-line-tools-reference/feature-gates/) for an explanation of enabling feature gates. The `RuntimeClass` feature gate must be enabled on API server _and_ kubelets. 1. Configure the CRI implementation on nodes (runtime dependent). 2. Create the corresponding RuntimeClass resources. </del> <ins> 1. Configure the CRI implementation on nodes (runtime dependent) 2. Create the corresponding RuntimeClass resources </ins> ### 1. Configure the CRI implementation on nodes

{{< feature-state for_k8s_version="v1.16" state="beta" >}} <del> As of Kubernetes v1.16, RuntimeClass includes support for heterogeneous clusters through its `scheduling` fields. Through the use of these fields, you can ensure that pods running with this RuntimeClass are scheduled to nodes that support it. To use the scheduling support, you must have the [RuntimeClass admission controller](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass) enabled (the default, as of 1.16). </del> <ins> By specifying the `scheduling` field for a RuntimeClass, you can set constraints to ensure that Pods running with this RuntimeClass are scheduled to nodes that support it. If `scheduling` is not set, this RuntimeClass is assumed to be supported by all nodes. </ins> To ensure pods land on nodes supporting a specific RuntimeClass, that set of nodes should have a common label which is then selected by the `runtimeclass.scheduling.nodeSelector` field. The

- [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md#runtimeclass-scheduling) - Read about the [Pod Overhead](/docs/concepts/scheduling-eviction/pod-overhead/) concept - [PodOverhead Feature Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md)
Change:
Problem: The documentation references loading the overlay and brnetfilter kernel modules at both of these locations: Modules do not persist reboots Documentation states that they will persist across reboots. Cluster will fail pre-flight if modules are not loaded Proposed Solution: In installation prerequisites add: cat <<EOF | sudo tee /etc/modules- overlay brnetfilter EOF This is correct in the containerd installation prerequisites but appears missing from CRI-O. Modules do not appear to persist across reboots unless /etc/modules-load.d has a config reference to load at boot. In the example given at add: cat <<EOF | sudo tee /etc/modules- br_netfilter EOF
a PR with the fix is welcome. /sig node cluster-lifecycle /triage accepted
Thank you PRs submitted.
please close this once the PRs merge. or add in one of the PR descriptions.

Discussion:
Install and configure prerequisites: ```shell <ins> # Create the .conf file to load the modules at bootup cat <<EOF | sudo tee /etc/modules-load.d/crio.conf overlay br_netfilter EOF </ins> sudo modprobe overlay sudo modprobe br_netfilter
Change:
No content in this page. !
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language zh /kind bug BTW the fix for this is to copy the redirect that's configured for the English version of the page.
/assign

Discussion:
/docs/setup/minikube/     /docs/tasks/tools/ 302 /docs/setup/learning-environment/     /docs/tasks/tools/  302! <ins> /zh/docs/setup/learning-environment/     /zh/docs/tasks/tools/  302! </ins> /docs/setup/learning-environment/kind/  /docs/tasks/tools/  302 /docs/setup/learning-environment/minikube/  /docs/tasks/tools/ 302 /docs/setup/cri/     /docs/setup/production-environment/container-runtimes/   301
Change:
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 The site '' does not list RHEL 8 or CentOS 8 as a supported os. Only RHEL 7 / CentOS 7 is listed. Both os versions released over a year ago and Google provides a lot of guides for how to install Kubernetes on CentOS 8. Please a) add RHEL 8 / CentOS 8 to the list of supported platforms or b) if there is a reason for this, explain it on the website. Why is this needed It is confusing when only an old os version ist supported without any further explanation. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /sig cluster-lifecycle /help
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 : it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /help </details
/triage accepted
/kind feature /retitle Document kubeadm for RHEL 8
I had a look at it and sent in a pull request for this. Add forward compatibility in RHEL / CentOS to the list of supported platforms.
/assign

Discussion:
* One or more machines running one of: - Ubuntu 16.04+ - Debian 9+ <del> - CentOS 7 - Red Hat Enterprise Linux (RHEL) 7 </del> <ins> - CentOS 7+ - Red Hat Enterprise Linux (RHEL) 7+ </ins> - Fedora 25+ - HypriotOS v1.0.1+ - Flatcar Container Linux (tested with 2512.3.0)
Change:
Link to PodOverhead Design is not working and resulting in 404.
/triage accepted /assign
/language en
/sig scheduling /close Fixed in PR
Closing this issue. <detailsIn response to : /sig scheduling /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

Discussion:
* [RuntimeClass](/docs/concepts/containers/runtime-class/) <del> * [PodOverhead Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md) </del> <ins> * [PodOverhead Design](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/688-pod-overhead) </ins>
Change:
"The works with the NGINX webserver (as a proxy)." The URL given against the text "NGINX Ingress Controller for Kubernetes" is not working. It returned 404 error(Page not found) in my case.
/triage accepted /kind cleanup

Discussion:
is an [Istio](https://istio.io/) based ingress controller. * The [Kong Ingress Controller for Kubernetes](https://github.com/Kong/kubernetes-ingress-controller#readme) is an ingress controller driving [Kong Gateway](https://konghq.com/kong/). <del> * The [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx/kubernetes-ingress-controller) </del> <ins> * The [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx-ingress-controller/) </ins> works with the [NGINX](https://www.nginx.com/resources/glossary/nginx/) webserver (as a proxy). * [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress, designed as a library to build your custom proxy. * The [Traefik Kubernetes Ingress provider](https://doc.traefik.io/traefik/providers/kubernetes-ingress/) is an
Change:
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

Discussion:
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,
Change:
is a 404. It's the fourth result when and also a common Google search result for anything relating to node labels. Originally posted by in I believe this is related to
/triage accepted
/assign
/kind cleanup

Discussion:
/docs/reference/kubernetes-api/api-index/ /docs/reference 301 <ins> /docs/reference/kubernetes-api/labels-annotations-taints/ /docs/reference/labels-annotations-taints/ 301 </ins> /docs/reporting-security-issues/     /security/ 301 /docs/roadmap/     https://github.com/kubernetes/kubernetes/milestones/ 301
Change:
Hi, This command does not exist for kompose I'm using version 1.22 and there is no such command.
This looks like a report for The fix I recommend is to remove the list item, currently numbered 2 in the rendered page, that starts /language en /good-first-issue /kind bug /triage accepted /priority backlog Thanks
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 : This looks like a report for Run the kompose up command to deploy to Kubernetes directly, or skip to the next step instead to generate a file to use with kubectl. /good-first-issue /kind bug /triage accepted /priority backlog 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
+1 to remove the list item, I would like to work on it. /assign
If you have time, this task page could use some cleanup of the markup.

Discussion:
kompose.service.type: LoadBalancer ``` <del> 2.  Run the `kompose up` command to deploy to Kubernetes directly, or skip to the next step instead to generate a file to use with `kubectl`. ```bash $ kompose up We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application. If you need different kind of resources, use the 'kompose convert' and 'kubectl apply -f' commands instead. INFO Successfully created Service: redis INFO Successfully created Service: web INFO Successfully created Deployment: redis INFO Successfully created Deployment: web Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details. ``` 3.  To convert the `docker-compose.yml` file to files that you can use with </del> <ins> 2.  To convert the `docker-compose.yml` file to files that you can use with </ins> `kubectl`, run `kompose convert` and then `kubectl apply -f <output file>`. ```bash

Your deployments are running in Kubernetes. <del> 4.  Access your application. </del> <ins> 3.  Access your application. </ins> If you're already using `minikube` for your development process:
Change:
This is a Feature Request translate /docs/tasks/administer-cluster/migrating-from- into Chinese What would you like to be /zh/docs/tasks/administer-cluster/migrating-from-dockershim/index.m /assign /language 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

Discussion:
<ins> --- title: "从 dockershim 迁移" weight: 10 content_type: task --- <!-- 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. --> 本节提供从 dockershim 迁移到其他容器运行时的必备知识。 <!-- 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/) --> 自从 Kubernetes 1.20 宣布 [弃用 dockershim](/zh/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation)， 各类疑问随之而来：这对各类工作负载和 Kubernetes 部署会产生什么影响。 你会发现这篇博文对于更好地理解此问题非常有用： [弃用 Dockershim 常见问题](/zh/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. --> 建议从 dockershim 迁移到其他替代的容器运行时。 请参阅[容器运行时](/zh/docs/setup/production-environment/container-runtimes/) 一节以了解可用的备选项。 当在迁移过程中遇到麻烦，请[上报问题](https://github.com/kubernetes/kubernetes/issues)。 那么问题就可以及时修复，你的集群也可以进入移除 dockershim 前的就绪状态。 </ins>
Change:
The specific location of the document is The documentation says You can acquire all these from the nginx https example. This requires having go and make tools installed. The link of the Chinese document is: he cannot access the link of the English document is: accessible
/triage accepted /language zh /kind bug
/assign

Discussion:
* 使用证书配置的 Nginx 服务器 * 使证书可以访问 Pod 的 [Secret](/zh/docs/concepts/configuration/secret/) <del> 你可以从 [Nginx https 示例](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/staging/https-nginx/) </del> <ins> 你可以从 [Nginx https 示例](https://github.com/kubernetes/examples/tree/{{< param "githubbranch" >}}/staging/https-nginx/) </ins> 获取所有上述内容。你需要安装 go 和 make 工具。如果你不想安装这些软件，可以按照 后文所述的手动执行步骤执行操作。简要过程如下：
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--Proposed Solution: in this page is linked to a dead url. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /sig node /language en /triage accepted Rather than linking to a KEP, we should really add a new page to the documentation (maybe in Concepts, maybe in Reference) and then link to that.
The fail link in Support Device Monitoring due to . This root cause in the kind/bug is the repo of kubernetes/enhancements url that move to . I had a look at it and sent in a pull request for fix this.(PR ) /assign
/close
Closing this issue. <detailsIn response to : /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

Discussion:
- `KubeletCredentialProviders`: Enable kubelet exec credential providers for image pull credentials. - `KubeletPluginsWatcher`: Enable probe-based plugin watcher utility to enable kubelet to discover plugins such as [CSI volume drivers](/docs/concepts/storage/volumes/#csi). <del> - `KubeletPodResources`: Enable the kubelet's pod resources GRPC endpoint. See [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/compute-device-assignment.md) </del> <ins> - `KubeletPodResources`: Enable the kubelet's pod resources gRPC endpoint. See [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/606-compute-device-assignment/README.md) </ins> for more details. - `LegacyNodeRoleBehavior`: When disabled, legacy behavior in service load balancers and node disruption will ignore the `node-role.kubernetes.io/master` label in favor of the
Change:
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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --The is lacking clarity that both the port name or port number can be used when proxying to a service. The documentation should mention the field represented by can either be the name of a port in a service or the port number of a service for both forms and . Why is this needed The apiserver proxy endpoint supports using either a to locate the service to proxy to. The alternative form of using the port number could be useful if migrating from an unnamed/default service port to a named service port. Example: The following api server request could be used to proxy either form of the following service object since it references the port number, . If the query was constructed as , only the unnamed port would return a result. Conversely, if was used in the query only the named port would return a result. default/unnamed: named: Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/kind cleanup
/triage accepted
/priority backlog

Discussion:
As mentioned above, you use the `kubectl cluster-info` command to retrieve the service's proxy URL. To create proxy URLs that include service endpoints, suffixes, and parameters, you append to the service's proxy URL: `http://`*`kubernetes_master_address`*`/api/v1/namespaces/`*`namespace_name`*`/services/`*`service_name[:port_name]`*`/proxy` <del> If you haven't specified a name for your port, you don't have to specify *port_name* in the URL. </del> <ins> If you haven't specified a name for your port, you don't have to specify *port_name* in the URL. You can also use the port number in place of the *port_name* for both named and unnamed ports. </ins> By default, the API server proxies to your service using http. To use https, prefix the service name with `https:`: `http://`*`kubernetes_master_address`*`/api/v1/namespaces/`*`namespace_name`*`/services/`*`https:service_name:[port_name]`*`/proxy`

The supported formats for the name segment of the URL are: * `<service_name>` - proxies to the default or unnamed port using http <del> * `<service_name>:<port_name>` - proxies to the specified port using http </del> <ins> * `<service_name>:<port_name>` - proxies to the specified port name or port number using http </ins> * `https:<service_name>:` - proxies to the default or unnamed port using https (note the trailing colon) <del> * `https:<service_name>:<port_name>` - proxies to the specified port using https </del> <ins> * `https:<service_name>:<port_name>` - proxies to the specified port name or port number using https </ins> ##### Examples
Change:
The host in the yaml is https- But the host in the document is
/language zh
/triage accepted /kind bug /assign

Discussion:
Name (CN), also known as a Fully Qualified Domain Name (FQDN) for `https-example.foo.com`. --> 在 Ingress 中引用此 Secret 将会告诉 Ingress 控制器使用 TLS 加密从客户端到负载均衡器的通道。 <del> 你需要确保创建的 TLS Secret 创建自包含 `sslexample.foo.com` 的公用名称（CN）的证书。 </del> <ins> 你需要确保创建的 TLS Secret 创建自包含 `https-example.foo.com` 的公用名称（CN）的证书。 </ins> 这里的公共名称也被称为全限定域名（FQDN）。 {{< note >}}