jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: On the page we find : 404 error in the section . The link is also wrong in the section, giving a 404 error. Proposed Solution: The proposed solution is to update the in the k/website repo. Do the following changes: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/triage accepted /language en
I think new contributors can work on this issue. /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 : I think new contributors can work on this issue. /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
/assign

Discussion:
investigate! Contact us on <del> [Slack](/docs/tasks/debug/overview/#slack) or </del> <ins> [Slack](https://slack.k8s.io/) or </ins> [Forum](https://discuss.kubernetes.io) or [GitHub](https://github.com/kubernetes/kubernetes). ## {{% heading "whatsnext" %}} <del> Visit the [troubleshooting overview document](/docs/tasks/debug/overview/) </del> <ins> Visit the [troubleshooting overview document](/docs/tasks/debug/) </ins> for more information.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: shortcode is not working in localized pages. found this in the PR . en: ja: https://deploy-preview---kubernetes-io-main- ... Proposed Solution: Update so that if the localized version of api reference for current lang exists (e.g. ), then shortcode generates a link that points to the localized version of api reference. if the localized version of api reference for current lang does not exist, then shortcode generates a link that points to the English version of api reference. File to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
After we resolve this, it might be great to backport this fix.
/triage accepted /area localization
/assign
Per , would you be willing to backport the change to the v1.23 and v1.22 releases?
Please let me know. I know that kubernetes/kubernetes has the following documentation Is there the method for backport in kubernetes/website? Should I create two new PRs for v1.23 and v1.22 with the old release as the merge destination?

Discussion:
{{ $pageArg := .Get "page" }} {{ $anchorArg := .Get "anchor" }} {{ $textArg := .Get "text" }} <del> {{ $page := site.GetPage "page" (printf "%s/%s" $base $pageArg) }} </del> <ins> {{ $pagePath := path.Join $base $pageArg }} {{ $page := site.GetPage "page" $pagePath }} {{ with $page }}{{else}}{{ range where site.Home.AllTranslations "Language.Lang" "en" }}{{ $page = .Site.GetPage "page" $pagePath }}{{ end }}{{ end }} </ins> {{ $metadata := $page.Params.api_metadata }} <a href="{{ $page.RelPermalink }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a>  No newline at end of file
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Kubernetes has alpha support for an annotation ; however, this is not registered or documented. Proposed Solution: register the annotation document it We can achieve both of these by updating with information about the annotation. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: We should document this name even though WG Naming have recommended avoiding the term “whitelist”. After documenting it, the next step could be to deprecate the annotation, or to make a new, non-alpha annotation that has a different name. /language en /kind bug /sig scheduling /lifecycle frozen
Also see
/triage accepted
Relevant to
/assign
Are you working on this issue? Do you need any help?
yes I am working on it.
Need any help from my side?
No as of now
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 found this issue while going through and trying to learn more about these annotations. I have raised a PR regarding same here: PTAL! Also, how to proceed with this?

Discussion:
This annotation requires the [PodTolerationRestriction](/docs/reference/access-authn-authz/admission-controllers/#podtolerationrestriction) admission controller to be enabled. This annotation key allows assigning tolerations to a namespace and any new pods created in this namespace would get these tolerations added. <ins> ### scheduler.alpha.kubernetes.io/tolerationsWhitelist {#schedulerkubernetestolerations-whitelist} Example: `scheduler.alpha.kubernetes.io/tolerationsWhitelist: '[{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}]'` Used on: Namespace This annotation is only useful when the (alpha) [PodTolerationRestriction](/docs/reference/access-authn-authz/admission-controllers/#podtolerationrestriction) admission controller is enabled. The annotation value is a JSON document that defines a list of allowed tolerations for the namespace it annotates. When you create a Pod or modify its tolerations, the API server checks the tolerations to see if they are mentioned in the allow list. The pod is admitted only if the check succeeds. </ins> ### scheduler.alpha.kubernetes.io/preferAvoidPods (deprecated) {#scheduleralphakubernetesio-preferavoidpods} Used on: Nodes
Change:
Hi, apt-transport-https is a dummy package since apt 1.5, means it's not needed anymore as of Debian 10 and Ubuntu 18.04.
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
/retitle Linux kubectl package install instructions recommend dummy package This issue is about /kind cleanup /language en The fix would be to omit mentioning , provided that we are confident that all readers are using at least Debian 10. I think the Ubuntu side of things we can take for granted. /priority awaiting-more-evidence
We can also rather add a piece of text, something like: sh sudo apt-get install -y apt-transport-https '``
- would you be willing to update the issue description to incorporate the idea from ?
I have this PR raised. I hope that helps.
/assign
Sorry, didn't see this earlier. However, looks like already did exactly this in .

Discussion:
```shell sudo apt-get update <del> sudo apt-get install -y apt-transport-https ca-certificates curl </del> <ins> sudo apt-get install -y ca-certificates curl </ins> ``` <ins> {{< note >}} If you use Debian 9 (stretch) or earlier you would also need to install `apt-transport-https`: ```shell sudo apt-get install -y apt-transport-https ``` {{< /note >}} </ins> 2. Download the Google Cloud public signing key: ```shell
Change:
Саму тому контейнери вважаються легковісними - wrong Саме тому контейнери вважаються легковаговими - right
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 uk
/retitle [uk] Incorrect localization for What Is Kubernetes
Thanks
/assign

Discussion:
<!-- **Container deployment era:** Containers are similar to VMs, but they have relaxed isolation properties to share the Operating System (OS) among the applications. Therefore, containers are considered lightweight. Similar to a VM, a container has its own filesystem, CPU, memory, process space, and more. As they are decoupled from the underlying infrastructure, they are portable across clouds and OS distributions. --> <del> **Ера розгортання контейнерів:** Контейнери схожі на VM, але мають спрощений варіант ізоляції і використовують спільну операційну систему для усіх застосунків. Саму тому контейнери вважаються легковісними. Подібно до VM, контейнер має власну файлову систему, ЦПУ, пам'ять, простір процесів тощо. Оскільки контейнери вивільнені від підпорядкованої інфраструктури, їх можна легко переміщати між хмарними провайдерами чи дистрибутивами операційних систем. </del> <ins> **Ера розгортання контейнерів:** Контейнери схожі на VM, але мають спрощений варіант ізоляції і використовують спільну операційну систему для усіх застосунків. Саме тому контейнери вважаються "легкими", в порівнянні з віртуалками. Подібно до VM, контейнер має власну файлову систему, ЦПУ, пам'ять, простір процесів тощо. Оскільки контейнери вивільнені від підпорядкованої інфраструктури, їх можна легко переміщати між хмарними провайдерами чи дистрибутивами операційних систем. </ins> <!-- Containers have become popular because they provide extra benefits, such as: -->
Change:
If we are using as our custom image, why do the documentation starts by telling the user to build an image from Dockerfile provided and the code?
Page:
/retitle HorizontalPodAutoscaler walkthrough page recommends unnecessary container image build /kind bug /language en /triage accepted Thanks for reporting this.
I could take this up /assign

Discussion:
## Run and expose php-apache server <del> To demonstrate a HorizontalPodAutoscaler, you will first make a custom container image that uses the `php-apache` image from Docker Hub as its starting point. The `Dockerfile` is ready-made for you, and has the following content: ```dockerfile FROM php:5-apache COPY index.php /var/www/html/index.php RUN chmod a+rx index.php ``` This code defines a simple `index.php` page that performs some CPU intensive computations, in order to simulate load in your cluster. ```php <?php $x = 0.0001; for ($i = 0; $i <= 1000000; $i++) { $x += sqrt($x); } echo "OK!"; ?> ``` Once you have made that container image, start a Deployment that runs a container using the image you made, and expose it as a {{< glossary_tooltip term_id="service">}} </del> <ins> To demonstrate a HorizontalPodAutoscaler, you will first start a Deployment that runs a container using the `hpa-example` image, and expose it as a {{< glossary_tooltip term_id="service">}} </ins> using the following manifest: {{< codenew file="application/php-apache.yaml" >}}

spec: containers: - name: php-apache <del> image: k8s.gcr.io/hpa-example </del> <ins> image: registry.k8s.io/hpa-example </ins> ports: - containerPort: 80 resources:
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The section tells to run the following command: kubectl get pods -l run=my-nginx -o yaml | grep podIP When I run this command, I get the following output: % kubectl get pods -l run=my-nginx -o yaml | grep podIP f:podIP: {} f:podIPs: podIP: 172.17.0.6 podIPs: f:podIP: {} f:podIPs: podIP: 172.17.0.7 podIPs: Proposed Solution: I'd use -custom-columns rather than grep to obtain the pods IP: kubectl get pods -l run=my-nginx -o custom- 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
/assign

Discussion:
Check your pods' IPs: ```shell <del> kubectl get pods -l run=my-nginx -o yaml | grep podIP podIP: 10.244.3.4 podIP: 10.244.2.5 </del> <ins> kubectl get pods -l run=my-nginx -o custom-columns=POD_IP:.status.podIPs POD_IP [map[ip:10.244.3.4]] [map[ip:10.244.2.5]] </ins> ``` You should be able to ssh into any node in your cluster and use a tool such as `curl` to make queries against both IPs. Note that the containers are *not* using port 80 on the node, nor are there any special NAT rules to route traffic to the pod. This means you can run multiple nginx pods on the same node all using the same `containerPort`, and access them from any other pod or node in your cluster using the assigned IP address for the Service. If you want to arrange for a specific port on the host Node to be forwarded to backing Pods, you can - but the networking model should mean that you do not need to do so.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The section "Securing the Service" tells to run the following command: kubectl get pods -o yaml | grep -i podip When I run this command, I get the following output: % kubectl get pods -o yaml | grep -i podip f:podIP: {} f:podIPs: podIP: 172.17.0.6 podIPs: f:podIP: {} f:podIPs: podIP: 172.17.0.3 podIPs: which includes the pod IP of the curl deployment that was started earlier in this tutorial. Proposed Solution: This command should limit the output to the my-nginx, by including a selector: % kubectl get pods -l run=my-nginx -o yaml | grep -i podip 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
/assign

Discussion:
At this point you can reach the nginx server from any node. ```shell <del> kubectl get pods -o yaml | grep -i podip podIP: 10.244.3.5 </del> <ins> kubectl get pods -l run=my-nginx -o custom-columns=POD_IP:.status.podIPs POD_IP [map[ip:10.244.3.5]] ``` ```shell </ins> node $ curl -k https://10.244.3.5 ... <h1>Welcome to nginx!</h1>
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Proposed Solution: Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: (from the same page!) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /language en /good-first-issue /priority backlog /triage accepted
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 downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: based on the calculation <!--Kubernetes Version:--/kind cleanup /language en /good-first-issue /priority backlog /triage accepted </details
/assign

Discussion:
An example is an existing application that assumes a particular well-known environment variable holds a unique identifier. One possibility is to wrap the <del> application, but that is tedious and error prone, and it violates the goal of low </del> <ins> application, but that is tedious and error-prone, and it violates the goal of low </ins> coupling. A better option would be to use the Pod's name as an identifier, and inject the Pod's name into the well-known environment variable.

If CPU and memory limits are not specified for a container, and you use the downward API to try to expose that information, then the kubelet defaults to exposing the maximum allocatable value for CPU and memory <del> (based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) calculation). </del> <ins> based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) calculation. </ins> ## {{% heading "whatsnext" %}}
Change:
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

Discussion:
### 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
Change:
I'm learning kubernetes and stepping through the various scenarios. I came across an issue that I can't tell if it is my own fault or some subtle issue with the yaml file. When I try to execute: kubectl apply -f After successfully doing the previous steps, I get: kubectl apply -f The StatefulSet "mysql" is invalid: Invalid value: map[string]string{"app":"mysql", "":"mysql"}: does not match template Should the mysql- be altered on line 15 (app: mysql) to match line 8 (app: mysql-server)? Or is there some other subtlety about label matching that will break how this app is structured? Thanks
HI , Edit your YAML files and set the same key-value pairs in both and
I am afraid to say that your suggestion is not a proper solution. If K8s doc has bug, then it would be great to fix that. This is reproducible for me. /triage accepted And rather than your suggestion ( L15 → ), I suggest this: [L8 in ] This will make the work.
I'd love to work on this /assign
Oops. This was introduced by - which I thought I'd fixed. Sorry about that.

Discussion:
spec: selector: matchLabels: <del> app: mysql-server </del> <ins> app: mysql </ins> app.kubernetes.io/name: mysql serviceName: mysql replicas: 3
Change:
kubectlNodroblem Detector ↓ kubectlNode Problem Detector <img width="849" alt="Screen Shot 2022-06-23 at 15 43 53" src="https://user-"
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 ja /kind bug
/assign

Discussion:
クラウドプロバイダーによっては、`Node Problem Detector`を{{< glossary_tooltip text="Addon" term_id="addons" >}}として有効にしている場合があります。 また、`kubectl`を使って`Node Problem Detector`を有効にするか、`Addon pod`を作成することで有効にできます。 <del> ### kubectlを使用してNodしますroblem Detectorを有効にします {#using-kubectl} </del> <ins> ### kubectlを使用してNode Problem Detectorを有効化します {#using-kubectl} </ins> `kubectl`は`Node Problem Detector`を最も柔軟に管理することができます。 デフォルトの設定を上書きして自分の環境に合わせたり、カスタマイズしたノードの問題を検出したりすることができます。
Change:
as of now : [default configuration(https://..... expected : [default configuration](https://... <img width="800" alt="Screen Shot 2022-06-24 at 18 40 25" src="https://user-"
/triage accepted /language ja
/assign

Discussion:
## コンフィギュレーションを上書きします <del> `Node Problem Detector`の Dockerイメージをビルドする際に、[default configuration(https://github.com/kubernetes/node-problem-detector/tree/v0.1/config)が埋め込まれます。 </del> <ins> `Node Problem Detector`の Dockerイメージをビルドする際に、[default configuration](https://github.com/kubernetes/node-problem-detector/tree/v0.1/config)が埋め込まれます。 </ins> [`ConfigMap`](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/) を使用することで設定を上書きすることができます。