jiebi/CodeConvo huggingface dataset:
Change:
### AppArmor support This version introduces the initial support for AppArmor, allowing users to load and <del> unload AppArmor profiles into cluster nodes by using the new [AppArmorProfile](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/deploy/base/crds/apparmorprofile.yaml) CRD. </del> <ins> unload AppArmor profiles into cluster nodes by using the new [AppArmorProfile](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/deploy/base-crds/crds/apparmorprofile.yaml) CRD. </ins> To enable AppArmor support use the [enableAppArmor feature gate](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/config.yaml#L10) switch of your SPO configuration. Then use our [apparmor example](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/apparmorprofile.yaml) to deploy your first profile across your cluster.

Discussion:
This is a Bug Report Problem: Link for AppArmorProfile in is broken. Proposed Solution: Should be updated with correct 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
/area blog /language en
/assign
Change:
输出中包含 `foregroundDeletion` {{<glossary_tooltip text="finalizer" term_id="finalizer">}}， 类似这样： <del> ```none </del> <ins> ``` </ins> "kind": "Deployment", "apiVersion": "apps/v1", "metadata": {

Discussion:
There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /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
Change:
</center> </div> <div class="main-section landscape-section"> <del> {{< cncf-landscape helpers=false category="kubernetes-training-partner" >}} </del> <ins> {{< cncf-landscape helpers=false category="special--kubernetes-training-partner" >}} </ins> </div> </div>

Discussion:
This is a Bug Report In Kubernetes Training page in hindi the link is not valid which do not show the several Kubernetes Training Partners. <!-- 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 embedded link is not valid. ! Proposed Solution: Update with the valid link Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language hi /sig docs /assign
/area localization
/triage accepted
This issue is resolved under pull request
so i am closing this issue marking as resolved and completed
/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
Change:
{{< /tabs >}} <del> 2. 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> ```powershell kubectl version --client ``` <del> 3. Navigate to your home directory: </del> <ins> 1. Navigate to your home directory: </ins> ```powershell # If you're using cmd.exe, run: cd %USERPROFILE% cd ~ ``` <del> 4. Create the `.kube` directory: </del> <ins> 1. Create the `.kube` directory: </ins> ```powershell mkdir .kube ``` <del> 5. Change to the `.kube` directory you just created: </del> <ins> 1. Change to the `.kube` directory you just created: </ins> ```powershell cd .kube ``` <del> 6. Configure kubectl to use a remote Kubernetes cluster: </del> <ins> 1. Configure kubectl to use a remote Kubernetes cluster: </ins> ```powershell New-Item config -type file

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:
{{< /note >}} Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. <ins> To enable bash autocompletion in current session of shell, source the ~/.bashrc file: ```bash source ~/.bashrc ``` </ins>

Discussion:
/kind documentation /sig docs Bash Auto Completion has a missing step to enable autocompletion in current shell session If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. To enable autocompletion in current session of shell, source the file:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/assign
Change:
<ins> --- title: "ポリシー" weight: 90 --- </ins>

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed This document is not translated in Japanese. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Copy a file from en contents to concepts/policy/resource- and translate it into Japanese.
/assign /language-ja
/language ja
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/assign
/unassign
/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
Change:
Here's an example. Suppose this is the configuration file for a Deployment object: <del> {% include code.html language="yaml" file="update_deployment.yaml" ghlink="/docs/concepts/tools/update_deployment.yaml" %} </del> <ins> {% include code.html language="yaml" file="update_deployment.yaml" ghlink="/docs/tutorials/object-management-kubectl/update_deployment.yaml" %} </ins> Also, suppose this is the live configuration for the same Deployment object:

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: 404 on Proposed Solution: Update location of Page to Update:
Change:
For example: <del> ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-approver rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - get - list - watch - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests/approval verbs: - update - apiGroups: - certificates.k8s.io resources: - signers resourceNames: - example.com/my-signer-name # example.com/* can be used to authorize for all signers in the 'example.com' domain verbs: - approve ``` </del> <ins> {{< codenew file="access/certificate-signing-request/clusterrole-approve.yaml" >}} </ins> To allow signing a CertificateSigningRequest:

Discussion:
/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly 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:
"service/networking": { "curlpod":                                 {&apps.Deployment{}}, "custom-dns":                              {&api.Pod{}}, <ins> "default-ingressclass":                    {&networking.IngressClass{}}, </ins> "dual-stack-default-svc":                  {&api.Service{}}, "dual-stack-ipfamilies-ipv6":              {&api.Service{}}, "dual-stack-ipv6-svc":                     {&api.Service{}},

Discussion:
While working through the Killer Shell scenario for NetworkPolicies to prep for my CKA, I used the example but it failed validation. When I looked at their solution it had one tiny difference, they had a - in front of "ports:" and you guys didn't. Based on the reference docs it appears ports does expect an array which would mean that you are missing the hyphen. docs: solution from
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
The indentation of list items may be the source of confusion. Once you indent all list items under a given key, the parent element of the 'ports' attribute becomes more evident. The example on the website is correct. I'm not sure about the solution from If you put as the first key of a list item object, if will carry the bar for that list item, if is not the the first key, you will indent it rather than adding another before it. Anyway, I'm fixing the example in hope things become clearer for readers.
Change:
The output displays the pod created: ``` <del> NAME                            READY     STATUS    RESTARTS   AGE redis-master-765d459796-258hz   1/1       Running   0          50s </del> <ins> NAME                     READY   STATUS    RESTARTS   AGE mongo-75f59d57f4-4nd6q   1/1     Running   0          2m4s </ins> ``` View the Deployment's status:

Discussion:
uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/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
/remove-triage needs-information
/assign
Change:
</tr> <tr> <ins> <td colspan="2">-v, --v int</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>number for the log level verbosity</p></td> </tr> <tr> </ins> <td colspan="2">--version version[=true]</td> </tr> <tr>

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
demonstrates how to create, delete, scale, and update the Pods of StatefulSets. --> <del> 本教程介绍如何了使用 [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) 来管理应用。 </del> <ins> 本教程介绍了如何使用 [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) 来管理应用。 </ins> 演示了如何创建、删除、扩容/缩容和更新 StatefulSets 的 Pods。

Discussion:
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
Link: /retitle [zh] Issue with /zh/docs/tutorials/stateful-application/basic-stateful-set
/assign
Change:
{{< feature-state for_k8s_version="1.22" state="stable" >}} The Kubernetes control plane sets an immutable {{< glossary_tooltip text="label" term_id="label" >}} <del> `kubernetes.io/metadata.name` on all namespaces, provided that the `NamespaceDefaultLabelName` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled. </del> <ins> `kubernetes.io/metadata.name` on all namespaces. </ins> The value of the label is the namespace name.

Discussion:
It looks like the feature gate "NamespaceDefaultLabelName" has been removed as described on this page: But it's noted on this page that it can be enabled: Maybe that the "Namespaces" page needs to be updated.
/language en /sig docs
/retitle Unclear documentation on feature gate The documentation is not wrong; however, we can clean up to avoid mentioning the feature gate at all (we'd keep the feature-state shortcode). /priority backlog /help /triage accepted
This request has been marked as needing help from a contributor. 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 : /retitle Unclear documentation on feature gate to avoid mentioning the feature gate at all (we'd keep the feature-state shortcode). /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
/assign
I had the same doubts before, and I changed it by the way, please help review, thanks
Change:
* [Generating Reference Documentation for the Kubernetes API](/docs/contribute/generate-ref-docs/kubernetes-api/) * [Contributing to the Upstream Kubernetes Project for Documentation](/docs/contribute/generate-ref-docs/contribute-upstream/) --> * [生成参考文档快速入门](/zh-cn/docs/contribute/generate-ref-docs/quickstart/) <del> * [为 kubectll 命令生成参考文档](/zh-cn/docs/contribute/generate-ref-docs/kubectl/) </del> <ins> * [为 kubectl 命令生成参考文档](/zh-cn/docs/contribute/generate-ref-docs/kubectl/) </ins> * [为 Kubernetes API 生成参考文档](/zh-cn/docs/contribute/generate-ref-docs/kubernetes-api/) * [为上游 Kubernetes 项目做贡献以改进文档](/zh-cn/docs/contribute/generate-ref-docs/contribute-upstream/)

Discussion:
This is a Bug Report There is a typo in the Chinese documentation. The text " kubectll " contains an extra "l" in "kubectl". Proposed Solution: The correct text should be " kubectl ". Page to Update:
/area localization /language zh
/triage accepted
/retitle Typo in localized page Kubernetes
Change:
* runc：v1.1 或更新版本 * crun: v1.8.6 或更新版本 <ins> * Linux 内核: v5.12 或更新版本 </ins> <!-- ## What's next?

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: Compared with [en] The [zh] miss in section Proposed Solution: add in section Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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:
scroll-margin-top: 35px; } </style> <del> <iframe id="iframe-landscape-kcsp" src="https://landscape.cncf.io/embed/embed.html?key=special--kubernetes-certified-service-provider&headers=true&style=shadowed&size=md&bg-color=%23d95e00&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> <iframe id="iframe-landscape-conformance" src="https://landscape.cncf.io/embed/embed.html?key=platform&headers=true&style=shadowed&size=md&bg-color=%23d95e00&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> <iframe id="iframe-landscape-ktp" src="https://landscape.cncf.io/embed/embed.html?key=special--kubernetes-training-partner&headers=true&style=shadowed&size=md&bg-color=%23d95e00&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> </del> <ins> <iframe id="iframe-landscape-kcsp" src="https://landscape.cncf.io/embed/embed.html?key=special--kubernetes-certified-service-provider&headers=true&style=shadowed&size=md&bg-color=%233371e3&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> <iframe id="iframe-landscape-conformance" src="https://landscape.cncf.io/embed/embed.html?key=platform&headers=true&style=shadowed&size=md&bg-color=%233371e3&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> <iframe id="iframe-landscape-ktp" src="https://landscape.cncf.io/embed/embed.html?key=special--kubernetes-training-partner&headers=true&style=shadowed&size=md&bg-color=%233371e3&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> </ins> <script> iFrameResize({ }, '#iframe-landscape-kcsp'); iFrameResize({ }, '#iframe-landscape-conformance');

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: uses the wrong background color(s); it's but should be (Kubernetes blue). I think the orange color was copied from by mistake. Proposed Solution: Revise the shortcode. Consider making the color be set once and then reused (“”). Page to Update: You would see the change on We should use blue backgrounds whether or not an announcement banner is showing. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: PR updated the shortcode. /area web-development /triage accepted /priority backlog If fixing this, consider also moving the iframe scroll-margin-top fix to be more general. See and
this is a nit against PR but fixing it isn't at all urgent.
/lifecycle frozen We should fix this eventually.
I would like to help with this. /assign
/assign
Change:
It conflicts with the [core values of the Kubernetes project](https://git.k8s.io/community/values.md) and our community does not tolerate it. - name: Kubecon 2021 EU <del> startTime: 2021-04-30T00:00:00 endTime: 2021-05-07T00:00:00 </del> <ins> startTime: 2021-04-30T00:00:00 endTime: 2021-05-07T00:00:00 </ins> style: "background-image: linear-gradient(90deg, rgb(249, 145, 6) 0%, rgb(252, 29, 68) 100%)" title: | <img src="/images/announcements/kubecon-eu-2021-white.svg" style="float: right; height: 80px;" />

Discussion:
Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . File to Update: /good-first-issue /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . /kind document /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
/remove-good-first-issue Banner changes are actually a bit weird.
/language en
/triage accepted