jiebi/CodeConvo huggingface dataset:
Change:
- kow3ns title: DaemonSet content_type: concept <del> weight: 50 </del> <ins> weight: 40 </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:
kubectl create secret docker-registry secret-tiger-docker  --docker-username=tiger  --docker-password=pass113  <del> --docker-email=tiger@acme.com </del> <ins> --docker-email=tiger@acme.com  --docker-server=my-registry.example:5000 </ins> ``` This command creates a Secret of type `kubernetes.io/dockerconfigjson`.

Discussion:
Doc link: ` I think it's more understandable by adding to this command the docker server (registry) Current version: kubectl create secret docker-registry secret-tiger-docker --docker-username=tiger --docker-password=pass113 --docker- New version: kubectl create secret docker-registry secret-tiger-docker --docker-username=tiger --docker-password=pass113 --docker- --docker-server=my-registry:5000
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
/sig storage
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
Change:
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`.

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:
ip6tables -t nat -A PREROUTING -d $xip/128 -j DNAT --to-destination $podip ``` <del> Assuming the JSON output above is stored in `/tmp/out` ([jq](https://stedolan.github.io/jq/) is an *awesome* program!). </del> <ins> Assuming the JSON output above is stored in `/tmp/out` ([jq](https://jqlang.github.io/jq/) is an *awesome* program!). </ins> As this is an example we make it really simple for ourselves by using

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 download page for is now (previously ) Proposed Solution: Throughout the English pages, replace the old download URL with the new one. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The download page for is now (previously ) Throughout the English pages, replace the old download URL with the new one. <!--Kubernetes Version:--/language en /priority backlog /triage accepted /help </details
I want to help with this. /assign
Hello I would like to work on this issue are you working on the issue?
I have riasd PR to help with this issue.
Change:
glossary_tooltip text="kubelet" term_id="kubelet" >}} and {{< glossary_tooltip text="kube-apiserver" term_id="kube-apiserver" >}} (`--feature-gates=HugePageStorageMediumSize=true`). <del> ## Future - NUMA locality guarantees as a feature of quality of service. - LimitRange support. </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: includes a statement about the future. These are best left to and GitHub issues rather than documentation - see . Proposed Solution: Remove the section at Consider making this change in the branch for the next release, so that the update happens at a time when changes are expected. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /help /priority backlog /language en /kind cleanup
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: includes a statement about the future. These are best left to and GitHub issues rather than documentation - see . Remove the section at <!--Kubernetes Version:--/help /priority backlog /language en /kind cleanup </details
/assign
Change:
```none deployment.apps/web created ``` <ins> Verify that the Deployment is in a Ready state: ```shell kubectl get deployment web ``` The output should be similar to: ```none NAME   READY   UP-TO-DATE   AVAILABLE   AGE web    1/1     1            1           53s ``` </ins> 1. Expose the Deployment:

Discussion:
Problem: Going through the documentation provided by the link such issue has being met on the step of verification that Ingress controller is directing the traffic using the command below: curl --resolve "hello-$( minikube ip )" -i http://hello- After running this command the terminal returns: Failed to connect to hello- port 80 after ms: Couldn't connect to server Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Kubernetes version: v1.28.3 <!--Additional Information:--Environment that is used: Macbook M1 Pro Minikube version: v1.32.0 Minikube uses the docker driver. Step on which problem has been met:
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
Page reported in issue: /language en
This is same as issue /triage duplicate I believe this should be fixed by updating the page by mentioning the instructions to create a for MacOS and Windows users. I'll try to work on a PR for this. Till the time the page is modified, the way around this is mentioned . The reason why it fails on MacOS and Windows is documented here , , You can also visit the page and view the tab in Step 4 Deploy applications.
/assign

you need start and then to solve same problem in mac
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 needs-information Hi. Is this about a particular web page?
sorry, this is about following tutorial Create an Ingress step 4
/retitle Ingress tutorial does not mention commands needed for Mac /remove-triage needs-information
/kind bug /language en
I can confirm that this is a valid issue on MacOS and the page needs to be updated. I think we should move this to /triage accepted. I cannot test this on Windows at the moment, but suggests that the behaviour on Windows will be the same as MacOS. The network is limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly.
/assign
Change:
* Both contain the same number of domain parts and each part matches. * The URL path of match image must be a prefix of the target image URL path. <del> * If the imageMatch contains a port, then the port must match in the image as well. </del> <ins> * If the matchImages contains a port, then the port must match in the image as well. </ins> Some example values of `matchImages` patterns are:

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: In , the word appears 3 times: But the exact name of field is actually. Proposed Solution: In , [L85-L86] [L144-L145] And optionally, we might wrap with backticks; like: through the whole doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
AFAIK we use backticks only for API Resource names per the style guide. We don't need to have the backticks to wrap matchImages. I agree with the rest of the suggestion, though. /triage accepted
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
I would like to give a try on this. /assign
Change:
<!-- ## Create a minikube cluster <del> 1. Click **Launch Terminal** </del> <ins> 1. Click **Launch Terminal**. </ins> --> ## 创建 Minikube 集群  {#create-a-minikube-cluster}

Discussion:
Numbers in the following list may be not up to date. Please run again before working on each of them.
/language zh /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 : /language zh /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
Change:
The recommended way to install it on Linux is to download the pre-built binary and move it to a directory under the `$PATH`. ```shell <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl  </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl  </ins> && sudo install kubectl /usr/local/bin && rm kubectl ```

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 still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--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
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
{{- $prepend := .Get "prepend" }} {{- $glossaryBundle := site.GetPage "page" "docs/reference/glossary" -}} {{- $glossaryItems :=  $glossaryBundle.Resources.ByType "page" -}} <del> {{- $term_info := $glossaryItems.GetMatch (printf "%s*" $id ) -}} </del> <ins> {{- $term_info := $glossaryItems.GetMatch (printf "%s.md" $id ) -}} </ins> {{- if not $term_info -}} {{- errorf "[%s] %q: %q is not a valid glossary term_id, see ./docs/reference/glossary/* for a full list" site.Language.Lang .Page.Path $id -}} {{- 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: This line includes glossary. However, the displayed content is glossary. ! Proposed Solution: The contents should be glossary, but I don't know how. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ja
/kind bug /priority backlog
/assign
Change:
## kind <del> [`kind`](https://kind.sigs.k8s.io/docs/) lets you run Kubernetes on </del> <ins> [`kind`](https://kind.sigs.k8s.io/) lets you run Kubernetes on </ins> your local computer. This tool requires that you have [Docker](https://docs.docker.com/get-docker/) installed and configured.

Discussion:
Problem: The text on is not working, it should point to this Check the page for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text king link to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to this Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text king link to and not to this . /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
Hello , the doesnt direct to any page, I have checked the official king page, I believe adding would be appropriate. Please suggest if any changes, Thanks.
/triage accepted Mind propose a fix?
Change:
容易受到资源枯竭的攻击，则如果你不限制服务 B 的资源的话，损害服务 A 的风险就会很高。 下表列出了安全性关注的领域和建议，用以保护 Kubernetes 中运行的工作负载： <del> 工作负载安全性关注领域 |  建议 | </del> <ins> 工作负载安全性关注领域         |  建议                 | </ins> ------------------------------ | --------------------- | RBAC 授权(访问 Kubernetes API) | https://kubernetes.io/zh/docs/reference/access-authn-authz/rbac/ <del> 认证方式 | https://kubernetes.io/zh/docs/reference/access-authn-authz/controlling-access/ </del> <ins> 认证方式 | https://kubernetes.io/zh/docs/concepts/security/controlling-access/ </ins> 应用程序 Secret 管理 (并在 etcd 中对其进行静态数据加密) | https://kubernetes.io/zh/docs/concepts/configuration/secret/ <br> https://kubernetes.io/zh/docs/tasks/administer-cluster/encrypt-data/ Pod 安全策略 | https://kubernetes.io/zh/docs/concepts/policy/pod-security-policy/ 服务质量（和集群资源管理）| https://kubernetes.io/zh/docs/tasks/configure-pod-container/quality-service-pod/

Discussion:
! Chinese page link can not open
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language zh
/assign
/kind bug
Change:
<img src ="/images/announcements/kccnc-eu-2022-black.svg" style="float: right; height: 80px;" /> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon EU 2022</a> <em> Valencia, Spain + Virtual</em>. message: | <del> 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> </del> <ins> 5 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> </ins> May 16 - 20, 2022. - name: Kubecon 2022 NA

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
Change:
brew install kubernetes-cli ``` <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> ```bash kubectl version --client

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