jiebi/CodeConvo huggingface dataset:
Change:
1. Expiration/certificate lifetime - minimum of CSR signer or request. 1. CA bit allowed/disallowed - not allowed. <del> 1. `kubernetes.io/legacy-unknown`:  has no guarantees for trust at all. Some distributions may honor these as client certs, but that behavior is not standard Kubernetes behavior. </del> <ins> 1. `kubernetes.io/legacy-unknown`:  has no guarantees for trust at all. Some third-party distributions of Kubernetes may honor client certificates signed by it. The stable CertificateSigningRequest API (version `certificates.k8s.io/v1` and later) does not allow to set the `signerName` as `kubernetes.io/legacy-unknown`. </ins> Never auto-approved by {{< glossary_tooltip term_id="kube-controller-manager" >}}. 1. Trust distribution: None.  There is no standard trust or distribution for this signer in a Kubernetes cluster. 1. Permitted subjects - any

Discussion:
This is a Bug Report Problem: Doc is not aligned with latest kubernetes version 1.19.2: With version 1.19.2, is mandatory. Also signer is not supported in the list at: Proposed Solution: Specify in yaml definition Remove section Page to Update:
Just checked, the is a required field since 1.19.0 in group, but it is not required in the group. It makes sense to fix the example so that the YAML works. /sig auth
changed the apiVersion without actually updating required fields for v1
cc
About proposal "Remove section" of this issue, the v1.19 release notes indicates: Ref: Can you create a PR for this?
The documentation should remain until v1beta1 is no longer supported
I am happy to create a PR, but I am not able to push a branch to this repo. I have already signed CLA but still get: Any idea? Did I miss something in contribution doc? I will have a look at that again.
push it to your own clone, then use github to raise a pull request.
Great thanks. PR on the way then. :)
Change:
matchLabels: app: myapp policyTypes: <del> - Egress </del> <ins> - Egress </ins> egress: <del> - to: - namespaceSelector: matchExpressions: - key: namespace operator: In values: ["frontend", "backend"] </del> <ins> - to: - namespaceSelector: matchExpressions: - key: namespace operator: In values: ["frontend", "backend"] </ins> ``` {{< note >}}

Discussion:
There is minor fault in the webpage : The indent is wrong egress: to: namespaceSelector: matchExpressions: key: namespace operator: In values: ["frontend", "backend"] This fault only exist in the chinese version of this page, it should be corrected as english version as below: egress: to: namespaceSelector: matchExpressions: key: namespace operator: In values: ["frontend", "backend"]
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
Why would you say it is "wrong"? List items can be indented in either way.
I created two versions yaml, 1.yaml for chinese version and 2.yaml for english version: ! So matchExpressions should be indented. Meanwhile, although one whitespace indent is ok in yaml, it's good to use two whitespace indent as habits of most people.
I agree with the observations regarding the indentation in the Chinese version of the documentation and think it needs a fix.
/language zh /sig docs /sig node
Please paste your snippet into a code block, i.e. your yaml here ` I can guess what you are suggesting here, but need a confirmation.
Please check if is the fix you are suggesting.
Yes, I think it's fixed, thank you!
Change:
## Additional Links <del> * **Goals and Non-Goals**: For the goals and non-goals of the Minikube project, please see our [roadmap](https://git.k8s.io/minikube/docs/contributors/roadmap.md). * **Development Guide**: See [CONTRIBUTING.md](https://git.k8s.io/minikube/CONTRIBUTING.md) for an overview of how to send pull requests. * **Building Minikube**: For instructions on how to build/test Minikube from source, see the [build guide](https://git.k8s.io/minikube/docs/contributors/build_guide.md). * **Adding a New Dependency**: For instructions on how to add a new dependency to Minikube, see the [adding dependencies guide](https://git.k8s.io/minikube/docs/contributors/adding_a_dependency.md). * **Adding a New Addon**: For instructions on how to add a new addon for Minikube, see the [adding an addon guide](https://git.k8s.io/minikube/docs/contributors/adding_an_addon.md). </del> <ins> * **Goals and Non-Goals**: For the goals and non-goals of the Minikube project, please see our [roadmap](https://minikube.sigs.k8s.io/docs/contrib/roadmap/). * **Development Guide**: See [Contributing](https://minikube.sigs.k8s.io/docs/contrib/) for an overview of how to send pull requests. * **Building Minikube**: For instructions on how to build/test Minikube from source, see the [build guide](https://minikube.sigs.k8s.io/docs/contrib/building/). * **Adding a New Dependency**: For instructions on how to add a new dependency to Minikube, see the [adding dependencies guide](https://minikube.sigs.k8s.io/docs/contrib/drivers/). * **Adding a New Addon**: For instructions on how to add a new addon for Minikube, see the [adding an addon guide](https://minikube.sigs.k8s.io/docs/contrib/addons/). </ins> * **MicroK8s**: Linux users wishing to avoid running a virtual machine may consider [MicroK8s](https://microk8s.io/) as an alternative. ## Community

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 some broken links in the "Managing your Cluster", "Additional Links" sections. Managing your Cluster section: Line: 336 -This page has gone. I couldn't find any documents about upgrading minikube on macos. This issue was already opened via . Additional Links section: Proposed Solution: Additional Links section: roadmap: (I think the link title should be changed to "Contributing") build guide: adding dependencies guide: (I'm not sure actually...) adding an addon guide: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign
Change:
# containerd 재시작 systemctl restart containerd ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} ### systemd

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/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

Discussion:
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
Change:
both version before the node is upgraded in order to guarantee that device allocations continue to complete successfully during the upgrade. <del> Refer to [API compatiblity](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#api-compatibility) and [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions/) for more details. </del> <ins> Refer to [API compatibility](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#api-compatibility) and [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions/) for more details. </ins>  No newline at end of file

Discussion:
This is a Bug Report Problem: Links for API compatibility and Kubelet Device Manager API Versions under in task are Invalid. It gives a 404 Page not found error. Proposed Solution: For API compatibility the link should be: For Kubelet Device Manager API Versions the link should be: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /sig docs
Fixed it here
/triage accepted
Change:
or aggregated API servers, to extend the default roles. For example: the following ClusterRoles let the "admin" and "edit" default roles manage the custom resource <del> named CronTab, whereas the "view" role can perform just read actions on CronTab resources. </del> <ins> named CronTab, whereas the "view" role can perform only read actions on CronTab resources. </ins> You can assume that CronTab objects are named `"crontabs"` in URLs as seen by the API server. --> 默认的[面向用户的角色](#default-roles-and-role-bindings) 使用 ClusterRole 聚合。

Discussion:
! ! There is a problem with the Chinese version translated here, it should be in the "development" namespace.
/triage accepted /kind bug /assign
/language zh
Change:
--- title: Tutorial interativo - implantando um aplicativo weight: 20 <ins> headless: true toc_hide: true _build: list: never publishResources: false </ins> --- <!DOCTYPE html> <del> <html lang="en"> </del> <ins> <html lang="pt-BR"> </ins> <body>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
[gRPC](https://grpc.io) protocol for the communication between the [cluster components](/docs/concepts/overview/components/#node-components) {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and <del> ￼{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}. </del> <ins> {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}. </ins>

Discussion:
I am being shown on the page. This is in the last paragraph before the API heading. This may be a small bug and can be removed easily in the text. I can see this both on Chrome and Mozilla Firefox on Ubuntu 20.04. Attaching a Screenshot. Look at the bottom right in this image. ! PS. I can look into this.
/triage accepted /kind bug /good-first-issue looks like a problem with
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /kind bug /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
Change:
description: "Snippets to be included in the main kubectl-installs-*.md pages." headless: true toc_hide: true <ins> _build: list: never render: never publishResources: false </ins> ---  No newline at end of file

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 source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Proposed Solution: Edit every file within : Page to Update: and its contents /area web-development /help /priority backlog /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Edit every file within : Page to Update: and its contents /help /priority backlog /good-first-issue </details
/retitle Include files for install are rendered and served /triage accepted
/assign
/unassign
Thanks !
Change:
## {{% heading "whatsnext" %}} <del> - Read [Debugging DNS Resolution](/docs/tasks/debug-application-cluster/dns-debugging-resolution/) </del> <ins> - Read [Debugging DNS Resolution](/docs/tasks/administer-cluster/dns-debugging-resolution/) </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: On page is 404: Proposed Solution: Find correct link and update the url Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Seems it should be this... I'll update it and submit a PR /assign
Change:
* To specify resources with one or more files:  `-f file1 -f file2 -f file<#>` * [Use YAML rather than JSON](/docs/concepts/configuration/overview/#general-configuration-tips) since YAML tends to be more user-friendly, especially for configuration files.<br/> <del> Example: `kubectl get pod -f ./pod.yaml` </del> <ins> Example: `kubectl get -f ./pod.yaml` </ins> * `flags`: Specifies optional flags. For example, you can use the `-s` or `--server` flags to specify the address and port of the Kubernetes API server.<br/>

Discussion:
Example: kubectl get pod -f error: when paths, URLs, or stdin is provided as input, you may not specify resource arguments as well The example should be "kubectl get -f ".
/triage accepted /kind bug /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 : /triage accepted /kind bug /help 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
Change:
<tr> <td style="white-space: nowrap">Host Ports</td> <td> <del> <p>HostPorts should be disallowed, or at minimum restricted to a known list.</p> </del> <ins> <p>HostPorts should be disallowed entirely (recommended) or restricted to a known list</p> </ins> <p><strong>Restricted Fields</strong></p> <ul> <li><code>spec.containers[*].ports[*].hostPort</code></li>

Discussion:
This is a Feature Request "Host Ports" rule have the following description "HostPorts should be disallowed, or at minimum restricted to a known list." It is not clear for the reader that this statement is composed from two mutually exclusive terms "HostPorts should be disallowed” OR “HostPorts should be restricted to a known list." Additionally, it is not clear that Pod Security Admission Controller implements the first option and the second one is for 3rd party controllers like Gatekeeper/Kyverno. What would you like to be "Host Ports" rule can be rephrased so it is clear that it consist of two mutually exclusive options. Or it be divided into two separate rules (two rows in the table). doc or/and doc should clearly state which "Host Ports" option is implemented by the "Pod Security Admission" Why is this needed Pod Security Standards doc can mislead user. Comments
/language en /sig security
/sig auth
/remove-kind feature /kind bug
If we're updating the PSA doc, we should perhaps work with sig-auth ( maybe) to identify if there are other Pod Security Standards where PSA only enforces a specific condition or behaviour by default.
Yes, I agree. I'd be OK with just change this to "HostPorts should be disallowed". The standards used to include more optional restrictions, but we've been making them more opinionated (and aligned with the PSA implementation) over time.
/triage accepted
/assign
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
For the adventurous contributor looking for a good issue, here's what you need to do: In the Host Ports row in , replace the first sentence with "HostPorts should be disallowed." For instructions to edit a page and create a PR, use in our contributor guide /help-wanted
Change:
--- {{< note >}} <del> El autocompletado para Fish necesita de kubectl versión 1.23 o superior. </del> <ins> Se requiere kubectl 1.23 o superior para utilizar el autocompletado de Fish. </ins> {{< /note >}} <del> El script de autocompletado de Fish para kubectl puede ser generado con el comando `kubectl completion fish`. Ejecutando este comando en tu shell habilitará el autocompletado de kubectl para Fish. </del> <ins> El script de autocompletado de Fish puede ser generado con el comando `kubectl completion fish`. Leyendo este archivo en su Shell habilita el autocompletado de kubectl. </ins> <del> Para qué funcione en sus futuras sesiones shell, debes agregar la siguiente línea al archivo `~/.config/fish/config.fish`: </del> <ins> Para hacer esto en todas sus sesiones agregue la siguiente linea a su archivo `~/.config/fish/config.fish`: </ins> ```shell kubectl completion fish | source

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs
/assign
Change:
openssl genrsa -out ca.key 2048 <del> <!-- 1.  According to the ca.key generate a ca.crt (use -days to set the certificate effective time): --> 1.  在 ca.key 文件的基础上，生成 ca.crt 文件（用参数 -days 设置证书有效期） </del> <ins> <!-- 2.  According to the ca.key generate a ca.crt (use -days to set the certificate effective time): --> 2.  在 ca.key 文件的基础上，生成 ca.crt 文件（用参数 -days 设置证书有效期） </ins> openssl req -x509 -new -nodes -key ca.key -subj "/CN=${MASTER_IP}" -days 10000 -out ca.crt <del> <!-- 1.  Generate a server.key with 2048bit: --> 1.  生成一个 2048 位的 server.key 文件： </del> <ins> <!-- 3.  Generate a server.key with 2048bit: --> 3.  生成一个 2048 位的 server.key 文件： </ins> openssl genrsa -out server.key 2048 <del> <!-- 1.  Create a config file for generating a Certificate Signing Request (CSR). Be sure to substitute the values marked with angle brackets (e.g. `<MASTER_IP>`) with real values before saving this to a file (e.g. `csr.conf`). Note that the value for `MASTER_CLUSTER_IP` is the service cluster IP for the API server as described in previous subsection. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 1.  创建一个用于生成证书签名请求（CSR）的配置文件。 </del> <ins> <!-- 4.  Create a config file for generating a Certificate Signing Request (CSR). Be sure to substitute the values marked with angle brackets (e.g. `<MASTER_IP>`) with real values before saving this to a file (e.g. `csr.conf`). Note that the value for `MASTER_CLUSTER_IP` is the service cluster IP for the API server as described in previous subsection. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 4.  创建一个用于生成证书签名请求（CSR）的配置文件。 </ins> 保存文件（例如：`csr.conf`）前，记得用真实值替换掉尖括号中的值（例如：`<MASTER_IP>`）。 注意：`MASTER_CLUSTER_IP` 就像前一小节所述，它的值是 API 服务器的服务集群 IP。 下面的例子假定你的默认 DNS 域名为 `cluster.local`。

Discussion:
Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.