jiebi/CodeConvo huggingface dataset:
Change:
and a `removed_release` label that indicates the Kubernetes release in which the API will no longer be served. This is an example query using `kubectl`, [prom2json](https://github.com/prometheus/prom2json), <del> and [jq](https://stedolan.github.io/jq/) to determine which deprecated APIs have been requested </del> <ins> and [jq](https://jqlang.github.io/jq/) to determine which deprecated APIs have been requested </ins> from the current instance of the API server: ```sh

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:
{{ end }} {{ partialCached "head-css.html" . "asdf" }} <script <del> src="https://code.jquery.com/jquery-3.3.1.min.js" </del> <ins> src="{{ "js/jquery-3.3.1.min.js" | relURL }}" </ins> integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8=" crossorigin="anonymous"></script> {{ if and (.Site.Params.offlineSearch) (not .Site.Params.gcs_engine_id) }}

Discussion:
Kubernetes website does not respond to language change
This is because .... we are not using the cached jquery script. We are downloading from which is sometimes blocked from China.
Change:
### Enabling Etcd Tracing <del> Add `--experimental-enable-distributed-tracing`,  `--experimental-distributed-tracing-address=0.0.0.0:4317`, `--experimental-distributed-tracing-service-name=etcd` flags to etcd to enable tracing.  Note that this traces every request, so it will probably generate a lot of traces if you enable it. </del> <ins> Add `--experimental-enable-distributed-tracing`,  `--experimental-distributed-tracing-address=0.0.0.0:4317`, `--experimental-distributed-tracing-service-name=etcd` flags to etcd to enable tracing.  Note that this traces every request, so it will probably generate a lot of traces if you enable it. Required etcd version is [v3.5+](https://etcd.io/docs/v3.5/op-guide/monitoring/#distributed-tracing). </ins> ### Example Trace: List Nodes

Discussion:
is an awesome blog. It didn't mention that required etcd version is 3.5+ to support .
cc
hey . I wanna work on this issue . how can i work on this issue ?
/assign
this was your article. I'm guessing you'd be happy with the revision but as it is a blog article I wanted to check first. /language en /area blog /remove-kind support
Yes, I think it would be good to update it with that detail.
/triage accepted
Change:
--build-arg HUGO_VERSION=$(HUGO_VERSION) container-build: module-check <del> $(CONTAINER_RUN) --read-only $(CONTAINER_IMAGE) hugo --minify </del> <ins> $(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 $(CONTAINER_IMAGE) sh -c "npm ci && hugo --minify" </ins> container-serve: module-check $(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir

Discussion:
This is a Bug Report As discussed in the SIG-Docs meeting, the current steps for building doc website in README is incomplete in the following point of views. It requires yarn on top of npm, but is missing and package- is there. did not work for me but I need further investigation on it. The build step is going to be equal in containerized and local in , but yarn installation or npm ci is currently missing in . <!--Required Information--Proposed Solution: and remove yarn from the dependency the npm command inside of the container Page to Update: N/A
Here's my cat picture after the sig-docs meeting lol !
AIUI, the live website build (within Netlify) relies on , and does not use Yarn.
/area web-development
Could you have a quick look if npm ci in local works just fine?
Yes, I believe so.
worked in my local environment
/kind bug /priority important-longterm
/sig contributor-experience I suppose
Change:
- title: Online Training Course path: https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615 - docs/tutorials/stateless-application/hello-minikube.md <ins> - title: Configuration section: - docs/tutorials/configuration/configure-redis-using-configmap.md </ins> - title: Object Management Using kubectl section: - docs/tutorials/object-management-kubectl/object-management.md

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done
Change:
```yaml apiVersion: v1 <del> kind: List </del> items: - apiVersion: stable.example.com/v1 kind: CronTab metadata: <del> creationTimestamp: 2017-05-31T12:56:35Z </del> <ins> annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"stable.example.com/v1","kind":"CronTab","metadata":{"annotations":{},"name":"my-new-cron-object","namespace":"default"},"spec":{"cronSpec":"* * * * */5","image":"my-awesome-cron-image"}} creationTimestamp: "2021-06-20T07:35:27Z" </ins> generation: 1 name: my-new-cron-object namespace: default <del> resourceVersion: "285" uid: 9423255b-4600-11e7-af6a-28d2447dc82b </del> <ins> resourceVersion: "1326" uid: 9aab1d66-628e-41bb-a422-57b8b3b1f5a9 </ins> spec: cronSpec: '* * * * */5' image: my-awesome-cron-image <ins> kind: List </ins> metadata: resourceVersion: "" <ins> selfLink: "" </ins> ``` ## Delete a CustomResourceDefinition

Discussion:
Problem: Output from the example on this page is incorrect. Proposed Solution: Fix example to show the correct output. Page to Update: Additional Information: There has been some confusion about how the works in Kubernetes. The output from this example is incorrect and it implies that the API server returns at the top of the output. In reality, the API server doesn't implement . It is kubectl that adds to the end of the output as a means of rendering it. Here is the output that returned when I ran the commands on this page:
Thanks for the reporting the bug and clear explanation! I will fix the doc. /triage accepted /assign
Thanks for taking that on, . For anyone interested in a discussion of , I'm working on some larger writing to describe that and related list types (PodList, ServiceList, etc.). See .
Thanks for writting the larger topic for the List. I close this issue since the larger topic is tracked in another issue. /close
Closing this issue. <detailsIn response to : Thanks for writting the larger topic for the List. I close this issue since the larger topic is tracked in another issue. /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
Thanks for taking care of this issue so quickly! I was happy to see that it had published when I looked at it today.
Change:
Kubernetes 节点发送的心跳（Heartbeats）有助于确定节点的可用性。 心跳有两种形式：`NodeStatus` 和 [`Lease` 对象] <del> (/docs/reference/generated/kubernetes-api/{{< latest-version >}}/#lease-v1-coordination-k8s-io)。 </del> <ins> (/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#lease-v1-coordination-k8s-io)。 </ins> 每个节点在 `kube-node-lease`{{< glossary_tooltip term_id="namespace" text="名字空间">}} 中都有一个与之关联的 `Lease` 对象。 `Lease` 是一种轻量级的资源，可在集群规模扩大时提高节点心跳机制的性能。

Discussion:
The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.
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
this is fixed here
Change:
document assumes these default ports. However, they are configurable through the kubeadm config file. * Each host must [have docker, kubelet, and kubeadm installed](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/). <ins> * Each host should have access to the Kubernetes container image registry (`k8s.gcr.io`) or list/pull the required etcd image using `kubeadm config images list/pull`. This guide will setup etcd instances as [static pods](https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/) managed by a kubelet. </ins> * Some infrastructure to copy files between hosts. For example `ssh` and `scp` can satisfy this requirement.

Discussion:
It would be VERY helpful to know, that you have to download, extract, etc... the etcd binaries. Or that etcd will run as pods. The only point where this is mentioned is in the "optional" section... thank you!
hello, this is a valid request. PRs are welcome. this list here: could include something like: file to change: /sig cluster-lifecycle /kind feature /priority backlog /help /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 : hello, this is a valid request. PRs are welcome. file to change: /kind feature /priority backlog /help /good-first-issue </details
/assign
I think I can help with this, thank you.
Change:
weight: 20 --- <!-- overview --> <del> This page provides an overview of DNS support by Kubernetes. </del> <ins> Kubernetes creates DNS records for services and pods. You can contact services with consistent DNS names instead of IP addresses. </ins> <!-- body -->

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 guidance on DNS resolution for services between namespaces is confusing users. Proposed Solution: add additional info on the troubleshooting pages, add a table to the services concept page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted /kind cleanup
/sig network
Change:
This page shows how to create an External Load Balancer. When creating a service, you have the option of automatically creating a <del> cloud network load balancer. This provides an externally-accessible IP address that sends traffic to the correct port on your cluster nodes _provided your cluster runs in a supported environment and is configured with the correct cloud load balancer provider package_. </del> <ins> cloud network load balancer. This provides an externally-accessible IP address that sends traffic to the correct port on your cluster nodes _provided your cluster runs in a supported environment and is configured with the correct cloud load balancer provider package_. For information on provisioning and using an Ingress resource that can give services externally-reachable URLs, load balance the traffic, terminate SSL etc., please check the [Ingress](/docs/concepts/services-networking/ingress/) documentation. </ins> {% endcapture %}

Discussion:
Problem: this page should mention concept as a way to create an external LB to an application. Page to Update:
There are some offhanded mentions of Ingress in samples, but they're likely to be more confusing than not. Agreed: more/better docs needed.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
ユーザーは削除を要求可能であるべきで、プロセスがいつ終了するかを知ることができなければなりませんが、削除が最終的に完了することも保証できるべきです。ユーザーがPodの削除を要求すると、システムはPodが強制終了される前に意図された猶予期間を記録および追跡します。強制削除までの猶予期間がある場合、{{< glossary_tooltip text="kubelet" term_id="kubelet" >}}正常な終了を試みます。 <del> 通常、コンテナランタイムは各コンテナのメインプロセスにTERMシグナルを送信します。多くのコンテナランタイムは、コンテナイメージで定義されたSTOPSIGNAL値を尊重し、TERMの代わりにこれを送信します。猶予期間が終了すると、プロセスにKILLシグナルが送信され、Podは{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}から削除されます。プロセスの終了を待っている間にkubeletかコンテナランタイムの管理サービスが再起動されると、クラスターは元の猶予期間を含めて、最初からリトライされます。 </del> <ins> 通常、コンテナランタイムは各コンテナのメインプロセスにTERMシグナルを送信します。多くのコンテナランタイムは、コンテナイメージで定義されたSTOPSIGNAL値を尊重し、TERMシグナルの代わりにこれを送信します。猶予期間が終了すると、プロセスにKILLシグナルが送信され、Podは{{< glossary_tooltip text="API server" term_id="kube-apiserver" >}}から削除されます。プロセスの終了を待っている間にkubeletかコンテナランタイムの管理サービスが再起動されると、クラスターは元の猶予期間を含めて、最初からリトライされます。 </ins> フローの例は下のようになります。

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update some links and fix some expressions. Why is this needed Some of the links have already been translated Also, some expressions were not official. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
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
Change:
以便将 Pod `mypod` 放置在可用区 `B` 上，而不是可用区 `C` 上。 同样，Kubernetes 也会一样处理 `spec.nodeSelector`。 <del> {{< codenew file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" >}} </del> <ins> {{% code file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" %}} </ins> <!-- ## Implicit conventions

Discussion:
the Chinese translation is wrong, "" should be "" see from English site:
/language zh
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn </details
/language zh
/sig docs
/triage accepted
/assign
Change:
ajaxConf.beforeSend = function(xhr){ xhr.setRequestHeader('Ocp-Apim-Subscription-Key', '51efd23677624e04b4abe921225ea7ec'); }; $.ajax(ajaxConf).done(function(res) { <ins> if (res.webPages == null) return; // If no result, 'webPages' is 'undefined' </ins> var paginationAnchors = window.getPaginationAnchors(Math.ceil(res.webPages.totalEstimatedMatches / 10)); res.webPages.value.map(ob => { results += window.getResultMarkupString(ob); })

Discussion:
Searching keyword including space is not working. If you search one keyword, for example, "command", it will work. But, if "command and args" is input, the search result shows "Fetching results..." and do not return the result.
Hello, Thank you for pointing out the issue! I confirmed the same problem happens when searching the keyword "command and args" (). And I'll investigate the cause of this problem and fix it. /assign
BTW this applies to users using Bing search from China. See PR
are these symptoms still occurring? We're seeing different reports.
I have confirmed that this issue has dissapeared! Thank you for dealing with!
I'm glad to hear that!
I've had this problem now. But it disappeared because I used a different browser (chrome to Firefox).
Change:
<!-- overview --> <del> {{< feature-state for_k8s_version="v1.21" state="stable" >}} </del> <ins> {{< feature-state for_k8s_version="v1.22" state="stable" >}} </ins> A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repeating schedule. One CronJob object is like one line of a _crontab_ (cron table) file. It runs a job periodically on a given schedule, written in [Cron](https://en.wikipedia.org/wiki/Cron) format. <ins> In addition, the CronJob schedule supports timezone handling, you can specify the timezone by adding "CRON_TZ=<time zone>" at the beginning of the CronJob schedule, and it is recommended to always set `CRON_TZ`. </ins> {{< caution >}} All **CronJob** `schedule:` times are based on the timezone of the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}.

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: PR highlights that the documentation for CronJob is out of date since the v1.22 release. We're now using the revised controller by default (with no option to revert) and also a different syntax for the schedule. Proposed Solution: Identify stale or incorrect data on the pages about CronJobs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v.122 Additional Information: /kind bug /sig apps Relevant to
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
Change:
<!-- overview --> <del> This page shows how to use `kubectl port-forward` to connect to a Redis </del> <ins> This page shows how to use `kubectl port-forward` to connect to a MongoDB </ins> server running in a Kubernetes cluster. This type of connection can be useful for database debugging.

Discussion:
uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /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 : /triage accepted /kind bug /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
/remove-triage needs-information
/assign
Change:
kubectl चेकसम फाइल डाउनलोड करें: ```powershell <del> curl -LO https://dl.k8s.io/{{% param "fullversion" %}}/bin/windows/amd64/kubectl.exe.sha256 </del> <ins> curl -LO https://dl.k8s.io/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe.sha256 </ins> ``` चेकसम फ़ाइल से kubectl बाइनरी को मान्य करें:

Discussion:
Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.
Change:
title: "fish auto-completion" description: "Optional configuration to enable fish shell auto-completion." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- {{< note >}}

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 source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Proposed Solution: Edit every file within : Page to Update: and its contents /area web-development /help /priority backlog /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Edit every file within : Page to Update: and its contents /help /priority backlog /good-first-issue </details
/retitle Include files for install are rendered and served /triage accepted
/assign
/unassign
Thanks !
Change:
Descargue el archivo de comprobación de kubectl: ```powershell <del> curl -LO https://dl.k8s.io/{{% param "fullversion" %}}/bin/windows/amd64/kubectl.exe.sha256 </del> <ins> curl -LO https://dl.k8s.io/v{{% skew currentPatchVersion %}}/bin/windows/amd64/kubectl.exe.sha256 </ins> ``` Valide el binario kubectl con el archivo de comprobación:

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 param is deprecated. Proposed Solution: Replace the shortcode (Spanish pages), for example with or something close. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Part of /language es
/triage accepted /area localization /priority backlog