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

Discussion:
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 ().
Change:
建议使用基于策略的准入插件（例如 [PodSecurityPolicy](#podsecuritypolicy) 和自定义准入插件）， 该插件可以针对特定用户或命名空间，还可以防止创建权限过高的 Pod。 <del> ### DenyEscalatingExec {#denyescalatingexec} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### DenyEscalatingExec {#denyescalatingexec} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> <!-- This admission controller will deny exec and attach commands to pods that run with escalated privileges that

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
{{< kat-button >}} {{< note >}} <del> If you installed minikube locally, run `minikube start`. </del> <ins> If you installed minikube locally, run `minikube start`. Before you run `minikube dashboard`, you should open a new terminal, start `minikube dashboard` there, and then switch back to the main terminal. </ins> {{< /note >}} 2. Open the Kubernetes dashboard in a browser:

Discussion:
Katacoda doesn’t work. Minikube doesn’t work. Is there a good, official, tutorial that does work? Or that is “printed” only without requiring finicky interactive stuff that never works?
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
I tested following the instructions, using Katacoda to host the cluster. I noticed a missing detail. Before you run , you should open a new terminal, start there, and then switch back to the main terminal. Alternatively, we could rely on shell process management and have the reader run . This doesn't work on Windows though. Would you be willing to revise the issue description to include these details I discovered
I didn't have any luck with it on any of several browsers I tried. It failed out on all of them.
Change:
kubectl config current-context                       # display the current-context kubectl config use-context my-cluster-name           # set the default context to my-cluster-name <del> # add a new cluster to your kubeconf that supports basic auth </del> <ins> # add a new user to your kubeconf that supports basic auth </ins> kubectl config set-credentials kubeuser/foo.kubernetes.com --username=kubeuser --password=kubepassword # permanently save the namespace for all subsequent kubectl commands in that context.

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. --Need to rectify comment wherein "cluster" is mentioned instead of "user" <!--Required Information--Problem: Comment section reads - Proposed Solution: Comment shall be - "# add a new user to your kubeconf that supports basic auth" Page to Update:
Thanks for spotting this The command you've mentioned lets you tell about new user identity (new to your anyway), including details on how to authenticate as that user. As you say, it doesn't configure etc to know about a new cluster. This looks worth fixing. /help /language en /kind bug /priority important-longterm
/sig cli
Sorry for jumping in, I'm gonna update the Issue labels to reflect the work on linked PR. /remove-help /assign
GitHub didn't allow me to assign the following users: gosoon. 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 : Sorry for jumping in, I'm gonna update the Issue labels to reflect the work on linked PR. /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
Change:
date: 2018-04-12 full_link: /docs/tasks/administer-cluster/running-cloud-controller/ short_description: > <del> Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud. </del> <ins> Cloud Controller Manager is a Kubernetes component that embeds cloud-specific control logic. </ins> aka: tags:

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue
I'll work on that! /remove-help /assign
Change:
hugo server --buildFuture docker-image: <del> $(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION) </del> <ins> $(DOCKER) build .  --network=host  --tag $(DOCKER_IMAGE)  --build-arg HUGO_VERSION=$(HUGO_VERSION) </ins> docker-build: $(DOCKER_RUN) $(DOCKER_IMAGE) hugo

Discussion:
This is a Bug Report Problem: When building kubernetes-hugo it can fail with below error because build process can't access internet. By default docker build use bridge network to reach Internet which is not always correct assumption. The same problem can be seen reported in few other places: Error: [root website]# make docker-image docker build . --tag kubernetes-hugo --build-arg HUGOVERSION=0.59.1 Sending build context to Docker daemon 3.584kB Step 1/7 : FROM alpine:latest --- Step 2/7 : LABEL maintainer="Luc Perkins " ---Using cache --- Step 3/7 : RUN apk add --no-cache curl git openssh-client rsync build-base libc6-compat ---Running in fetch http://dl- WARNING: Ignoring http://dl- temporary error (try again later) fetch http://dl- WARNING: Ignoring http://dl- temporary error (try again later) ERROR: unsatisfiable constraints: build-base (missing): required by: world[build-base] curl (missing): required by: world[curl] git (missing): required by: world[git] libc6-compat (missing): required by: world[libc6-compat] openssh-client (missing): required by: world[openssh-client] rsync (missing): required by: world[rsync] The command '/bin/sh -c apk add --no-cache curl git openssh-client rsync build-base libc6-compat' returned a non-zero code: 6 make: [Makefile:39: docker-image] Error 6 Proposed Solution: It would be more reliable to use docker host network instead of bridge network. For building kubernetes-hugo, it doesn't really matter which network is used to pull all artifacts. And docker host network almost always guarantees access to Internet. Page to Update: N/A Version:* Problem can be seen on latest master.
Change:
1. Launch a terminal window in the directory you downloaded the manifest files. 1. Apply the MongoDB Deployment from the `mongo-deployment.yaml` file: <ins> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml --> </ins> ```shell kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml ``` <del> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml --> </del> 1. Query the list of Pods to verify that the MongoDB Pod is running:

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Change:
Kubeadm signs the certificate in the `admin.conf` to have `Subject: O = system:masters, CN = kubernetes-admin`. `system:masters` is a break-glass, super user group that bypasses the authorization layer (e.g. RBAC). Do not share the `admin.conf` file with anyone and instead grant users custom permissions by generating <del> them a kubeconfig file using the `kubeadm kubeconfig user` command. </del> <ins> them a kubeconfig file using the `kubeadm kubeconfig user` command. For more details see [Generating kubeconfig files for additional users](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs#kubeconfig-additional-users). </ins> {{< /warning >}} Make a record of the `kubeadm join` command that `kubeadm init` outputs. You

Discussion:
The command only has Cobra (CLI) documentation and there are no pointers on what fields are relevant in the configuration passed with --config to it: Add a minimal example + config for the command usage on this page: /sig cluster-lifecycle /kind feature xref
/triage accepted
/language en
Change:
<ins> --- title: "Kubeadm Generated" weight: 10 toc_hide: true --- </ins>

Discussion:
<!-- 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 href is (English). The of is recently in . Proposed Solution: In , Before: After: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
/language ko
/triage accepted
Resolved by
Change:
{{ define "hero-more" }} {{ with site.GetPage "section" "docs/tutorials/kubernetes-basics" }} <del> <a href="{{ .RelPermalink }}" id="quickstartButton" class="button">{{ .LinkTitle }}</a> </del> <ins> <a href="{{ .RelPermalink }}"><button id="quickstartButton" class="button">{{ .LinkTitle }}</button></a> </ins> {{ end }} {{ end }}

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: On the home page of website I found that the Learn Kubernetes Basics button needs to be edited as when we hover upon it the words are not clearly visible. Proposed Solution: We can make this button same as the buttons in other pages of the website like for example, under the documentation tab we have View Concepts and View Tutorial buttons. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--I would like to work upon this issue if you assign it to me. Thankyou.
/sig docs /area web-development /language en
Hi Thank you for raising this issue. You can assign this issue to yourself by commenting tag.
/assign
/retitle Learn Kubernetes Basics button difficult to read when hovered
/triage accepted /priority important-longterm Fixes are welcome.
I have a few options for the title: "Getting Started with Kubernetes Basics" "Exploring the Fundamentals of Kubernetes" "K8s Fundamentals" Please review these suggestions. Thanks
Hi The title seems interesting; we can use 'Exploring the Fundamentals of Kubernetes' as the new title.
Waiting for suggestions from other members.
'Learn Kubernetes Basics' is simple and conveys the correct message as is imo
Let's leave the text as is, and fix the poor color contrast that happens when someone hovers over the button.
Thank you
Untested, But a probable alternate fix Try modifying to wrap the with a like: css changes would not be necessary
It's been a month since this is waiting, Would any contributor like a take on this? (I think this can be a good first issue)
Just one thing; it's handy to cover even older issues that we're prioritizing too. See
Change:
```powershell stop-service kube-proxy <del> curl.exe -Lo <path-to-kube-proxy.exe> "https://dl.k8s.io/{{< skew currentPatchVersion >}}/bin/windows/amd64/kube-proxy.exe" </del> <ins> curl.exe -Lo <path-to-kube-proxy.exe> "https://dl.k8s.io/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kube-proxy.exe" </ins> restart-service kube-proxy ``` -->

Discussion:
<!--Required Information--Problem: We've deprecated the param () and now English documents are using instead. (by ) All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: For each localization team, search and change appropriately. (See the reference, ) Please check the following task box if the localization task is complete. Page to Update: [x] de [x] es [x] fr [x] hi [x] id [x] ja [x] ko [x] pt-br [x] ru [x] vi [ ] zh-ch [previously done]Once all localizations have switched over, we can remove the parameter from the site.
/assign for the Korean contents.
PR: [ko] Replace deprecated fullversion shortcode for Korean :) The task for Korean can be completed after is merged into the main branch.
/assign For Brazilian Portuguese changes
/triage accepted
/assign For Hindi changes
The Brazilian Portuguese localization has replaced all occurrences via /.
/assign for french content
/reopen
Reopened this issue. <detailsIn response to : /reopen 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-help
I reopened as there is one more page to fix.
Really done! Thanks folks. /close
Closing this issue. <detailsIn response to : Really done! 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:
- stdin - stdinOnce - tty <ins> - name: Security context fields: - securityContext </ins> - name: Not allowed fields: - ports

Discussion:
This is a Bug Report <!--Required Information--Problem: Setting for ephemeral containers is allowed as of Kubernetes 1.22, but it's still showing up as a "not allowed" field here: Proposed Solution: This page looks to be autogenerated based on the API definition, but I'm not sure how it's detecting not allowed fields. If it's automatic we'll correct the metadata or if it's curated then just reclassify the field in docs. Page to Update:
/assign
The fix is likely to happen within
is autogenerated. I don't think received field updates for v1.22
Track the update of the documentation as an issue in this repository. /triage accepted
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]:
Looks like this is still happening, and also is showing up under the alpha heading even though its description says (correctly) that it's beta. This dropped off my radar, but I'll take a look at it in the next few days. /remove-lifecycle stale
/priority critical-urgent
/remove-priority critical-urgent /priority important-soon /sig security you're welcome to make a case for raising it back to critical. What would be the motivation there?
Hi I don't wish to make that case. I was just trying to assign a priority according to guidance and . The documentation is wrong for a core feature, which seems like a "fix it now" rather than "fix it in the next release" priority. The priority isn't important to me, though. Happy for it to be whatever you think is best.
This repo uses continuous deployment (we don't wait for a release for fixes). Anyway, yes, it looks important.
Change:
} } <ins> .flip-nav .search-item { .td-search-input { background-color: $medium-grey; } input, textarea { color: white; } textarea:focus, input:focus { color: white; } } @media only screen and (max-width: 1500px) { header nav .search-item { display: none; } } </ins> /* FOOTER */ footer { background-color: #303030;

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 Currently Docs search hides when you scroll down the page, but it should not get hidden it must stay there at the top. Why is this needed Search Input should always stay at its place.Also, as a suggestion it can also be called on keyboard shortcut like like this to easily navigation in the docs. Comments !
/sig docs
/area web-development How about putting the search in the top nav? See for a related suggestion.
But, I'm not sure it's a good plan. The top nav already has a bunch of sections, and adding the search might make it look too crowded.
See how does it - I think that's a nice approach. We could drop one of the sections that's in the top nav now, or maybe combine two of them into a menu.
/triage accepted Making this improvement is helpful. /priority backlog though
/assign
Have a review on this PR -
Does it? On my browser, that doesn't happen. ! You can see that this page is scrolled but the search in the left-hand nav is still available for someone to look at it. /priority awaiting-more-evidence /remove-triage accepted
Even though I don't think the issue description is quite right, I still see the value of putting a search in the top nav. That is a place where people would look for it.
I think it more depend on screen size, in my case when i have scroll down the page, then i am not able to see that search button on the left side !
Change:
- `path`: Path that is exported by the NFS server. - `readOnly`: A flag indicating whether the storage will be mounted as read only (default false). <del> Kubernetes doesn't include an internal NFS provisioner. You need to use an external provisioner to create a StorageClass for NFS. </del> <ins> Kubernetes doesn't include an internal NFS provisioner. You need to use an external provisioner to create a StorageClass for NFS. </ins> Here are some examples: - [NFS Ganesha server and external provisioner](https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner)

Discussion:
There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted
Change:
with your new arguments. {{< note >}} <del> The `command` field corresponds to `entrypoint` in some container runtimes. Refer to the [Notes](#notes) below. </del> <ins> The `command` field corresponds to `entrypoint` in some container runtimes. </ins> {{< /note >}} In this exercise, you create a Pod that runs one container. The configuration

Discussion:
URL: File: /tasks/inject-data-application/define-command-argument- Remove the entire Notes section. Clean up the page so that there's no mention of a specific runtime. /sig docs /language en
I would remove the entire section. Docker is far from the only alternative to Kubernetes. If someone wanted to, we could accept a blog article that compares Docker, Kubernetes, Nomad, etc for how you specify these things. But it's fine if that blog is never submitted. /triage accepted
to me this is more about comparing Docker Swarm to Kubernetes. I think it's a good bit of tidying but I'm not sure it's needed for the dockershim removal work.