jiebi/CodeConvo huggingface dataset:
Change:
Umbrella issue: Investigate removing and its containing folder. This appears to be a script for a slack bot. To my knowledge, we don't use any slack bots. I think it's safe to remove this.
/help /good-first-issue /kind-cleanup /priority important-longterm
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 : /help /good-first-issue /kind-cleanup /priority important-longterm 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 cleanup
/assign

Discussion:
<del> "use strict"; const { IncomingWebhook } = require('@slack/client'), kubernetesSiteRoot = 'https://kubernetes.io', fetch = require('node-fetch').default, { SLACK_WEBHOOK_URL } = process.env; const webhook = new IncomingWebhook(SLACK_WEBHOOK_URL); // A random smattering of Kubernetes documentation pages // We can add as many pages here as we'd like const kubernetesEndpoints = [ 'docs/home', 'docs/tutorials/configuration/configure-redis-using-configmap', ] // Ensure that the SLACK_WEBHOOK_URL environment variable is set const checkEnv = () => { if (!SLACK_WEBHOOK_URL) { return { statusCode: 422, body: "[FAILURE] The Slack webhook URL must be set via the SLACK_WEBHOOK_URL environment variable" } } } // This function posts a warning message to Slack const sendSlackMessage = (msg) => { const slackMessageObject = { username: "noindex checker", text: msg } // Send the message to the webhook webhook.send(slackMessageObject, (err, res) => { return (err) ? { statusCode: 422, body: `[ERROR] Slack webhook error: ${err}` } : { statusCode: 200, body: `[SUCCESS] Response received from Slack: ${JSON.stringify(res)}` }; }); } // Iterate through each Kubernetes endpoint to check for noindex headers const checkEndpoints = () => { kubernetesEndpoints.forEach((endpoint) => { const url = `${kubernetesSiteRoot}/${endpoint}`; fetch(url) .then(res => { const headers = res.headers; if ('x-robots-tag' in headers.raw() && (headers.get('x-robots-tag') == 'noindex')) { const msg = `[WARNING] "X-Robots-Tag: noindex" header found on the following page: ${url}`; // Send Slack notification sendSlackMessage(msg); return { statusCode: 404, body: msg }; } else { const msg = `[SUCCESS] No improper X-Robots-Tag: noindex headers found on ${url}`; return { statusCode: 200, body: msg }; } }) .catch(err => { return { statusCode: 422, body: err }; }); }); } // The handler function exports.handler = async (event, context) => { checkEnv(); // Below are the various deploy succeeded checks checkEndpoints(); } </del>
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 following documents contain the broken link which points to the wrong section name: concepts/storage/storage-[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#class-1) tasks/administer-cluster/change-default-storage-[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#class-1) Proposed Solution: Fix the wrong section name as the below: concepts/storage/storage-[PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) tasks/administer-cluster/change-default-storage-[PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
/kind bug

Discussion:
Administrators can specify a default StorageClass just for PVCs that don't request any particular class to bind to: see the <del> [PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#class-1) </del> <ins> [PersistentVolumeClaim section](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) </ins> for details. ```yaml

an existing StorageClass that is marked as default. This default StorageClass is then used to dynamically provision storage for PersistentVolumeClaims that do not require any specific storage class. See <del> [PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#class-1) </del> <ins> [PersistentVolumeClaim documentation](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) </ins> for details. The pre-installed default StorageClass may not fit well with your expected workload;
Change:
Expected behavior: https://v1- (drop-downs work) Actual behavior: (drop-downs do not work) This may be a issue or a result of non-translated pages not showing up in autogenerated navs. I'm unsure.
/assign /priority important-soon /kind bug
Hello, calestehorgan I investigated this problem quickly and found that (this is the version and language box) seemed to remain when the mouse cursor has hovered. ! Adding the following style makes the problem disappeared: ! Maybe some style is missing or something blocks a style applied.
Thank you for the help!! I'll try it out.
I'm glad to help!

Discussion:
left: 0; background: #fff; } <del> .dropdown-menu { left: -80px; } &.dropdown:hover { color: $medium-grey; } </del> } }

} } } <del> } </del> <ins> } </ins>  No newline at end of file

{{ partialCached "footer.html" . }} <!-- Disabling this as elements queries do not appear to exist on case studies --> <!-- {{ partialCached "footer-scripts.html" . }} --> <ins> {{ partialCached "scripts.html" . }} </ins> </body> </html>  No newline at end of file

<ins> {{/* Link directly to documentation etc., if possible. */}} {{ $langPage := cond (gt (len .Translations) 0) . .Site.Home }} <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> {{ $langPage.Language.LanguageName }} </a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> {{ range $langPage.Translations }} <a class="dropdown-item" href="{{ .RelPermalink }}">{{ .Language.LanguageName }}</a> {{ end }} </div> </ins>  No newline at end of file

<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> <del> {{ T "version_menu" }} </del> <ins> {{ T "version_menu" }} </ins> </a> <del> <div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink"> </del> <ins> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> </ins> {{ range .Site.Params.versions }} <a class="dropdown-item" href="{{ .url }}">{{ .version }}</a> {{ end }} <del> </div> </del> <ins> </div> </ins>  No newline at end of file
Change:
This paragraph is a bit backwards. It would be more intuitive to start with the "Make sure that the br_netfilter module is loaded before this step..." phrases.
/language en /kind cleanup /priority backlog /good-first-issue Thanks
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 : /language en /kind cleanup /priority backlog /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
/sig cluster-lifecycle

Discussion:
## Letting iptables see bridged traffic <ins> Make sure that the `br_netfilter` module is loaded. This can be done by running `lsmod | grep br_netfilter`. To load it explicitly call `sudo modprobe br_netfilter`. </ins> As a requirement for your Linux Node's iptables to correctly see bridged traffic, you should ensure `net.bridge.bridge-nf-call-iptables` is set to 1 in your `sysctl` config, e.g. ```bash

sudo sysctl --system ``` <del> Make sure that the `br_netfilter` module is loaded before this step. This can be done by running `lsmod | grep br_netfilter`. To load it explicitly call `sudo modprobe br_netfilter`. </del> For more details please see the [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) page. ## Check required ports
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 page is 404: Proposed Solution: Find correct link and update the url Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Seems it should be this... I'll update it and submit a PR /assign

Discussion:
## {{% heading "whatsnext" %}} <del> - Read [Debugging DNS Resolution](/docs/tasks/debug-application-cluster/dns-debugging-resolution/) </del> <ins> - Read [Debugging DNS Resolution](/docs/tasks/administer-cluster/dns-debugging-resolution/) </ins>
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: Current page is lost when switching between documentation versions. Steps to reproduce to some page in the docs, for example the version selector at the top of the page to change to 1.17. that it it sends me to the instead of showing me the . Proposed Solution: Keep the relative path when switching versions Page to Update: All <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: Am I wrong that it used to preserve the page you are on when switching versions? I feel like it used to do that, but I'm not 100% sure.
Yes, at some point the site kept the same page when switching between versions.
/kind bug /priority backlog (I think this is a low-priority-backlog sort of issue; it's a frustration, but we have other places where it makes sense to focus effort first).
/area web-development

Discussion:
{{ define "main" }} <ins> {{ partial "handle-version-switch-404.html" . }} </ins> <div class="container-404"> <h4> Perhaps you were looking for:

<ins> {{/* If a 404 occurs and the referrer is a different version of the Kubernetes documentation, don't show the regular 404 error page, but instead redirect to the site root */}} <script type="text/javascript"> var sameBaseUrlRegExp = new RegExp("^" + location.protocol + "//" + location.host.replace(".", ".") + "/.*", "i"); var kubernetesDocumentationUrlRegExp = new RegExp("^https?://(.+.)?kubernetes.io/.*", "i"); if (!sameBaseUrlRegExp.test(document.referrer) && kubernetesDocumentationUrlRegExp.test(document.referrer)) { location.replace("/"); } </script> </ins>

{{ T "version_menu" }} </a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> <ins> {{ $p := . }} </ins> {{ range .Site.Params.versions }} <del> <a class="dropdown-item" href="{{ .url }}">{{ .version }}</a> </del> <ins> <a class="dropdown-item" href="{{ .url }}{{ $p.RelPermalink }}">{{ .version }}</a> </ins> {{ end }} </div>  No newline at end of file
Change:
This is a Bug Report Problem: The "background" sections describes volumes as if they all were ephemeral: It also starts with a comparison against Docker, which may or may not still make sense. Proposed Solution: Rewrite and link to the persistent- and (once is merged) to ephemeral- Page to Update:
/sig storage /priority backlog I definitely agree about the Docker stuff - there's no need to focus on a particular runtime, nor on Docker as a local development tool.
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. 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 /lifecycle frozen
/triage accepted
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
/triage accepted
/assign

Discussion:
## Background <del> Docker has a concept of [volumes](https://docs.docker.com/storage/), though it is somewhat looser and less managed. A Docker volume is a directory on disk or in another container. Docker provides volume drivers, but the functionality is somewhat limited. </del> Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod" text="Pod" >}} can use any number of volume types simultaneously. [Ephemeral volume](/docs/concepts/storage/ephemeral-volumes/) types have a lifetime of a pod,
Change:
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.

Discussion:
{{ 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) }}

<script src="{{ "js/script.js" | relURL }}"></script> {{ with .Params.js }}{{ range (split . ",") }}<script src="{{ (trim . " ") | relURL }}"></script><!-- custom js added --> <del> {{ end }}{{ else }}<!-- no custom js detected -->{{ end }} </del>  No newline at end of file <ins> {{ end }}{{ else }}<!-- no custom js detected -->{{ end }} </ins>

{{/* Link directly to documentation etc., if possible. */}} {{ $langPage := cond (gt (len .Translations) 0) . .Site.Home }} <del> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> </del> <ins> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownMenuLink" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> </ins> {{ $langPage.Language.LanguageName }} </a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> {{ range $langPage.Translations }} <a class="dropdown-item" href="{{ .RelPermalink }}">{{ .Language.LanguageName }}</a> {{ end }} <del> </div> </del>  No newline at end of file <ins> </div> </ins>
Change:
Greetings,Running CentOS 8... This is what the docs say: systemd To use the systemd cgroup driver, set = true in When using kubeadm, manually configure the cgroup driver for kubelet So this is what I did: disabledplugins = ["cri"] = true This caused these errors: -- Unit docker.service has begun starting up. Jul 19 10:07:45 containerd[]: containerd: Near line 2 (last key parsed ''): bare keys cannot contain '.' Jul 19 10:07:45 systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE Jul 19 10:07:45 systemd[1]: containerd.service: Failed with result 'exit-code'. Jul 19 10:07:45 systemd[1]: Stopped Docker Application Container Engine. -- Subject: Unit docker.service has finished shutting down -- Defined-By: systemd -- Support: -- Unit docker.service has finished shutting down. And: -- Unit docker.service has begun starting up. Jul 19 09:53:05 containerd[]: containerd: Near line 2 (last key parsed ''): bare keys cannot contain '.' Jul 19 09:53:05 systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE Jul 19 09:53:05 systemd[1]: containerd.service: Failed with result 'exit-code'. Jul 19 09:53:05 systemd[1]: Stopped Docker Application Container Engine. -- Subject: Unit docker.service has finished shutting down -- Defined-By: systemd -- Support: -- Unit docker.service has finished shutting down. Changed the code to this: [] systemdcgroup = true It now works!
/sig cluster-lifecycle
would you be willing to with the fixes? It sounds like you have a good idea of what these would be.
this change seems fine. PR welcome.
/priority backlog /language en

Discussion:
### systemd <del> To use the `systemd` cgroup driver, set `plugins.cri.systemd_cgroup = true` in `/etc/containerd/config.toml`. </del> <ins> To use the `systemd` cgroup driver in `/etc/containerd/config.toml` set ``` [plugins.cri] systemd_cgroup = true ``` </ins> When using kubeadm, manually configure the [cgroup driver for kubelet](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#configure-cgroup-driver-used-by-kubelet-on-control-plane-node)
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: is returning 404 Proposed Solution: The correct link is at but that still seems kinda wrong just from what the path looks like. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
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 Seems like straight forward fix to adjust the link 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

Discussion:
--- title: Opening a pull request <del> slug: new-content </del> content_type: concept weight: 10 card:
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 monitoring page on the Kubernetes website has a link to in the What's Next section which links to an empty list in GitHub. Proposed Solution: I have been unable to find another list of stable metrics. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Looks wrong to me. /language en /priority backlog /kind bug
Duplicated by issue
I tried to compile the generated content of the file locally, but I didn't get any results. It was generated using , but there are bugs and need to be fixed.
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. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /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
/reopen /assign
Reopened this issue. <detailsIn response to : /reopen /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
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
/remove-lifecycle rotten

Discussion:
## {{% heading "whatsnext" %}} * Read about the [Prometheus text format](https://github.com/prometheus/docs/blob/master/content/docs/instrumenting/exposition_formats.md#text-based-format) for metrics <del> * See the list of [stable Kubernetes metrics](https://github.com/kubernetes/kubernetes/blob/master/test/instrumentation/testdata/stable-metrics-list.yaml) </del> * Read about the [Kubernetes deprecation policy](/docs/reference/using-api/deprecation-policy/#deprecating-a-feature-or-behavior)
Change:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /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

Discussion:
<ins> --- title: 拡張リソースをコンテナに割り当てる content_type: task weight: 40 --- <!-- overview --> {{< feature-state state="stable" >}} このページでは、拡張リソースをコンテナに割り当てる方法について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} この練習を始める前に、[Nodeに拡張リソースをアドバタイズする](/ja/docs/tasks/administer-cluster/extended-resource-node/)の練習を行ってください。これにより、Nodeの1つがドングルリソースをアドバタイズするように設定されます。 <!-- steps --> ## 拡張リソースをPodに割り当てる 拡張リソースをリクエストするには、コンテナのマニフェストに`resources:requests`フィールドを含めます。拡張リソースは、`*.kubernetes.io/`以外の任意のドメインで完全修飾されます。有効な拡張リソース名は、`example.com/foo`という形式になります。ここで、`example.com`はあなたの組織のドメインで、`foo`は記述的なリソース名で置き換えます。 1つのコンテナからなるPodの構成ファイルを示します。 {{< codenew file="pods/resource/extended-resource-pod.yaml" >}} 構成ファイルでは、コンテナが3つのdongleをリクエストしていることがわかります。 次のコマンドでPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/resource/extended-resource-pod.yaml ``` Podが起動したことを確認します。 ```shell kubectl get pod extended-resource-demo ``` Podの説明を表示します。 ```shell kubectl describe pod extended-resource-demo ``` dongleのリクエストが表示されます。 ```yaml Limits: example.com/dongle: 3 Requests: example.com/dongle: 3 ``` ## 2つ目のPodの作成を試みる 以下に、1つのコンテナを持つPodの構成ファイルを示します。コンテナは2つのdongleをリクエストします。 {{< codenew file="pods/resource/extended-resource-pod-2.yaml" >}} Kubernetesは、2つのdongleのリクエストを満たすことができません。1つ目のPodが、利用可能な4つのdongleのうち3つを使用してしまっているためです。 Podを作成してみます。 ```shell kubectl apply -f https://k8s.io/examples/pods/resource/extended-resource-pod-2.yaml ``` Podの説明を表示します。 ```shell kubectl describe pod extended-resource-demo-2 ``` 出力にはPodがスケジュールできないことが示されます。2つのdongleが利用できるNodeが存在しないためです。 ``` Conditions: Type    Status PodScheduled  False ... Events: ... ... Warning   FailedScheduling  pod (extended-resource-demo-2) failed to fit in any node fit failure summary on nodes : Insufficient example.com/dongle (1) ``` Podのステータスを表示します。 ```shell kubectl get pod extended-resource-demo-2 ``` 出力には、Podは作成されたものの、Nodeにスケジュールされなかったことが示されています。PodはPending状態になっています。 ```yaml NAME                       READY     STATUS    RESTARTS   AGE extended-resource-demo-2   0/1       Pending   0          6m ``` ## クリーンアップ この練習で作成したPodを削除します。 ```shell kubectl delete pod extended-resource-demo kubectl delete pod extended-resource-demo-2 ``` ## {{% heading "whatsnext" %}} ### アプリケーション開発者向け * [コンテナおよびPodへのメモリーリソースの割り当て](/ja/docs/tasks/configure-pod-container/assign-memory-resource/) * [コンテナおよびPodへのCPUリソースの割り当て](/ja/docs/tasks/configure-pod-container/assign-cpu-resource/) ### クラスター管理者向け * [Nodeに拡張リソースをアドバタイズする](/ja/docs/tasks/administer-cluster/extended-resource-node/) </ins>