jiebi/CodeConvo huggingface dataset:
Change:
dependent resources, based on the delete permissions of the owner. This control prevents unauthorized users from delaying owner object deletion. <ins> {{< note >}} Cross-namespace owner references are disallowed by design. Namespaced dependents can specify cluster-scoped or namespaced owners. A namespaced owner **must** exist in the same namespace as the dependent. If it does not, the owner reference is treated as absent, and the dependent is subject to deletion once all owners are verified absent. Cluster-scoped dependents can only specify cluster-scoped owners. In v1.20+, if a cluster-scoped dependent specifies a namespaced kind as an owner, it is treated as having an unresolvable owner reference, and is not able to be garbage collected. In v1.20+, if the garbage collector detects an invalid cross-namespace `ownerReference`, or a cluster-scoped dependent with an `ownerReference` referencing a namespaced kind, a warning Event with a reason of `OwnerRefInvalidNamespace` and an `involvedObject` of the invalid dependent is reported. You can check for that kind of Event by running `kubectl get events -A --field-selector=reason=OwnerRefInvalidNamespace`. {{< /note >}} </ins> ## Ownership and finalizers When you tell Kubernetes to delete a resource, the API server allows the

Discussion:
The following information was dropped in and is critical to include in the garbage collection ownerReferences topic:
/triage accepted /sig api-machinery
/priority important-soon
Change:
在服务器日志中没有出现 RBAC 拒绝消息，就可以删除 ABAC 鉴权器。 <!-- <del> ## Permissive RBAC Permissions </del> <ins> ### Permissive RBAC Permissions </ins> You can replicate a permissive policy using RBAC role bindings. --> <del> ## 宽松的 RBAC 权限   {#permissive-rbac-permissions} </del> <ins> ### 宽松的 RBAC 权限   {#permissive-rbac-permissions} </ins> 你可以使用 RBAC 角色绑定在多个场合使用宽松的策略。

Discussion:
There is a translation bug: " --remove-extra-permissions" should be changed to " --remove-extra-subjects" There is a typographical bug: ,%E4%BB%8E%20ABAC%20%E5%8D%87%E7%BA%A7,-%E5%8E%9F%E6%9D%A5%E8%BF%90%E8%A1%8C%E8%BE%83 "" and " RBAC " should become subdirectory of " ABAC "
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
/assign
Change:
serving the health check at `/healthz`. You can test this: ```shell <del> kubectl get pod -o wide -l run=source-ip-app </del> <ins> kubectl get pod -o wide -l app=source-ip-app </ins> ``` The output is similar to this: ```

Discussion:
On page: Based on the labels I see in the pod, I believe that the line that says: should be changed to:
/assign
/triage accepted
/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 : /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
/language en
Change:
### Migrating to the `systemd` driver in kubeadm managed clusters <del> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </del> <ins> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/) </ins> if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters. ## Container runtimes

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In there is a table broken with GitHub Markdown renderer. ! BTW, the table is not broken with Hugo Markdown renderer. ! Proposed Solution: Page to Update: No Page on to Update. Just a Markdown file on GitHub to update. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
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
We support viewing the rendered documentation via I don't think this issue is valid.
/priority awaiting-more-evidence /langauge en
Thank for your comment. I will describe a bit more about this issue I opened. [As-is] Yes, although the second row of the Markdown code has 4 columns and other rows have 3 columns, this table is rendered alright by Hugo Markdown renderer. This is a issue about improving consistency of the number of columns in the Markdown code, regardless of the type of Markdown renderer. [To-be]

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In , the link is broken. Proposed Solution: In Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
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
already logged here: /close /sig cluster-lifecycle
Closing this issue. <detailsIn response to : already logged here: /sig cluster-lifecycle 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:
Limiting port ranges of communication | This recommendation may be a bit self-explanatory, but wherever possible you should only expose the ports on your service that are absolutely essential for communication or metric gathering. | 3rd Party Dependency Security | It is a good practice to regularly scan your application's third party libraries for known security vulnerabilities. Each programming language has a tool for performing this check automatically. | Static Code Analysis | Most languages provide a way for a snippet of code to be analyzed for any potentially unsafe coding practices. Whenever possible you should perform checks using automated tooling that can scan codebases for common security errors. Some of the tools can be found at: https://owasp.org/www-community/Source_Code_Analysis_Tools | <del> Dynamic probing attacks | There are a few automated tools that you can run against your service to try some of the well known service attacks. These include SQL injection, CSRF, and XSS. One of the most popular dynamic analysis tools is the [OWASP Zed Attack proxy](https://owasp.org/www-project-zap/) tool. | </del> <ins> Dynamic probing attacks | There are a few automated tools that you can run against your service to try some of the well known service attacks. These include SQL injection, CSRF, and XSS. One of the most popular dynamic analysis tools is the [OWASP Zed Attack proxy](https://www.zaproxy.org/) tool. | </ins> {{< /table >}}

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 link to in the code security section of leads to a 404 error. Proposed Solution: Replace the link with a working one or remove it. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig security /triage accepted
can we use the following link for ZAP: The above link redirects to the ZAP website.
cc your thoughts on this
/assign
Change:
description: Browse terminology, command line syntax, API resource types, and setup tool documentation. button: View Reference button_path: /docs/reference <del> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </del> - name: contribute title: Contribute to Kubernetes description: Anyone can contribute, whether you're new to the project or you've been around a long time. button: Find out how to help button_path: /docs/contribute <ins> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </ins> - name: Download title: Download Kubernetes description: Install Kubernetes or upgrade to the newest version.

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:
--> ## 将 ConfigMap 数据添加到一个卷中 <del> 如基于文件创建 ConfigMap](#create-configmaps-from-files) 中所述，当你使用 </del> <ins> 如基于文件创建 [ConfigMap](#create-configmaps-from-files) 中所述，当你使用 </ins> `--from-file` 创建 ConfigMap 时，文件名成为存储在 ConfigMap 的 `data` 部分中的键， 文件内容成为键对应的值。

Discussion:
! ‘ ConfigMap](#create-configmaps-from-files) ’
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:
1. Install the [Google Cloud SDK](https://cloud.google.com/sdk/). <del> 2. Run the `kubectl` installation command: </del> <ins> 1. Run the `kubectl` installation command: </ins> ```shell gcloud components install kubectl ``` <del> 3. Test to ensure the version you installed is up-to-date: </del> <ins> 1. Test to ensure the version you installed is up-to-date: </ins> ```shell kubectl version --client

Discussion:
There are no details or instructions on how to validate the binary downloaded from this page via some form of checksum, sha256 or otherwise. For automation purposes, eg. ansible playbook, being able to validate any binary downloads is a requirement of project stakeholders.
The site doesn't allow browsing, but the file is there as kubectl.sha256 afterall. Might be worth mentioning this in the document?
/retitle Document how to validate kubectl binary against checksum / signature /language en /kind feature /triage accepted The page in question is
To fix this: update to use download links from for example also explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere for example The and shortcodes are useful for automatically filling in the current Kubernetes version. /help /sig cli
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 : To fix this: update to use download links from explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere /sig cli 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
I may be able to help with this /assign
Change:
title: Create a Cluster weight: 10 --- <ins> Learn about Kubernetes {{< glossary_tooltip text="cluster" term_id="cluster" length="all" >}} and create a simple cluster using Minikube. </ins>

Discussion:
It would be nice to have a bit of text about what a cluster is, cuz I don't know what it does in kubernetes.
Someone might add a link to in .
The let you automatically include the existing explanation of what a cluster is. That ought to help too.
/language en /help /triage accepted
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 : /language en /help /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
We could also link to and
/sig cluster-lifecycle
/assign
/unassign Unassign myself since is already working on this issue. Thanks.
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten
/sig docs
you may have a look at . I think it will help you to understand, what the cluster is! Thank you.
Change:
- Blog posts should be relevant to Kubernetes users. - Topics related to participation in or results of Kubernetes SIGs activities are always on <del> topic (see the work in the [Upstream Marketing Team](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/blog-guidelines.md#upstream-marketing-blog-guidelines) </del> <ins> topic (see the work in the [Contributor Comms Team](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/blog-guidelines.md#upstream-marketing-blog-guidelines) </ins> for support on these posts). - The components of Kubernetes are purposely modular, so tools that use existing integration points like CNI and CSI are on topic.

Discussion:
Problem: The text on 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 Upstream Marketing Team 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 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 Upstream Marketing Team 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
/triage accepted
Change:
该准入控制器保护对 `metadata.ownerReferences` 对象的访问，以便只有对该对象具有 “删除” 权限的用户才能对其进行更改。该准入控制器还保护对 `metadata.ownerReferences[x].blockOwnerDeletion` 对象的访问，以便只有对所引用的 **属主（owner）** 的 `finalizers` 子资源具有 “更新” 权限的用户才能对其进行更改。 <del> ### PersistentVolumeLabel {#persistentvolumelabel} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### PersistentVolumeLabel {#persistentvolumelabel} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> <!-- This admission controller automatically attaches region or zone labels to PersistentVolumes

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
<!--more--> <del> [HostAliases](/docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-corev) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods. </del> <ins> [HostAliases](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods. </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: is out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue
I'll work on that! /remove-help /assign
Change:
--- title: アプリケーションのトラブルシューティング <del> description: Debugging common containerized application issues. </del> <ins> description: コンテナ化されたアプリケーションの一般的な問題をデバッグします。 </ins> weight: 20 --- <del> This doc contains a set of resources for fixing issues with containerized applications. It covers things like common issues with Kubernetes resources (like Pods, Services, or StatefulSets), advice on making sense of container termination messages, and ways to debug running containers. </del> <ins> このドキュメントには、コンテナ化されたアプリケーションの問題を解決するための、一連のリソースが記載されています。Kubernetesリソース(Pod、Service、StatefulSetなど)に関する一般的な問題や、コンテナ終了メッセージを理解するためのアドバイス、実行中のコンテナをデバッグする方法などが網羅されています。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate content/ja/docs/tasks/debug/debug- into Japanese. Why is this needed This file is only translated the title, not translated the description and the body text. Comments /language ja
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:
### Submitting Documentation Pull Requests <del> If you're fixing an issue in the existing documentation, you should submit a PR against the main branch.  Follow [these instructions to create a documentation pull request against the kubernetes.io repository](http://kubernetes.io/docs/home/contribute/create-pull-request/). </del> <ins> If you're fixing an issue in the existing documentation, you should submit a PR against the main branch.  Follow [these instructions to create a documentation pull request against the kubernetes.io repository](https://kubernetes.io/docs/contribute/new-content/open-a-pr/). </ins> For more information, see [contributing to Kubernetes docs](https://kubernetes.io/docs/contribute/).

Discussion:
Problem: The text . on is redirecting to , it should point to these Check the github repository 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 these instructions to create a documentation pull request against the repository 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 redirecting to , it should point to these Check the github repository 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 these instructions to create a documentation pull request against the repository 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