jiebi/CodeConvo huggingface dataset:
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: No resources found in default namespace. ``` <del> To sum things up, when there's an override owner reference from a child to a parent, deleting the parent deletes the children automatically. This is called `cascade`. The default for cascade is `true`, however, you can use the --cascade=false option for `kubectl delete` to delete an object and orphan its children. </del> <ins> To sum things up, when there's an override owner reference from a child to a parent, deleting the parent deletes the children automatically. This is called `cascade`. The default for cascade is `true`, however, you can use the --cascade=orphan option for `kubectl delete` to delete an object and orphan its children. </ins> <del> In the following example, there is a parent and a child. Notice the owner references are still included. If I delete the parent using --cascade=false, the parent is deleted but the child still exists: </del> <ins> In the following example, there is a parent and a child. Notice the owner references are still included. If I delete the parent using --cascade=orphan, the parent is deleted but the child still exists: </ins> ``` kubectl get configmap
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: mymap-child    0      13m8s mymap-parent   0      13m8s <del> kubectl delete --cascade=false configmap/mymap-parent </del> <ins> kubectl delete --cascade=orphan configmap/mymap-parent </ins> configmap "mymap-parent" deleted kubectl get configmap
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: fields to be updated.  Also, the DaemonSet controller will use the original template the next time a node (even with the same name) is created. <del> You can delete a DaemonSet.  If you specify `--cascade=false` with `kubectl`, then the Pods </del> <ins> You can delete a DaemonSet.  If you specify `--cascade=orphan` with `kubectl`, then the Pods </ins> will be left on the nodes.  If you subsequently create a new DaemonSet with the same selector, the new DaemonSet adopts the existing Pods. If any Pods need replacing the DaemonSet replaces them according to its `updateStrategy`.
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: to use a different pod template and for the Job to have a new name. You cannot update the Job because these fields are not updatable. Therefore, you delete Job `old` but _leave its pods <del> running_, using `kubectl delete jobs/old --cascade=false`. </del> <ins> running_, using `kubectl delete jobs/old --cascade=orphan`. </ins> Before deleting it, you make a note of what selector it uses: ```shell
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: You can delete a ReplicationController without affecting any of its pods. <del> Using kubectl, specify the `--cascade=false` option to [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete). </del> <ins> Using kubectl, specify the `--cascade=orphan` option to [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete). </ins> When using the REST API or Go client library, you can delete the ReplicationController object.
Code change:
According to the can get a parameter with a value of "background", "orphan", or "foreground". proposes to use .
Hello Related PRs/issues: So, the page should be updated. /kind bug /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign
/assign
To : has already assigned himself/herself, and posted a PR ().

Related discussion:
text: Run the following command: ```shell <del> kubectl delete deployment nginx-deployment --cascade=false </del> <ins> kubectl delete deployment nginx-deployment --cascade=orphan </ins> ``` **Using the Kubernetes API**
Code 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: lists Helm as being built-in to Kubernetes. (it isn't; it's a separate project that depends on Kubernetes in order to be useful) Proposed Solution: Reword the page to be a list of both built-in tools and external tools that are so commonly used or relevant that they may as well be seen as required for Kubernetes to function. (for context: see ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
/assign
/triage accepted

Related discussion:
text: --- <!-- overview --> <del> Kubernetes contains several built-in tools to help you work with the Kubernetes system. </del> <ins> Kubernetes contains several built-in tools and external tools that are commonly used or relevant that may as well be seen as required for Kubernetes to function. </ins> <!-- body -->
Code change:
Page to Update: Kubernetes is deprecating as mentioned . But in the page linked there is not even a mention of PSP being deprecated. Either that section should be removed or a deprecation notice needs to be so that the users wouldn't end following those steps if they are on higher versions.
For anyone's information: In PodSecurityPolicy is being replaced by a new, simplified admission controller. For more details on this change, see . Follow these guidelines to simplify migration from PodSecurityPolicy to the new admission controller: /triage accepted /language en
/assign I would like to work on this.
fixed it here:

Related discussion:
text: ### Restricting profiles with the PodSecurityPolicy <ins> {{< note >}} PodSecurityPolicy is deprecated in Kubernetes v1.21, and will be removed in v1.25. See [PodSecurityPolicy documentation](/docs/concepts/policy/pod-security-policy/) for more information. {{< /note >}} </ins> If the PodSecurityPolicy extension is enabled, cluster-wide AppArmor restrictions can be applied. To enable the PodSecurityPolicy, the following flag must be set on the `apiserver`:
Code change:
This is a Bug Report <!--Required Information--Problem: In docs, link give 404 error. Proposed Solution: should be linked to 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
/assign I can work on this.
Fixed it here:
ref
Hi I think we don't change in file as it is used as configuration when building the website. It was changed in this , as for website repo master branch renamed to main in k8s v1.22.

Related discussion:
text: to the REST api. For further documentation refer to the authorization.v1beta1 API objects and <del> [webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go). </del> <ins> [webhook.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go). </ins>
Code 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: Proposed Solution: to to to to 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
Closest issue I could find related to this
Is the issue open? I would be happy to work on it. Thank you.
Do you mind testing it on your local environment. I think the documentation is correct.
/triage needs-information
/kind support
Perhaps the words "Pod" and "Job" may have been misleading. I think "Job" refers to a container that complete in a certain period. In other words, this explanation means the following. The activeDeadlineSeconds is recommended to be use for containers (Pod) that complete after a certain period. It should not be used for containers (Pod) that will run forever.
I would suggest the following. How about it? before: after:
/close Please re-open if you believe this clarification ("only if" instead of "if") is important
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

Related discussion:
text: Use `activeDeadlineSeconds` on the Pod to prevent init containers from failing forever. The active deadline includes init containers. <del> However it is recommended to use `activeDeadlineSeconds` if user deploy their application </del> <ins> However it is recommended to use `activeDeadlineSeconds` only if teams deploy their application </ins> as a Job, because `activeDeadlineSeconds` has an effect even after initContainer finished. The Pod which is already running correctly would be killed by `activeDeadlineSeconds` if you set.
Code 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 link " API " is broken. Proposed Solution: Page to Update: -- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
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
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue </details
/assign

Related discussion:
text: 힙스터에서 메트릭 가져오기는 Kubernetes 1.11에서 사용 중단(deprecated)됨. {{< /note >}} <del> 자세한 사항은 [메트릭 API를 위한 지원](#메트릭-API를-위한-지원)을 참조한다. </del> <ins> 자세한 사항은 [메트릭 API를 위한 지원](#메트릭-api를-위한-지원)을 참조한다. </ins> 오토스케일러는 스케일 하위 리소스를 사용하여 상응하는 확장 가능 컨트롤러(예: 레플리케이션 컨트롤러, 디플로이먼트, 레플리케이션 셋)에 접근한다. 스케일은 레플리카의 개수를 동적으로 설정하고 각 현재 상태를 검사 할 수 있게 해주는 인터페이스이다.
Code change:
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.

Related discussion:
text: [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)
Code change:
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.

Related discussion:
text: [build.environment] NODE_VERSION = "10.20.0" <del> HUGO_VERSION = "0.82.0" </del> <ins> HUGO_VERSION = "0.87.0" </ins> RUBY_VERSION = "3.0.1" [context.production.environment]
Code change:
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.

Related discussion:
text: <del> Subproject commit 0f9c38b8daae932518bee269de2768395d2a2dc2 </del> <ins> Subproject commit f6a1870918520c83872fc07943a67a1d9d2a998c </ins>
Code change:
In k8s document page: Second paragraph below Rule b says: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 3 months (4 per year). It should say: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 4 months (3 per year).
/kind bug /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /triage accepted Thanks for the report.
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 /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /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
I would like to pick this up /assign

Related discussion:
text: All of this is best illustrated by examples.  Imagine a Kubernetes release, version X, which introduces a new API group.  A new Kubernetes release is made <del> every approximately 3 months (4 per year).  The following table describes which </del> <ins> every approximately 4 months (3 per year).  The following table describes which </ins> API versions are supported in a series of subsequent releases. <table>
Code 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: Except for the [EN] version, the unnecessary 'Tools Include' item is displayed in translated versions. Check the left side navigation menu in , However, the translated versions(, , , , , , ) have 'Tools Included' item. Why 'Tools Included' item is shown only in translated versions? This item is an intended headless page(, ) and should not be rendered. Proposed Solution: The item should not appear in translated versions. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/triage accepted
/assign

Related discussion:
text: {{ range . }} {{ with (where $.section.Translations ".Lang" . ) -}} {{ $p := index . 0 -}} <del> {{ $pages =  $pages | lang.Merge (union $p.Pages $p.Sections) -}} </del> <ins> {{ $pages = where ( $pages | lang.Merge (union $p.Pages $p.Sections)) ".Params.toc_hide" "!=" true -}} </ins> {{ end -}} {{ end -}} {{ end -}}