jiebi/CodeConvo huggingface dataset:
Change:
<!-- overview --> <del> CronJobs was promoted to general availability in Kubernetes v1.21. If you are using an older version of Kubernetes, please refer to the documentation for the version of Kubernetes that you are using, so that you see accurate information. Older Kubernetes versions do not support the `batch/v1` CronJob API. </del> You can use a {{< glossary_tooltip text="CronJob" term_id="cronjob" >}} to run {{< glossary_tooltip text="Jobs" term_id="job" >}} on a time-based schedule. These automated jobs run like [Cron](https://en.wikipedia.org/wiki/Cron) tasks on a Linux or UNIX system.

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There's some text on some of the pages about CronJob ; for example, When Kubernetes v1.25 is released, we can (and think should) remove that text, because none of the versions before 1.21 would be in support. Proposed Solution: Remove that paragraph. :informationsource: make the update on the dev-1.25 branch Page to Update: Kubernetes Version: v1.25 (upcoming)_ Additional Information: /sig apps /language en /kind cleanup /milestone 1.25
/assign
/triage accepted
/assign
/unassign
Thank you
Change:
$($(CertUtil -hashfile .kubectl.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl.exe.sha256) ``` <del> 1. Add the binary in to your `PATH`. </del> <ins> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </ins> 1. Test to ensure the version of `kubectl` is the same as downloaded:

Discussion:
Hello, I have recently and I have noticed that there is a slight error at step 3. Namely, the line says: when it really should be: I have tested it a few times and indeed, adding to PATH does not work, while simply adding yields the correct result (i.e. being able to invoke kubectl commands from the command prompt). I know it is a minor issue but for beginners (like myself) it could make the difference between completing the installation or not. Even though I have not tried other methods of installation, I suspect that the same step should also be corrected in section , where it also says "Add the binary in to your PATH." Best regards, Paula
/triage accepted Similar issue exists in . cf. In : !
is kind of techie vernacular (it's how I'd say it in spoken English to a colleague), but in technical docs we can be more precise. /language en
Hi, I would like to work on this issue. /assign
/sig windows
Change:
To apply Pod Security Standards to specific namespaces, refer to [Apply Pod Security Standards at the namespace level](/docs/tutorials/security/ns-level-pss). <ins> If you are running a version of Kubernetes other than v{{< skew currentVersion >}}, check the documentation for that version. </ins> ## {{% heading "prerequisites" %}} Install the following on your workstation:

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: Apply Pod Security Standards at the Cluster Level documents Pod Security admission defaults, but for Kubernetes v1.23 rather than any more recent release. Proposed Solution: Either: Edit to automatically render with the version of Kubernetes being documented Update for Kubernetes v1.24 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority backlog /lifecycle frozen /triage accepted
What would need to change here? The Kubernetes minor version in the commands or also the version in the intro paragraph? (wouldn't that remain 1.23 since that's when the feature went beta?)
The tutorial shows you how to deploy a v1.23.x cluster; it should be v1.24. Maybe if we don't specify any version explicitly, that's good enough (I haven't checked, and I'm not very familiar with ). Making that version always match the latest release is left as an exercise for the reaser.
Hi, I have a question if we automatically render the Kubernetes version being documented for the page, would it be okay to mention something along the lines of : ? Thanks.
You can use this shortcode to show the version: See for an example.
Great, now I can try to work on this issue on the lines of the example. Thanks. /assign
Change:
<center> <h2>Learn with the Linux Foundation</h2> <p>The Linux Foundation offers instructor-led and self-paced courses for all aspects of the Kubernetes application development and operations lifecycle.</p> <del> <br><br> </del> <ins> <br/><br/> </ins> <a href="https://training.linuxfoundation.org/training/course-catalog/?_sft_technology=kubernetes" target="_blank" class="button">See Courses</a> </center> </div>

Discussion:
This is feedback by email from within the CNCF/Linux Foundation: add the CKA/CKAD logos from to the page.
I'll take care of this, so assign it to me :)
/assign
Change:
The legacy Linux package repositories (`apt.kubernetes.io` and `yum.kubernetes.io` AKA `packages.cloud.google.com`)<br/> have been frozen starting from September 13, 2023 **and are going away in January 2024**, users *must* migrate.<br/> Please read our [announcement](/blog/2023/08/31/legacy-package-repository-deprecation/) for more details. <ins> - name: KubeCon 2024 EU startTime: 2024-02-16T00:00:00  #Added in https://github.com/kubernetes/website/pull/44828 endTime: 2024-03-22T18:00:00 style: >- background: linear-gradient(90deg, rgba(67,53,105,1) 0%, rgba(89,187,234,1) 100%); color: #fffff; title: | <img src ="/images/announcements/kccnc-eu-2024-white.svg" style="float: right; height: 80px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon Europe 2024</a> message: | Join us for four days of incredible opportunities to collaborate, learn and share with the cloud native community.<br/> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/?utm_source=kubernetes&utm_medium=all&utm_campaign=kubeconeu24&utm_content=slim-banner"> Buy your ticket now! 19 - 22 March | Paris, France </a> </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 Set a banner to announce KubeCon 2024 EU Why is this needed We usually turn on a banner for the upcoming KubeCon about 4 weeks ahead of the event, but I've had a request that we run it a bit earlier. Is 8 weeks possible? Logos are available from: (Note: be sure to copy the logo into this repo) should help with text. Also see the config from a previous year's KubeCon. Comments This change will need approval. I would like to set the banner to start on the Jan 26, 2024 and to end on the March 22, 2024 at 1800 CET (UTC+1). If 8 weeks isn't possible, the 4 week dates are Feb 23, 2024 to March 22, 2024. /priority important-soon
/triage accepted
It's worth noting that the existing banner is scheduled to run until Feb 1. Considering this, we might want to keep the KubeCon EU 2024 banner active after that date. How about initiating the banner from Feb 16? This would give us approximately a month (5 weeks) before KubeCon kicks off on March 19, 2024.
I want to help with this. /assign
PR is created to help with this request. Please do review whenever you have the time. Thanks in advance!
I'd appreciate 5 weeks too
Change:
Kubernetesは、コンテナ化されたアプリケーションの展開、スケーリング、また管理を自動化するためのオープンソースコンテナプラットフォームです。このオープンソースプロジェクトは、Cloud Native Computing Foundation(<a href="https://www.cncf.io/about">CNCF</a>)によってホストされています。 cards: - name: concepts <del> title: "基本を理解する" </del> <ins> title: "Kubernetesを理解する" </ins> description: "Kubernetesとその基本的なコンセプトを学びます。" button: "コンセプトを学ぶ" button_path: "/docs/concepts"

Discussion:
This is a Feature Request Update Why is this needed Many people view this page. Updating the links on this page is useful for many people. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/assign /language ja /area localization
/triage accepted
Change:
security mechanisms to make sure that users and workloads can get access to the resources they need, while keeping workloads, and the cluster itself, secure. You can set limits on the resources that users and workloads can access <del> by managing [policies](https://kubernetes.io/docs/concepts/policy/) and </del> <ins> by managing [policies](/docs/concepts/policy/) and </ins> [container resources](/docs/concepts/configuration/manage-resources-containers/). Before building a Kubernetes production environment on your own, consider

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
**Notes:** <del> - Please refer to the [kubeadm reference guide](/docs/reference/setup-tools/kubeadm/) if you want to </del> <ins> - Please refer to the [kubeadm reference guide](/docs/reference/setup-tools/kubeadm/kubeadm/) if you want to </ins> read more about the flags `kubeadm init` provides. You can also specify a [configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file) instead of using flags. - You need to choose a Pod Network Plugin in the next step. Depending on what

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x ] Bug Report Problem: Link to kubeadm reference guide broken. In step (2/4) Initializing your master, the link here is broken: "Please refer to the kubeadm reference guide if you want to read ..." Proposed Solution: Page to Update: backed by: docs/setup/independent/create-cluster- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
### Accessing the cluster with a browser <del> We install two UIs on Kubernetes. The original KubeUI and [the newer kube dashboard](/docs/tasks/web-ui-dashboard/). When you create a cluster, the script should output URLs for these interfaces like this: KubeUI is running at ```https://${MASTER_IP}:6443/api/v1/namespaces/kube-system/services/kube-ui/proxy```. </del> <ins> We install [the kubernetes dashboard](/docs/tasks/web-ui-dashboard/). When you create a cluster, the script should output URLs for these interfaces like this: </ins> kubernetes-dashboard is running at ```https://${MASTER_IP}:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy```.

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:
title: "PowerShell auto-completion" description: "Some optional configuration for powershell auto-completion." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- The kubectl completion script for PowerShell can be generated with the command `kubectl completion powershell`.

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:
gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled by default to validate custom resource based on _validation rules_. You can disable this feature by explicitly setting the `CustomResourceValidationExpressions` feature gate to `false`, <del> for the `[kube-apiserver](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/)` component. </del> <ins> for the [kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/) component. </ins> This feature is only available if the schema is a [structural schema](#specifying-a-structural-schema).

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: has a Markdown error. renders like that, but should be a hyperlink: Proposed Solution: Update the Markdown source Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /help /triage accepted
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: has a Markdown error. renders like that, but should be a hyperlink: Update the Markdown source <!--Kubernetes Version:--/language en /help /triage accepted </details
/assign
/assign
Change:
</div> </div> </div> <del> {{ partial "footer.html" . }} </del> </div> <ins> {{ partial "footer.html" . }} </ins> {{ partial "scripts.html" . }} </body> </html>  No newline at end of file

Discussion:
This is a Bug Report Problem: There are whitespaces on both sides of the footer on the blog page. ! Page to Update:
/area web-development
/priority backlog /triage accepted
A little whitespace line across whole page is also present , but maybe in this case it will get resolved by fixing footer.
Change:
--> {{< note >}} 如果你在本地运行 Minikube 环境，你可以使用浏览器来访问 <del> hellow-world.info 和 hello-world.info/v2。 </del> <ins> hello-world.info 和 hello-world.info/v2。 </ins> {{< /note >}} ## {{% heading "whatsnext" %}}

Discussion:
Ingress Ingress Minikube hellow- hellow- typohellow
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:
curl -L https://github.com/cloudflare/cfssl/releases/download/v1.5.0/cfssl-certinfo_1.5.0_linux_amd64 -o cfssl-certinfo chmod +x cfssl-certinfo <del> <!-- 1.  Create a directory to hold the artifacts and initialize cfssl: --> 1.  创建一个目录，用它保存所生成的构件和初始化 cfssl： </del> <ins> <!-- 2.  Create a directory to hold the artifacts and initialize cfssl: --> 2.  创建一个目录，用它保存所生成的构件和初始化 cfssl： </ins> mkdir cert cd cert ../cfssl print-defaults config > config.json ../cfssl print-defaults csr > csr.json <del> <!-- 1.  Create a JSON config file for generating the CA file, for example, `ca-config.json`: --> 1.  创建一个 JSON 配置文件来生成 CA 文件，例如：`ca-config.json`： </del> <ins> <!-- 3.  Create a JSON config file for generating the CA file, for example, `ca-config.json`: --> 3.  创建一个 JSON 配置文件来生成 CA 文件，例如：`ca-config.json`： </ins> { "signing": {

Discussion:
Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.
Change:
--build-arg HUGO_VERSION=$(HUGO_VERSION) container-build: module-check <del> $(CONTAINER_RUN) $(CONTAINER_IMAGE) hugo --minify </del> <ins> $(CONTAINER_RUN) --read-only $(CONTAINER_IMAGE) hugo --minify </ins> container-serve: module-check <del> $(CONTAINER_RUN) --mount type=tmpfs,destination=/src/resources,tmpfs-mode=0777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 </del> <ins> $(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 </ins> test-examples: scripts/test_examples.sh install

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:
## Check required ports These [required ports](/docs/reference/ports-and-protocols/) <del> need to be open in order for Kubernetes components to communicate with each other. You can use `telnet` to check if a port is open. for example: </del> <ins> need to be open in order for Kubernetes components to communicate with each other. You can use telnet to check if a port is open. For example: </ins> ```shell telnet 127.0.0.1 6443

Discussion:
The "Install kubeadm" page has an incorrect capitalization in the "" section. Should be /language en /kind cleanup /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 : The "Install kubeadm" page has an incorrect capitalization in the "" section. You can use telnet to check if a port is open. For example: /kind cleanup /good-first-issue </details
/triage accepted
/remove-kind bug
Hey, could you please assign me ?
/assign
Change:
title: 容器环境变量 id: container-env-variables date: 2018-04-12 <del> full_link: /docs/concepts/containers/container-environment-variables.md </del> <ins> full_link: /zh/docs/concepts/containers/container-environment/ </ins> short_description: > 容器环境变量提供了运行容器化应用所必须的一些重要信息。

Discussion:
could you please be more specific? I cannot find the broken link...
if you enter [], you can see next describtion: Pod PodPreset Secret Pod . and you click ‘’ the link is broken
thank you, I'm fixing it now ~
/assign
/language zh
Change:
Um eine bestimmte Version herunterzuladen, ersetzen Sie den Befehlsteil `$(curl -LS https://dl.k8s.io/release/stable.txt)` mit der jeweiligen Version. <del> Um beispielsweise die Version {{< param "fullversion" >}} auf Linux herunterzuladen, verwenden Sie den folgenden Befehl: </del> <ins> Um beispielsweise die Version {{< skew currentPatchVersion >}} auf Linux herunterzuladen, verwenden Sie den folgenden Befehl: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` 2. Machen Sie die kubectl-Binärdatei ausführbar.

Discussion:
[de] Replace deprecated shortcode Problem: Based on , I have created this issue/task to help update the [de] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 42: Um zum Beispiel Version {{< param "fullversion" }} auf Linux herunterzuladen: 45: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install-kubectl- 47: Um zum Beispiel Version {{< param "fullversion" }} auf Intel macOS herunterzuladen: 50: curl -LO "{{< param "fullversion" }}/bin/darwin/amd64/kubectl" 56: curl -LO "{{< param "fullversion" }}/bin/darwin/arm64/kubectl" /home/rdlugyhe/kubernetes/k8s-website/content/de/docs/tasks/tools/install- 200: Um beispielsweise die Version {{< param "fullversion" }} auf macOS herunterzuladen, verwenden Sie 203: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 228: Um beispielsweise die Version {{< param "fullversion" }} auf Linux herunterzuladen, verwenden Sie 231: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 247: Laden Sie das aktuellste Release {{< param "fullversion" }} von diesem linkg
Change:
2. Create a Service to expose MongoDB on the network: ```shell <del> kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-service.yaml </ins> ``` The output of a successful command verifies that the Service was created:

Discussion:
In the section of There is no file with the specified URL, and the output of running this command is:
In PR the is deleted, which is used in the 'Creating MongoDB deployment and service' page. /kind bug
/triage accepted /retitle Example missing from Use Port Forwarding to Access Applications in a Cluster
/assign will add these yaml's
Fix it here