jiebi/CodeConvo huggingface dataset:
Change:
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

Discussion:
在服务器日志中没有出现 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 角色绑定在多个场合使用宽松的策略。
Change:
This is a Bug Report Problem: In the documentation page , in the last section What's next, the link to appears to be dead. Proposed Solution: Remove (or Update) the link. Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en /kind bug /sig service-catalog
/assign

Discussion:
* If you are familiar with {{< glossary_tooltip text="Helm Charts" term_id="helm-chart" >}}, [install Service Catalog using Helm](/docs/tasks/service-catalog/install-service-catalog-using-helm/) into your Kubernetes cluster. Alternatively, you can [install Service Catalog using the SC tool](/docs/tasks/service-catalog/install-service-catalog-using-sc/). * View [sample service brokers](https://github.com/openservicebrokerapi/servicebroker/blob/master/gettingStarted.md#sample-service-brokers). * Explore the [kubernetes-sigs/service-catalog](https://github.com/kubernetes-sigs/service-catalog) project. <del> * View [svc-cat.io](https://svc-cat.io/docs/). </del>
Change:
There are some bugs: ,node%2D1%20drained,no%20node,-pod%2Db%20available "pod-b available" should be changed to "pod-b terminating". "node-2" should be changed to "node-2 draining".
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

Discussion:
|    node-1 *drained*  |       node-2        |       node-3       | *no node*          | |:--------------------:|:-------------------:|:------------------:|:------------------:| <del> |                      | pod-b *available*   | pod-c *available*  | pod-e *pending*    | </del> <ins> |                      | pod-b *terminating* | pod-c *available*  | pod-e *pending*    | </ins> |                      | pod-d *available*   | pod-y              |                    | <!--
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: In "Ephemeral Volumes" page, some -related contents exist. But according to the : Proposed Solution: Update -related contents in "Ephemeral Volumes", as PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be removed in v1.25. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign

Discussion:
standardized. See the documentation of each CSI driver for further instructions. <ins> ### CSI driver restrictions {{< feature-state for_k8s_version="v1.21" state="deprecated" >}} </ins> As a cluster administrator, you can use a [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) to control which CSI drivers can be used in a Pod, specified with the [`allowedCSIDrivers` field](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podsecuritypolicyspec-v1beta1-policy). <ins> {{< note >}} PodSecurityPolicy is deprecated and will be removed in the Kubernetes v1.25 release. {{< /note >}} </ins> ### Generic ephemeral volumes {{< feature-state for_k8s_version="v1.23" state="stable" >}}
Change:
This is a Feature Request What would you like to be Right now, building container images for local use of this repository via does not work with Apple Silicon chips. This is because the Dockerfile downloads the Hugo binary for amd64 architecture. I have been able to workaround this issue by explicitly asking for , however, containers built in this way have very poor performance. Instead, I would like to contribute a Dockerfile that works for arm64 architecture, in a way that contributors can build container images that work in architectures that are not amd64. Why is this needed Provide a better contributor experience while creating new documentation pages and testing them locally using containers.
I created pull request with a Dockerfile and Makefile target that I have tested to address this issue.
/retitle Docs build container image only supports AMD64 architecture
/priority backlog /triage accepted

Discussion:
# change is that the Hugo version is now an overridable argument rather than a fixed # environment variable. <del> FROM golang:1.15-alpine </del> <ins> FROM golang:1.16-alpine </ins> LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>" RUN apk add --no-cache  curl  <ins> gcc  g++  musl-dev  build-base  libc6-compat ARG HUGO_VERSION RUN mkdir $HOME/src &&  cd $HOME/src &&  curl -L https://github.com/gohugoio/hugo/archive/refs/tags/v${HUGO_VERSION}.tar.gz | tar -xz &&  cd "hugo-${HUGO_VERSION}" &&  go install --tags extended FROM golang:1.16-alpine RUN apk add --no-cache  </ins> git  openssh-client  rsync  <del> build-base  libc6-compat  </del> npm &&  npm install -D autoprefixer postcss-cli <del> ARG HUGO_VERSION </del> RUN mkdir -p /usr/local/src &&  cd /usr/local/src &&  <del> curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz &&  mv hugo /usr/local/bin/hugo &&  </del> addgroup -Sg 1000 hugo &&  adduser -Sg hugo -u 1000 -h /src hugo <ins> COPY --from=0 /go/bin/hugo /usr/local/bin/hugo </ins> WORKDIR /src USER hugo:hugo
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: page garbled. ! /language zh
I suddenly saw this page showing garbled characters today. Can you take a look?
Looking into this.
raised a PR for diagnosis looks like the cached version of the HTML is corrupted. It is not treated as HTML media type. Dummy PR for this:
/triage accepted

Discussion:
content_type: concept weight: 30 --- <!-- reviewers: - pweil-

### AppArmor Controlled via annotations on the PodSecurityPolicy. Refer to the [AppArmor <del> documentation](/docs/tutorials/clusters/apparmor/#podsecuritypolicy-annotations). </del> <ins> documentation](/docs/tutorials/policy/apparmor/#podsecuritypolicy-annotations). </ins> --> ### AppArmor 通过 PodSecurityPolicy 上的注解来控制。 详情请参阅 <del> [AppArmor 文档](/zh/docs/tutorials/clusters/apparmor/#podsecuritypolicy-annotations)。 </del> <ins> [AppArmor 文档](/zh/docs/tutorials/policy/apparmor/#podsecuritypolicy-annotations)。 </ins> <!--
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: In , the step No. 3 is talking about the location of binary, but actually in this section ("Install plugin") we should care about the location of binary, not of binary. Proposed Solution: In : And optionally, wrap these words with backquotes in : : kubectl L47: kubectl L62: kubectl L159: kubectl-convert L165: kubectl-convert (L180: kubectl-convert) - Already suggested above. Page to Update: )-,Append%20or%20prepend%20the%20kubectl%20binary%20folder%20to%20your%20PATH%20environment%20variable.,-Verify%20plugin%20is <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/triage accepted
/assign

Discussion:
1. Validate the binary (optional) <del> Download the kubectl checksum file: </del> <ins> Download the `kubectl` checksum file: </ins> ```powershell curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256" ``` <del> Validate the kubectl binary against the checksum file: </del> <ins> Validate the `kubectl` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:

$($(CertUtil -hashfile .kubectl.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl.exe.sha256) ``` <del> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </del> <ins> 1. Append or prepend the `kubectl` binary folder to your `PATH` environment variable. </ins> 1. Test to ensure the version of `kubectl` is the same as downloaded:

1. Validate the binary (optional) <del> Download the kubectl-convert checksum file: </del> <ins> Download the `kubectl-convert` checksum file: </ins> ```powershell curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256" ``` <del> Validate the kubectl-convert binary against the checksum file: </del> <ins> Validate the `kubectl-convert` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:

$($(CertUtil -hashfile .kubectl-convert.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl-convert.exe.sha256) ``` <del> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </del> <ins> 1. Append or prepend the `kubectl-convert` binary folder to your `PATH` environment variable. </ins> 1. Verify plugin is successfully installed
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: In section of Node Pressure Eviction Page, a Note is referred to the deprecation section of that doesn't exist. Proposed Solution: The Note should be removed as there are no deprecated flags for kubelet garbage collection. Page to Update: /sig node
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
The 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 /assign

Discussion:
Kubelet auto-discovers these filesystems and ignores other filesystems. Kubelet does not support other configurations. <del> {{<note>}} Some kubelet garbage collection features are deprecated in favor of eviction. For a list of the deprecated features, see [kubelet garbage collection deprecation](/docs/concepts/architecture/garbage-collection/#deprecation). {{</note>}} </del> <ins> Some kubelet garbage collection features are deprecated in favor of eviction: | Existing Flag | New Flag | Rationale | | ------------- | -------- | --------- | | `--image-gc-high-threshold` | `--eviction-hard` or `--eviction-soft` | existing eviction signals can trigger image garbage collection | | `--image-gc-low-threshold` | `--eviction-minimum-reclaim` | eviction reclaims achieve the same behavior | | `--maximum-dead-containers` | | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | | deprecated once old logs are stored outside of container's context | </ins> ### Eviction thresholds
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 Update to (briefly) mention that access control mechanisms are followed, optionally, by an audit mechanism recording that decision. Why is this needed Once the concept of auditing is into the Concepts section, we can update other mentions of that concept to hyperlink there. Comments Also relevant to The task page at already gives some background to the mechanism. It's OK to borrow text from that task page if it makes sense to do so. /language en
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign

Discussion:
Once a request passes all admission controllers, it is validated using the validation routines for the corresponding API object, and then written to the object store (shown as step **4**). <ins> ## Auditing Kubernetes auditing provides a security-relevant, chronological set of records documenting the sequence of actions in a cluster. The cluster audits the activities generated by users, by applications that use the Kubernetes API, and by the control plane itself. For more information, see [Auditing](/docs/tasks/debug-application-cluster/audit/). </ins> ## API server ports and IPs
Change:
This is a Bug Report Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /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

Discussion:
<ins> --- api_metadata: apiVersion: "" import: "k8s.io/api/core/v1" kind: "LocalObjectReference" content_type: "api_reference" description: "LocalObjectReference 包含足够的信息，可以让你在同一命名空间内找到引用的对象。" title: "LocalObjectReference" weight: 4 auto_generated: true --- <!-- api_metadata: apiVersion: "" import: "k8s.io/api/core/v1" kind: "LocalObjectReference" content_type: "api_reference" description: "LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace." title: "LocalObjectReference" weight: 4 auto_generated: true --> `import "k8s.io/api/core/v1"` <!-- LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. --> LocalObjectReference 包含足够的信息，可以让你在同一命名空间（namespace）内找到引用的对象。 <hr> <!-- - **name** (string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names --> - **name** (string) 被引用者的名称。 更多信息: https://kubernetes.io/zh/docs/concepts/overview/working-with-objects/names/#names。 </ins>
Change:
In , the para says that But after I click the page, I find no and I can only see . I also try in my env, the updateStrategy` does not. error: error validating "dep-": error validating data: ValidationError(): unknown field "updateStrategy" in ; if you choose to ignore these errors, turn validation off with --validate=false Is this document outdated? I can make a fix if it is.
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
Hi Both DaemonSet and Deployment use these 3 fields, linking to the deployment creates some confusion or misleading. I think we could link and to , same as refer to this similar issue for more info: see the reference api for
/good-first-issue
/remove-good-first-issue We only add that label for issues that have a barrier to entry that is zero or close to it. I'd expect to see at least: a link to the page that needs fixing a language label on the issue clear advice on the route to a fix / no concerns that there might be different options and the person working on it must choose /language en
Thanks, for this information. Actually, I forgot to mention the page in my comment, This is the page we have to update:
Yeah. I agree the new link will be better.
/assign

Discussion:
To enable the rolling update feature of a DaemonSet, you must set its `.spec.updateStrategy.type` to `RollingUpdate`. <del> You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) </del> <ins> You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) </ins> (default to 1), <del> [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) and </del> <ins> [`.spec.minReadySeconds`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (default to 0) and </ins> [`.spec.updateStrategy.rollingUpdate.maxSurge`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (a beta feature and defaults to 0) as well.
Change:
This is a Bug Report There is a link /docs/tutorials/clusters/seccomp on line 481 of the page content endocsreferencelabels-annotations-,but this link does not exist. <!--Required Information--Problem: There is a link /docs/tutorials/clusters/seccomp on line 481 of the page contentendocsreferencelabels-annotations-,but this link does not exist. Proposed Solution: commented redirects to We should update so that it hyperlinks to instead. Page to Update: <!--Kubernetes Version:--v1.23 <!--Additional Information:--NA Comments /language zh /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 done, next time we can use in PR description to auto close this. /close
Closing this issue. <detailsIn response to : Already done, next time we can use in PR description to auto close this. 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:
### container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io} This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25. <del> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes </del> <ins> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/seccomp/) takes </ins> you through the steps you follow to apply a seccomp profile to a Pod or to one of its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes, based on setting `securityContext` within the Pod's `.spec`.

### container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io} 此注解自 Kubernetes v1.19 起已被弃用，将在 v1.25 中失效。 <del> 教程[使用 seccomp 限制容器的系统调用](/zh/docs/tutorials/clusters/seccomp/)将引导你完成将 </del> <ins> 教程[使用 seccomp 限制容器的系统调用](/zh/docs/tutorials/security/seccomp/)将引导你完成将 </ins> seccomp 配置文件应用于 Pod 或其容器的步骤。 该教程介绍了在 Kubernetes 中配置 seccomp 的支持机制，基于在 Pod 的 `.spec` 中设置 `securityContext`。
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: Wrong rendering in ! cf. en version page: ! en file: zh file: Proposed Solution: Place Hugo-related fields in the beginning of . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language zh /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

Discussion:
<del> <!-- </del> <ins> --- </ins> api_metadata: apiVersion: "" import: "k8s.io/apimachinery/pkg/apis/meta/v1" kind: "LabelSelector" content_type: "api_reference" <del> description: "A label selector is a label query over a set of resources." title: "LabelSelector" </del> <ins> description: "标签选择器是对一组资源的标签查询。" title: "标签选择器" </ins> weight: 2 <del> --> </del> <ins> auto_generated: true </ins> --- <ins> <!-- </ins> api_metadata: apiVersion: "" import: "k8s.io/apimachinery/pkg/apis/meta/v1" kind: "LabelSelector" content_type: "api_reference" <del> description: "标签选择器是对一组资源的标签查询。" title: "标签选择器" </del> <ins> description: "A label selector is a label query over a set of resources." title: "LabelSelector" </ins> weight: 2 <del> auto_generated: true --- </del> <ins> --> </ins> `import "k8s.io/apimachinery/pkg/apis/meta/v1"`