jiebi/CodeConvo huggingface dataset:
Change:
--> 要删除正在运行 Hello World 应用程序的 Deployment，ReplicaSet 和 Pod，请输入以下命令： <del> kubectl delete deployment hello-world </del> <ins> ```shell kubectl delete deployment hello-world ``` </ins> ## {{% heading "whatsnext" %}} <!-- Learn more about [connecting applications with services](/docs/concepts/services-networking/connect-applications-service/). --> <del> 了解更多关于[将应用程序与服务连接](/zh/docs/concepts/services-networking/connect-applications-service/)。 </del> <ins> 进一步了解[将应用程序与服务连接](/zh/docs/concepts/services-networking/connect-applications-service/)。 </ins>

Discussion:
This is a Bug Report Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- outdated <!-- 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: Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- is different with English version page. Proposed Solution: Update Chinese page Page to Update: contentzhdocstutorialsstateless-applicationexpose-external-ip- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign
Change:
[upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. ``` <del> 1.  Manually upgrade your CNI provider plugin. </del> <ins> -  Manually upgrade your CNI provider plugin. </ins> Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow. Check the [addons](/docs/concepts/cluster-administration/addons/) page to

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.
Change:
<!-- overview --> This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * Kubernetes version 1.10.0 or later is required

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 indentation errors in the yaml files of EncryptionConfiguration. For example in the following yaml, lines after "- secrets" should indent two to the right. ! Proposed Solution: Correct the indentation errors. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Is it right to have in the fixed page?
I checked the preview page, and it's still wrong. I've close my PR.
It should looks like this or "secrets" is the subcontent of the second "resources", and "providers" is with the same level of the second "resources". Although I modified the markdown, the rendered webpage is still wrong.
/priority backlog /language en /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 : /priority backlog /language en /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
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten /assign
Change:
spec: containers: - name: nginx <del> image: registry.k8s.io/nginx-slim:0.8 </del> <ins> image: registry.k8s.io/nginx-slim:0.7 </ins> ports: - containerPort: 80 name: web

Discussion:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.
Change:
* [Scheduler Performance Tuning](/docs/concepts/scheduling-eviction/scheduler-perf-tuning/) * [Resource Bin Packing for Extended Resources](/docs/concepts/scheduling-eviction/resource-bin-packing/) * [Pod Scheduling Readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/) <ins> * [Descheduler](https://github.com/kubernetes-sigs/descheduler#descheduler-for-kubernetes) </ins> ## Pod Disruption

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 Change to mention the Why is this needed The Kubernetes project provides the descheduler - as an add-on - but our overview of scheduling makes no mention of it. Comments /language en /kind feature /sig scheduling
/priority backlog /triage accepted /help
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 : /priority backlog /triage accepted /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
/assign RakshitKumar04
Hii, Can you please elaborate, do I just need to add a heading under Scheduling and connect a link to it? !
Contributors are welcome to propose their own way to include the new concept (the descheduler) into the existing page. if you are not sure about how to the new detail, you could consider looking for a different issue. Maybe there is some other work to do that you'd understand better.
IMO, we can make a new heading for descheduler and add a paragraph(some content) for descheduler under it, and link it to the for more information.
Hi, your thoughts on the above opinion?
The approach I recommend is to open a PR and ask for feedback there. I don't see this as being a complicated change.
Thanks for your opinion.
Change:
You can read about [`downwardAPI` volumes](/docs/concepts/storage/volumes/#downwardapi). You can try using the downward API to expose container- or Pod-level information: <del> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) </del> <ins> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) </ins> * as [files in `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/)

Discussion:
This is a Bug Report <!--Required Information--Problem: The link is dead. The content from the section seems moved into top of the document and glossary in . Proposed Solution: remove fragment from the link change link to or Page to Update: /docs/concepts/workloads/pods/downward-api /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information /docs/tasks/job/indexed-parallel-processing-static
/assign
/language en /triage accepted /help We should find existing hyperlinks to and replace those with links to
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 : /language en /triage accepted /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
/unassign As has already opened a PR
/assign
GitHub didn't allow me to assign the following users: hs0210. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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:
<ins> The files in this directory have been imported from other sources. Do not edit them directly, except by replacing them with new versions. For Japanese translation, cncf-code-of-conduct.md is copied from the following CNCF repository: https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/jp.md </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Change:
and the API server does verify if the required keys are provided in a Secret configuration. <ins> {{< caution >}} SSH private keys do not establish trusted communication between an SSH client and host server on their own. A secondary means of establishing trust is needed to mitigate "man in the middle" attacks, such as a `known_hosts` file added to a ConfigMap. {{< /caution >}} </ins> ### TLS secrets Kubernetes provides a builtin Secret type `kubernetes.io/tls` for to storing

Discussion:
This is a Feature Request What would you like to be Add a caution note to the Concepts document article for Secrets, warning that SSH private keys do not establish fully trusted communication between clients and host servers. Why is this needed SSH key pairs provide a means of establishing authenticated communication between two parties, but not trusted communication between two parties. Trust can only be established via a secondary means, like a file. Without establishing trust, applications which utilize SSH keys by themselves for authentication are susceptible to "man in the middle" attacks. Comments This item was discussed during the first SIG Docs Security subproject meeting.
/sig security /triage accepted
/priority important-longterm Thanks
Change:
--- title: Garbage Collection content_type: concept <del> weight: 70 </del> <ins> weight: 60 </ins> --- <!-- overview -->

Discussion:
This is an enhancement 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 Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. It is also OK to replace this page with a hand-written overview that achieves the same effect. Why is this needed ReplicationController is deprecated. Comments You can make this change by editing the attribute in the of pages inside . /language en /priority backlog /good-first-issue /kind cleanup
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is an enhancement Request <!-- See for guidance on writing an actionable issue description. --Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. ReplicationController is deprecated. You can make this change by editing the attribute in the of pages inside . /priority backlog /good-first-issue /kind cleanup 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
Just the order of list needs to be changed to list Deployments and then ReplicaSet early and ReplicationController at the end in the , right?
(and to anyone else) you can make the minimal change you described, or you can consider further tidying. Either approach is valid; if you like, there is a spectrum of thoroughness in how you deal with this.
Oh, I've fixed the link to front matter; it should be to
Hey folks, I can take care of it if OK with that.
Sure you can go ahead!
Thanks! /assign
Change:
## {{% heading "whatsnext" %}} Learn more about the following: <del> * [Nodes](/docs/concepts/architecture/nodes/) and [their communication](/docs/concepts/architecture/control-plane-node-communication/) with the control plane. </del> <ins> * [Nodes](/docs/concepts/architecture/nodes/) and [their communication](/docs/concepts/architecture/control-plane-node-communication/) with the control plane. </ins> * Kubernetes [controllers](/docs/concepts/architecture/controller/). * [kube-scheduler](/docs/concepts/scheduling-eviction/kube-scheduler/) which is the default scheduler for Kubernetes. * Etcd's official [documentation](https://etcd.io/docs/).

Discussion:
Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign
Change:
[params.ui] # Enable to show the side bar menu in its compact state. sidebar_menu_compact = false <ins> # https://github.com/gohugoio/hugo/issues/8918#issuecomment-903314696 sidebar_cache_limit = 1 </ins> #  Set to true to disable breadcrumb navigation. breadcrumb_disable = false #  Set to true to hide the sidebar search box (the top nav search box will still be displayed if search is enabled)

Discussion:
Look into evaluating how we can make building the site take less memory / cpu. As has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build). This is all good though, it means we are adding content and localizations. Look into ways to reduce build time. A few options come to mind: Can we remove a large chunk of unused content? Can we build only a small subset of docs (easily and portable to the various localizations)? Are there any optimizations in hugo itself? There should be a way to reduce the amount of resources required to build . Considering there isn't a clear solution, I won't mark as good-first-issue. /sig docs /triage accepted
Idea: run the build localization-by-localization. I don't know if Hugo supports this but if it might let us run 14 shorter builds (potentially in parallel) rather than 1 long one. Idea: look for image resize options at build time. If reasonable to do so, replace the source image with what it gets resized to.
This might be an area where we could look for resources from CNCF to help with it - especially if the fix is applicable across multiple CNCF projects.
Change:
## Using environment variables inside of your config <del> Environment variables that you define in a Pod's configuration can be used elsewhere in the configuration, for example in commands and arguments that you set for the Pod's containers. </del> <ins> Environment variables that you define in a Pod's configuration under `.spec.containers[*].env[*]` can be used elsewhere in the configuration, for example in commands and arguments that you set for the Pod's containers. </ins> In the example configuration below, the `GREETING`, `HONORIFIC`, and `NAME` environment variables are set to `Warm greetings to`, `The Most <del> Honorable`, and `Kubernetes`, respectively. Those environment variables are then used in the CLI arguments passed to the `env-print-demo` container. </del> <ins> Honorable`, and `Kubernetes`, respectively. The environment variable `MESSAGE` combines the set of all these environment variables and then uses it as a CLI argument passed to the `env-print-demo` container. </ins> ```yaml apiVersion: v1

Discussion:
The "Using environment variables inside of your config" feature is great and has been very useful. Thanks! I have two minor suggestions: would also be useful to document which fields of a container spec this interpolation applies (or if it applies to almost all fields, what the exceptions are.) , the example is slightly confusing / misleading. The key feature that is documented here is the ability to statically use env vars defined in the config in other config fields. While the example is calling with a single string, it may look at a glance like a shell command which would do the interpolation itself (note notation and not or ). Perhaps a clearer example would be using env vars inside of other env vars: This shows more clearly that environment variable is configured statically from previously set environment variables - before the Pod is created, no shell interpolation involved.
/triage accepted /language en
/assign
As per my understanding, you are expecting here to add where this environment variable applies inside the configuration file like below. To set environment variables, include the env or envFrom field in the configuration file under .spec.containers[*]. Please confirm if i wrongly understood.
PR Raised here .
Change:
### 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> <!--

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 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
Change:
[CVE-2020-8554: Man in the middle using LoadBalancer or ExternalIPs](https://github.com/kubernetes/kubernetes/issues/97076) and the [DenyServiceExternalIPs admission controller](/docs/reference/access-authn-authz/admission-controllers/#denyserviceexternalips) for further information. ## Pod security - [ ] RBAC rights to `create`, `update`, `patch`, `delete` workloads is only granted if necessary.

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 Security Checklist describes Seccomp Default as an alpha feature, but it is GA in Kubernetes 1.27. This was also identified in Proposed Solution: Update the language and link. I didn't find a more recent relevant blog post but I didn't look carefully. There is a mention of the feature in a tutorial: Page to Update:
/language en /triage accepted /priority backlog
hey can I write blog for this
/assign
Change:
* Learn about [scheduling](/docs/concepts/scheduling-eviction/kube-scheduler/) * Learn about [kube-scheduler Configuration](/docs/reference/scheduling/config/) * Read the [kube-scheduler configuration reference (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/) <del> * Read the [kube-scheduler Policy reference (v1)](/docs/reference/config-api/kube-scheduler-policy-config.v1/) </del>

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 scheduler policy API was completely removed in 1.23. Proposed Solution: Revise concepts/configuration/manage-resources- to remove references to the scheduler policy API; Revise or even remove which is meaningless; Remove the kube-scheduler-policy- file from config API. Page to Update: See above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Related:
/sig scheduling /language en
/triage accepted