jiebi/CodeConvo huggingface dataset:
Change:
* Container Resource Monitoring * [Setup instructions](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/) * GUI <del> * [Setup instructions](https://github.com/kubernetes/kube-ui) cluster. </del> <ins> * [Setup instructions](https://github.com/kubernetes/dashboard) </ins> ## Troubleshooting

Discussion:
Connect with Proxies references kube ui. It should use the kube dashboard instead.
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
Change:
### 言語と文法 - 言語や文法に明らかな間違いはないですか？ もっとよい言い方はないですか？ <ins> - 作成者が変更している箇所の用語や文法に注目してください。作成者がページ全体の変更を目的として明確にしていない限り、そのページのすべての問題を修正する義務はありません。 - 既存のページを変更するPRである場合、変更されている箇所に注目してレビューしてください。その変更されたコンテンツは、技術的および編集の正確性についてレビューしてください。PRの作成者が対処しようとしている内容と直接関係のない間違いを見つけた場合、それは別のIssueとして扱うべきです(既存のIssueが無いことを確認してください)。 - コンテンツを*移動*するPull Requestに注意してください。作成者がページの名前を変更したり、2つのページを結合したりする場合、通常、私たち(Kubernetes SIG Docs)は、その移動されたコンテンツ内で見つけられるすべての文法やスペルの間違いを修正することを作成者に要求することを避けています。 </ins> - もっと簡単な単語に置き換えられる複雑な単語や古い単語はありませんか？ - 使われている単語や専門用語や言い回しで差別的ではない別の言葉に置き換えられるものはありませんか？ - 言葉選びや大文字の使い方は[style guide](/docs/contribute/style/style-guide/)に従っていますか？

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. It contains important information for contributors. Comments /language ja /assign
/triage accepted
Change:
reviewers: - liggitt - cheftako <del> description: Configure the kubelet's image credential provider plugin </del> content_type: task min-kubernetes-server-version: v1.26 weight: 120

Discussion:
This is a Bug Report Problem: Sub section " under is having a redundant text(sub section name is repeating as a normal text). ! Proposed Solution: Remove the text that present under "Configure a kubelet image credential provider". Page to Update:
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 docs /language en
I want to help with this. /assign
I try to fix this in
Change:
However, the particular path specified in the custom recycler Pod template in the `volumes` part is replaced with the particular path of the volume that is being recycled. <ins> ### Reserving a PersistentVolume The control plane can [bind PersistentVolumeClaims to matching PersistentVolumes](#binding) in the cluster. However, if you want a PVC to bind to a specific PV, you need to pre-bind them. By specifying a PersistentVolume in a PersistentVolumeClaim, you declare a binding between that specific PV and PVC. If the PersistentVolume exists and has not reserved PersistentVolumeClaims through its `claimRef` field, then the PersistentVolume and PersistentVolumeClaim will be bound. The binding happens regardless of some volume matching criteria, including node affinity. The control plane still checks that [storage class](https://kubernetes.io/docs/concepts/storage/storage-classes/), access modes, and requested storage size are valid. ``` apiVersion: v1 kind: PersistentVolumeClaim metadata: name: foo-pvc namespace: foo spec: volumeName: foo-pv ... ``` This method does not guarantee any binding privileges to the PersistentVolume. If other PersistentVolumeClaims could use the PV that you specify, you first need to reserve that storage volume. Specify the relevant PersistentVolumeClaim in the `claimRef` field of the PV so that other PVCs can not bind to it. ``` apiVersion: v1 kind: PersistentVolume metadata: name: foo-pv spec: claimRef: name: foo-pvc namespace: foo ... ``` This is useful if you want to consume PersistentVolumes that have their `claimPolicy` set to `Retain`, including cases where you are reusing an existing PV. </ins> ### Expanding Persistent Volumes Claims {{< feature-state for_k8s_version="v1.11" state="beta" >}}

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. --Document Volume and Claim Pre-binding feature. Why is this needed PVC & PV pre-binding is useful sometimes, but this feature is not documented in our official website. It's better to add a topic or subtopic for it. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/sig storage cc /assign working on it
Change:
<ins> apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: multi-port-egress namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Egress egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 32000 endPort: 32768 </ins>

Discussion:
I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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 Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign
Change:
</div> </div> <del> <section> </del> <ins> <section id="get-certified"> </ins> <div class="main-section padded"> <del> <center> <h2>Get Kubernetes Certified</h2> </center> </del> <ins> <h2>Get Kubernetes Certified</h2> </ins> <div class="col-container"> <div class="col-nav"> <del> <center> </del> <h5> <b>Certified Kubernetes Application Developer (CKAD)</b> </h5> <p>The Certified Kubernetes Application Developer exam certifies that users can design, build, configure, and expose cloud native applications for Kubernetes.</p> <ins> <p>A CKAD can define application resources and use core primitives to build, monitor, and troubleshoot scalable applications and tools in Kubernetes.</p> </ins> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-application-developer-ckad/" target="_blank" class="button">Go to Certification</a> <del> </center> </del> </div> <div class="col-nav"> <del> <center> </del> <h5> <b>Certified Kubernetes Administrator (CKA)</b> </h5> <p>The Certified Kubernetes Administrator (CKA) program provides assurance that CKAs have the skills, knowledge, and competency to perform the responsibilities of Kubernetes administrators.</p> <ins> <p>A certified Kubernetes administrator has demonstrated the ability to do basic installation as well as configuring and managing production-grade Kubernetes clusters.</p> </ins> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/" target="_blank" class="button">Go to Certification</a> <del> </center> </del> <ins> </div> <div class="col-nav"> <h5> <b>Certified Kubernetes Security Specialist (CKS)</b> </h5> <p>The Certified Kubernetes Security Specialist program provides assurance that the holder is comfortable and competent with a broad range of best practices. CKS certification covers skills for securing container-based applications and Kubernetes platforms during build, deployment and runtime.</p> <p><em>Candidates for CKS must hold a current Certified Kubernetes Administrator (CKA) certification to demonstrate they possess sufficient Kubernetes expertise before sitting for the CKS.</em></p> <br> <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/" target="_blank" class="button">Go to Certification</a> </ins> </div> </div> </div>

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 Update to mention the new Kubernetes Security Specialist Certification Why is this needed There is a Kubernetes Security Specialist Certification, coming in November 2020. Comments /kind feature /language en
/priority important-soon
let's collaborate to put everything in place to make this into a Good First Issue.
Design-wise, it's much easier to place 2 certification logos than 3. do you have any thoughts on how to adjust things design-wise to incorporate the 3rd certification?
/sig security
/triage accepted
/cc
Change:
--- <del> title: Guide for scheduling Windows containers in Kubernetes </del> <ins> title: KubernetesでWindowsコンテナをスケジュールするためのガイド </ins> content_type: concept weight: 75 --- <!-- overview --> <del> Windows applications constitute a large portion of the services and applications that run in many organizations. This guide walks you through the steps to configure and deploy a Windows container in Kubernetes. </del> <ins> Windowsアプリケーションは、多くの組織で実行されるサービスとアプリケーションの大部分を占めます。このガイドでは、KubernetesでWindowsコンテナを構成してデプロイする手順について説明します。 </ins> <!-- body --> <del> ## Objectives </del> <ins> ## 目的 </ins> <del> * Configure an example deployment to run Windows containers on the Windows node * (Optional) Configure an Active Directory Identity for your Pod using Group Managed Service Accounts (GMSA) </del> <ins> * WindowsノードでWindowsコンテナを実行するサンプルのDeploymentを構成します * (オプション)Group Managed Service Accounts(GMSA)を使用してPodのActive Directory IDを構成します </ins> <del> ## Before you begin </del> <ins> ## 始める前に </ins> <del> * Create a Kubernetes cluster that includes a [master and a worker node running Windows Server](/ja/docs/setup/production-environment/windows/user-guide-windows-nodes/) * It is important to note that creating and deploying services and workloads on Kubernetes behaves in much the same way for Linux and Windows containers. [Kubectl commands](/docs/reference/kubectl/overview/) to interface with the cluster are identical. The example in the section below is provided simply to jumpstart your experience with Windows containers. </del> <ins> * [Windows Serverを実行するマスターノードとワーカーノード](/ja/docs/setup/production-environment/windows/user-guide-windows-nodes/)を含むKubernetesクラスターを作成します * Kubernetes上にServiceとワークロードを作成してデプロイすることは、LinuxコンテナとWindowsコンテナ共に、ほぼ同じように動作することに注意してください。クラスターとのインタフェースとなる[Kubectlコマンド](/docs/reference/kubectl/overview/)も同じです。Windowsコンテナをすぐに体験できる例を以下セクションに用意しています。 </ins> <del> ## Getting Started: Deploying a Windows container </del> <ins> ## はじめに:Windowsコンテナのデプロイ </ins> <del> To deploy a Windows container on Kubernetes, you must first create an example application. The example YAML file below creates a simple webserver application. Create a service spec named `win-webserver.yaml` with the contents below: </del> <ins> WindowsコンテナをKubernetesにデプロイするには、最初にサンプルアプリケーションを作成する必要があります。以下のYAMLファイルの例では、簡単なウェブサーバーアプリケーションを作成しています。以下の内容で`win-webserver.yaml`という名前のサービススペックを作成します。: </ins> ```yaml apiVersion: v1

Discussion:
This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/user-guide-windows-containers/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign
Change:
## kubelet configuration <del> Finally, with the master nodes properly set up and all of the necessary authentication and authorization in place, we can configure the kubelet. </del> <ins> Finally, with the control plane nodes properly set up and all of the necessary authentication and authorization in place, we can configure the kubelet. </ins> The kubelet requires the following configuration to bootstrap:

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: uses the outdated term “master” and “master node”. Proposed Solution: Replace references to the control plane that use the term “master” with the current term: “control plane”. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind cleanup /wg naming
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 “Kubelet TLS Bootstrapping” uses outdated wording
I would like to take up this issue
/assign
Change:
`metadata.labels['<KEY>']` : the text value of the pod's {{< glossary_tooltip text="label" term_id="label" >}} named `<KEY>` (for example, `metadata.labels['mylabel']`) <ins> The following information is available through environment variables **but not as a downwardAPI volume fieldRef**: </ins> `spec.serviceAccountName` : the name of the pod's {{< glossary_tooltip text="service account" term_id="service-account" >}}

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: Documentation should state that spec and status downward API fields are only available as environment variables, not as files. Proposed Solution: Add text before spec.serviceAccountName stating: Then for consistency, a few lines down change: to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: Confirmed on v1.24 and v1.25 Additional Information: Error message from kubectl (1.25) apply shows which values are allowed for each type (line breaks for readability)
Thanks for the report /sig node
/triage accepted sounds reasonable, thank you
I would like to give a try on this. /assign
Change:
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <ins> Ensure that your cluster has the `StorageVersionMigrator` and `InformerResourceVersion` [feature gates](/docs/reference/command-line-tools-reference/feature-gates/) enabled. You will need control plane administrator access to make that change. Enable storage version migration REST api by setting runtime config `storagemigration.k8s.io/v1alpha1` to `true` for the API server. For more information on how to do that, read [enable or disable a Kubernetes API](/docs/tasks/administer-cluster/enable-disable-api/). </ins> <!-- steps --> ## Re-encrypt Kubernetes secrets using storage version migration

Discussion:
Ref :- /assign /sig api-machinary
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Ref :- /sig api-machinary 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
/triage accepted
/sig api-machinery
What's SVM Contributors might need more of a clue about what work needs doing.
It's storage version migrator
Change:
<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>

Discussion:
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
Change:
# Hindi is disabled because it's currently in development. disableLanguages = ["hi", "no"] <ins> [caches] [caches.assets] dir = ":cacheDir/_gen" maxAge = -1 [caches.getcsv] dir = ":cacheDir/:project" maxAge = "60s" [caches.getjson] dir = ":cacheDir/:project" maxAge = "60s" [caches.images] dir = ":cacheDir/_images" maxAge = -1 [caches.modules] dir = ":cacheDir/modules" maxAge = -1 </ins> [markup] [markup.goldmark] [markup.goldmark.extensions]

Discussion:
This is a Bug Report run : output : my environment: mac version10.14.3 bash: 5.0.11 docker engine19.03.13 Proposed Solution: I try to figure out what's the problem, and I got following clue: line 71 of Makefile: container, list directory of /src/resources : line 32 of Dockerfile: seems it is a permission problem I simply commented out lines 32 of dockerfile , and the problem get solved Page to Update: Makefile Dockerfile
/assign
/cc
/priority important-soon
It seems like the challenge for compatibility is the Docker Desktop product on macOS. The symptoms don't seem to be present on Linux.
/kind bug /triage accepted
Change:
### Установка двоичного файла kubectl с помощью curl в Windows <del> 1. Загрузите последнюю версию {{< param "fullversion" >}} по [этой ссылке](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Загрузите последнюю версию {{< skew currentPatchVersion >}} по [этой ссылке](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe). </ins> Либо, если у вас установлен `curl`, выполните команду ниже: ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe </ins> ``` Последнюю стабильную версию (например, при написании скриптов) вы можете узнать из файла по ссылке [https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt).

Discussion:
Problem: Based on , I have created this issue/task to help update the [ru] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 33: Например, для установки версии {{< param "fullversion" }} на Linux введите: 36: {{< param "fullversion" }}/bin/linux/amd64/kubectl 110: Например, для установки версии {{< param "fullversion" }} на macOS введите: 113: {{< param "fullversion" }}/bin/darwin/amd64/kubectl 175: 1. Загрузите последний релиз {{< param "fullversion" }} по этой ссылке. 180: {{< param "fullversion" }} In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/concepts/containers/container- 44: DNS, если включен . /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/setup/learning- 222: чтобы запустить Minikube из-под версии {{< param "fullversion" }}, вам нужно выполнить следующую команду: 225: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 36: Например, команда загрузки версии {{< param "fullversion" }} для Linux будет выглядеть следующим образом 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: Например, команда загрузки версии {{< param "fullversion" }} для macOS будет выглядеть следующим образом 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 183: 1.

Загрузите последнюю версию {{< param "fullversion" }} по этой ссылкеe
Change:
- title: Nodejs + Mongo path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/nodesjs-mongodb - title: Petstore <del> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8spetstore/ </del> <ins> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8petstore/ </ins>

Discussion:
I wish /docs/samples/ didn't have a broken Petstore link
For the record, the broken link in question is located here: The actual link should be to . At least, that's what it is in the project. Not sure which one we should change ( makes more sense to me).