jiebi/CodeConvo huggingface dataset:
Change:
[javascript_required] other = "JavaScript must be [enabled](https://www.enable-javascript.com/) to view this content" <ins> [katacoda_removal_warning] other = """This online tutorial on this page uses functionality that will [not be available](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html) past <time datetime="2022-06-15">June 15th, 2022</time>.""" </ins> [latest_release] other = "Latest Release:"

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 For pages that use Katacoda, add a warning about its removal. Why is this needed Prompted by and Comments /priority critical-urgent /language en /triage accepted
Change:
{{ block "deprecated" . }} {{ partial "deprecation-warning.html" . }} {{ end }} <ins> {{ if or ( .HasShortcode "kat-button" ) ( .HasShortcode "katacoda-tutorial" ) }} {{ block "katacoda-removal" . }} {{ partial "katacoda-removal.html" . }} {{ end }} {{ end }} </ins> {{ block "main" . }}{{ end }} {{- if .HasShortcode "thirdparty-content" -}} {{ block "thirdparty-disclaimer" . }}

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 For pages that use Katacoda, add a warning about its removal. Why is this needed Prompted by and Comments /priority critical-urgent /language en /triage accepted
Change:
### ValidatingAdmissionWebhook {#validatingadmissionwebhook} <del> {{< feature-state for_k8s_version="v1.13" state="beta" >}} </del> This admission controller calls any validating webhooks which match the request. Matching webhooks are called in parallel; if any of them rejects the request, the request fails. This admission controller only runs in the validation phase; the webhooks it calls may not

Discussion:
This is a Bug Report It's not a bug, just an outdated doc thing. Problem: The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to in . But the docs still show that they are in beta state at and . Proposed Solution: the description from the two plug-ins. the descriptions of the two plug-ins if they need an update too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it. /assign
/triage accepted
Change:
<!-- lessoncontent --> <del> ## Minikubeクラスターの作成 </del> <ins> ## minikubeクラスターの作成 </ins> 1. **Launch Terminal** をクリックしてください {{< kat-button >}} {{< note >}} <del> Minikubeをローカルにインストール済みの場合は、`minikube start`を実行してください。 </del> <ins> minikubeをローカルにインストール済みの場合は、`minikube start`を実行してください。 </ins> {{< /note >}} 2. ブラウザーでKubernetesダッシュボードを開いてください:

Discussion:
This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted
Change:
- madhusudancs title: ReplicaSet content_type: concept <del> weight: 10 </del> <ins> weight: 20 </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:
1. Tải về phiên bản mới nhất: ``` <del> curl -LO "https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl" </ins> ``` <del> Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` trong câu lệnh với phiên bản cụ thể. </del> <ins> Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -LS https://dl.k8s.io/release/stable.txt)` trong câu lệnh với phiên bản cụ thể. </ins> Ví dụ, để tải về phiên bản {{< param "fullversion" >}} trên macOS, gõ: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Tạo kubectl binary thực thi.

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:
<ins> <div class="td-content"> <h1>{{ .Title }}</h1> {{ with .Params.description }}<div class="lead">{{ . | markdownify }}</div>{{ end }} <div class="td-byline mb-4"> {{ with .Params.author }}{{ T "post_byline_by" }} <b>{{ . | markdownify }}</b> |{{ end}} {{ with .Params.translator }}{{ T "translated_by" }} <b>{{ . | markdownify }}</b> |{{ end }} <time datetime="{{  $.Date.Format "2006-01-02" }}" class="text-muted">{{ $.Date.Format $.Site.Params.time_format_blog  }}</time> </div> <header class="article-meta"> {{ partial "taxonomy_terms_article_wrapper.html" . }} {{ if (and (not .Params.hide_readingtime) (.Site.Params.ui.readingtime.enable)) }} {{ partial "reading-time.html" . }} {{ end }} </header> {{ .Content }} {{ if (.Site.Params.DisqusShortname) }} <br /> {{ partial "disqus-comment.html" . }} <br /> {{ end }} {{ partial "pager.html" . }} </div> </ins>

Discussion:
This is a Feature Request What would you like to be In , the "author" metadata was to the front matter. Currently, some l10n teams are also setting "translator" metadata. This is one of the initiatives to promote the localization of blog posts. FYI: I would like to add "translator" metadata to the blog's front matter, just like the author metadata. Why is this needed To promote the localization of blog articles. This would be a significant motivation for those involved in localization. Comments
/area web-development /area blog /area localization
/assign
This is a great idea. It will be very motivating for localization contributors.
Thank you for your interest in this issue, mengjiao-liu ! I've opened a pull request to resolve it - . please have a look :)
Would be nice to add this feature. /priority backlog /triage accepted
Change:
## kind [`kind`](https://kind.sigs.k8s.io/docs/) lets you run Kubernetes on <del> your local computer. This tool it requires that you have </del> <ins> your local computer. This tool requires that you have </ins> [Docker](https://docs.docker.com/get-docker/) installed and configured. The kind [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/) page

Discussion:
In the second sentence of the first paragraph under : "This tool it requires that you have Docker installed and configured." Is it better to remove "it"? My suggestion is remove "it" "This tool requires that you have Docker installed and configured."
/triage accepted /language en /kind bug /good-first-issue /priority backlog Thanks - I agree with your suggested fix.
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 : /triage accepted /language en /kind bug /good-first-issue /priority backlog 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:
| `jobs` | | batch | true | Job | | `certificatesigningrequests` | `csr` | certificates.k8s.io | false | CertificateSigningRequest | | `leases` | | coordination.k8s.io | true | Lease | <ins> | `endpointslices` |  | discovery.k8s.io | true | EndpointSlice | </ins> | `events` | `ev` | events.k8s.io | true | Event | | `ingresses` | `ing` | extensions | true | Ingress | <ins> | `flowschemas` |  | flowcontrol.apiserver.k8s.io | false | FlowSchema | | `prioritylevelconfigurations` |  | flowcontrol.apiserver.k8s.io | false | PriorityLevelConfiguration | | `ingressclasses` |  | networking.k8s.io | false | IngressClass | | `ingresses` | `ing` | networking.k8s.io | true | Ingress | </ins> | `networkpolicies` | `netpol` | networking.k8s.io | true | NetworkPolicy | <ins> | `runtimeclasses` |  | node.k8s.io | false | RuntimeClass | </ins> | `poddisruptionbudgets` | `pdb` | policy | true | PodDisruptionBudget | | `podsecuritypolicies` | `psp` | policy | false | PodSecurityPolicy | | `clusterrolebindings` | | rbac.authorization.k8s.io | false | ClusterRoleBinding |

Discussion:
This is a Bug Report Problem: The resource type list on is about v1.13.3 which is too old. We are not obliged to keep the list updated on every release, but having the list updated to a supported version is still desireable. Proposed Solution: Update the list to reflect what we have today. Page to Update:
ref:
/assign
fixed. /close
Closing this issue. <detailsIn response to : fixed. /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
using the first configured service cluster IP range. * `PreferDualStack`: Allocates both IPv4 and IPv6 cluster IPs for the Service when dual-stack is enabled. If dual-stack is not enabled or supported, it falls back to single-stack behavior. * `RequireDualStack`: Allocates Service `.spec.clusterIPs` from both IPv4 and IPv6 address ranges when dual-stack is enabled. If dual-stack is not enabled or supported, the Service API object creation fails. <del> * Selects the `.spec.ClusterIP` from the list of `.spec.ClusterIPs` based on the address family </del> <ins> * Selects the `.spec.clusterIP` from the list of `.spec.clusterIPs` based on the address family </ins> of the first element in the `.spec.ipFamilies` array. If you would like to define which IP family to use for single stack or define the order of IP

Discussion:
page is plenty of wrong references to the non defined ` instead.
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. 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 : /good-first-issue 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
/kind bug
/assign
Thanks for solving this so so quick (you are the best ;-)
Change:
See the [webhook response](#response) section for the data expected from webhooks. The example admission webhook server leaves the `ClientAuth` field <del> [empty](https://github.com/kubernetes/kubernetes/blob/v1.13.0/test/images/webhook/config.go#L47-L48), </del> <ins> [empty](https://github.com/kubernetes/kubernetes/blob/v1.22.0/test/images/agnhost/webhook/config.go#L38-L39), </ins> which defaults to `NoClientCert`. This means that the webhook server does not authenticate the identity of the clients, supposedly apiservers. If you need mutual TLS or other ways to authenticate the clients, see

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 link for "admission webhook server leaves the ClientAuth field " mention under the in the redirect to the code of k8s version v1.13.0 i.e. , The webhook folder doesn't exist under images folder but now the folder is under () folder. Also, the code in the master is modified as compared to the code in v1.13.0. It should be redirected to the recent release i.e. v1.22.0 as linking to master isn't stable Proposed Solution: The link should be redirected to instead of 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
/sig auth
/assign
Fixed it here:
Change:
kubectl cluster-info dump --output-directory=/path/to/cluster-state   # Dump current cluster state to /path/to/cluster-state # View existing taints on which exist on current nodes. <del> kubectl get nodes -o=custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect </del> <ins> kubectl get nodes -o='custom-columns=NodeName:.metadata.name,TaintKey:.spec.taints[*].key,TaintValue:.spec.taints[*].value,TaintEffect:.spec.taints[*].effect' </ins> # If a taint with that key and effect already exists, its value is replaced as specified. kubectl taint nodes foo dedicated=special-user:NoSchedule

Discussion:
Add quotes in the flag of command to avoid confusing the shell: Otherwise, this is what user may see:
Link:
/assign
/triage accepted /language en /retitle Unquoted command in kubectl cheat sheet
Change:
同样，查看`annotations`文件： ```shell <del> /# cat /etc/annotations </del> <ins> /# cat /etc/podinfo/annotations </ins> ``` <!--

Discussion:
the file labels and annotations should be in the directory /etc/podinfo not /etc !
Hi What's the URL of the web page that isn't right? /triage needs-information
/triage accepted
/assign
Change:
memory: 200Mi requests: memory: 100Mi <del> ... </del> <ins> ... status: </ins> qosClass: Burstable ```

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 location of qosClass is not correct in the last example, which is a result of the following command: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en /priority backlog /sig scheduling
/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 : /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:
to see its supported topology keys and examples. {{< note >}} <del> If you choose to use `waitForFirstConsumer`, do not use `nodeName` in the Pod spec </del> <ins> If you choose to use `WaitForFirstConsumer`, do not use `nodeName` in the Pod spec </ins> to specify node affinity. If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state. Instead, you can use node selector for hostname in this case as shown below.

Discussion:
In ; waitForFirstConsumer is spelt. Correct spelling is WaitForFirstConsumer
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
Issue solved with
Change:
注意，某些方案可能需要同时采用几种类型的扩展。 <!-- image source for flowchart: https://docs.google.com/drawings/d/1sdviU6lDz4BpnzJNHfNpQrqI9F19QZ07KnhnxVrp2yg/edit --> <del> {{< figure src="/zh-cn/docs/concepts/extend-kubernetes/flowchart.png" </del> <ins> {{< figure src="/zh-cn/docs/concepts/extend-kubernetes/flowchart.svg" </ins> alt="附带使用场景问题和实现指南的流程图。绿圈表示是；红圈表示否。" class="diagram-large" caption="选择一个扩展方式的流程图指导" >}}

Discussion:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Please raise the issue in English language so that it can be easy to understand in community.
/language zh Issue Translation is Currently this After this page select , the text in the flow chart is not .
/triage needs-information Even with a translation, I don't understand if this is a bug report, a support query, or a feature request.
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page It is a bug, on zh-cn page , the text in the flowchart should be Chinese instead of Korean.
Re-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page , the text in the flowchart should be Chinese instead of Korean. 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
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page
/assign
Change:
use of that credential. Set short lifetimes on certificates and automate their rotation. Use an authentication provider that can control how long issued tokens are available and use short lifetimes where possible. If you use service-account tokens in external integrations, plan to <del> rotate those tokens frequently. For example, once the bootstrap phase is complete, a bootstrap </del> <ins> rotate those tokens frequently. For example, once the bootstrap phase is complete, a bootstrap </ins> token used for setting up nodes should be revoked or its authorization removed. ### Review third party integrations before enabling them

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. --We have two pages with similar aims: We should ensure that the advice in the two documents is aligned, and also make sure that the two documents link to each other. Why is this needed It's a bad idea to document multiple ways to make sure that your cluster is secure, unless those are well aligned. Comments /sig security /sig docs /language en
Relevant to
Regarding this: We can use a reference section/note/what's next section in the end of stating: -
/triage accepted
Hey I would like to work on this.
/assign