jiebi/CodeConvo huggingface dataset:
Change:
This example turned off client-side validation to demonstrate the API server's behavior, by adding the `--validate=false` command line option. <del> Because the [OpenAPI validation schemas are also published](#publish-validation-schema-in-openapi-v2) </del> <ins> Because the [OpenAPI validation schemas are also published](#publish-validation-schema-in-openapi) </ins> to clients, `kubectl` also checks for unknown fields and rejects those objects well before they would be sent to the API server.

Discussion:
This is a Bug Report Problem: The hyperlinks for OpenAPI validation schemas are also published and Validation Schema Publishing under the task page is not working. They both redirect to which is incorrect, the correct one is Proposed Solution: OpenAPI validation schemas are also published and Validation Schema Publishing should redirect to instead of 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
/assign
/sig api-machinery /language en /sig docs
Fixed the issue here:
Change:
- `KubeletPodResourcesGetAllocatable`: Enable the kubelet's pod resources `GetAllocatableResources` functionality. This API augments the [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) <del> - `KubeletPodResourcesDynamiceResources`: Extend the kubelet's pod resources gRPC endpoint to </del> <ins> - `KubeletPodResourcesDynamicResources`: Extend the kubelet's pod resources gRPC endpoint to </ins> to include resources allocated in `ResourceClaims` via `DynamicResourceAllocation` API. See [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) for more details. with informations about the allocatable resources, enabling clients to properly

Discussion:
The "KubeletPodResourcesDynamiceResources" feature gate is not in the feature gates tables ( or ), it's only on the . I think it should be to .
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
is a typo, notice the extra before the last word. PRs welcome.
I have raised PR to fix the typo
I should have mentioned the page where I saw the typo — there are still two typos there.
These typos should be fixed now after merge of PR
Change:
## Running the website locally using Hugo <del> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </del> To install dependencies, deploy and test the site locally, run: - For macOS and Linux

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: I tried to run the cloned website, which I forked on my Ubuntu Machine, but am getting error. I tried both running via docker and my running locally using Hugo but getting some issues in both. Following is the error while running via docker ! and this is while running locally via Hugo ! I also initialized modules by running the command: make module-init
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
/kind support
I tried to analyze a bit. On first investigation, it seems like a valid issue. However, I do not know the root cause. I created a new Ubuntu VM, and tried to setup k/w from scratch. On running , the hugo command was stuck at: I then executed and managed to reproduce the issue you reported. (Note that at times this command gets stuck without an output as well). On my local machine, I have older versions of npm, hugo, go and docker and k/w builds fine. It could be related to one of the upgrades in the dependencies (most probably Hugo), however I cannot state for certain.
The issue is in the Hugo version. Upon changing the version, it worked perfectly. Thanks for your input. I think this issue should be raised.
Can you please mention the exact combination of versions (npm, Hugo, go, docker) that worked for you?
here, it is but I think the issue is with Hugo's version only.
Try whilst you have the latest main branch checked out. That works for me. You should find that you're using Hugo 0.121.2 (see ). If you want to test a Hugo upgrade, run before .
The instruction to install a specific Hugo extended version as defined in is mentioned in the section. However, I believe it would be helpful to move the instruction to the section.

This would prevent readers from inadvertently installing the latest Hugo extended version (currently v0.124.1) which is incompatible with k/w. I'll try to work on a PR for this.
/assign
Change:
[options_heading] other = "选项" <ins> [post_create_child_page] other = "创建子页面" </ins> [prerequisites_heading] other = "准备开始"

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: Submodule need to updatecurrent version lack of i18n translation for Upgrade of can solve this problem, see it in ! <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /triage accepted /priority backlog /good-first-issue This issue is a good first issue because the single step needed to fix it is to update the version of the submodule.  has some contextual information; the command to use is .
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 : /kind bug /triage accepted /priority backlog /good-first-issue  has some contextual information; the command to use is . 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
:information_source: Note that PR is already open to address this.
/remove-label "help wanted"
Change:
`ControllerPublishVolume` and `ControllerUnpublishVolume` calls. This field is optional, and may be empty if no secret is required. If the Secret contains more than one secret, all secrets are passed. <del> `nodeExpandSecretRef`: A reference to the secret containing sensitive </del> <ins> * `nodeExpandSecretRef`: A reference to the secret containing sensitive </ins> information to pass to the CSI driver to complete the CSI `NodeExpandVolume` call. This field is optional, and may be empty if no secret is required. If the object contains more than one secret, all

Discussion:
Declared "CSIMigration" feature gate only exists in . According to "CSIMigration" could be a switchable feature gate, but it looks like it is always on and cannot be switched off, so it it's strange that it's mentioned in the v1.27 documentation. All of this is probably more or less OK, as it's suitable for earlier versions of Kubernetes especially since there are deprecation warnings. But it’s also unclear for which components this feature gate is intended. According to it's intended for . <brIt is not clear for which components "CSIMigrationAzureFile" feature gate is intended. <brIt is not clear which controller manager is meant — cloud controller manager or kube-controller-manager. According to it's intended for . It is not clear for which components "CSIMigrationRBD" feature gate is intended: <brIt is not clear for which components "SizeMemoryBackedVolumes" feature gate is intended. <brThe description of "nodeExpandSecretRef" field does not start with a new line in the list. <brThe double word "node".
/language en
/assign RakshitKumar04
Let's stop mentioning in You can specify feature gates for all Kubernetes components (some might be no-ops). We could document that, but it'd be better to track that change as a separate issue. Let's remove the double use of node Let's fix the formatting for these are useful things to point out. Thank you! If you find more, you can help further by opening one issue per thing that will need fixing.
/triage accepted
If you prefer to track this as separate issue, whether I should do something extra or not?
If you're willing to file a separate issue about that clarification please do.
I created separate issue , so this issue should be closed after solving everything except point 2.
Hey, should I raise a PR That fixes the following typos here? The description of "nodeExpandSecretRef" field does not start with a new line in the list. The double word "node". For Linux worker nodes, containerized CSI node node plugins are typically deployed as privileged containers.
If it leads to a documentation fix, sure. Sorry, but I don't know enough about the workflow adopted here. I just feel it is my duty to help make the documentation better and I do my best.
Hey, Should I raise a PR correcting the documentation?
Change:
apiVersion: rbac.authorization.k8s.io/v1 metadata: name: system:kube-dns-autoscaler <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> subjects: - kind: ServiceAccount name: kube-dns-autoscaler

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: mentions an annotation prefix that is deprecated / not actually official. Proposed Solution: Remove all mention of annotations from that page. Page to Update: and specifically Additional Information: This is a follow-up to /language en
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 Remove labels from ”Autoscale the DNS Service in a Cluster”
/assign
Change:
* See [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core). * See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).

Discussion:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /assign
Change:
### Container image lifecycle Kubernetes manages the lifecycle of all images through its *image manager*, <del> which is part of the kubelet, with the cooperation of cadvisor. The kubelet </del> <ins> which is part of the kubelet, with the cooperation of {{< glossary_tooltip text="cadvisor" term_id="cadvisor" >}}. The kubelet </ins> considers the following disk usage limits when making garbage collection decisions:

Discussion:
Kubernetes manages the lifecycle of all images through its image manager, which is part of the kubelet, with the cooperation of cadvisor. Needs pop up note on cadvisor
/kind feature /language en I think by pop up note, you're talking about a . Good suggestion, thanks! To fix this, someone should: add a new glossary entry read for context look in copy an existing item to use as a template (make sure to change everything that needs changing) add a glossary tooltip for cadvisor to /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 : /kind feature /language en add a new glossary entry /triage accepted 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
/priority backlog
Change:
date: 2018-04-12 full_link: /docs/concepts/overview/working-with-objects/labels/ short_description: > <del> ユーザーはラベルに基づいてリソースのリストをフィルタリングできます。 </del> <ins> セレクターを利用すると、ユーザーはラベルに基づいてリソースのリストをフィルタリングできます。 </ins> aka: tags: - fundamental --- <del> ユーザーは{{< glossary_tooltip text="ラベル" term_id="label" >}}に基づいてリソースのリストをフィルタリングできます。 </del> <ins> セレクターを利用すると、ユーザーは{{< glossary_tooltip text="ラベル" term_id="label" >}}に基づいてリソースのリストをフィルタリングできます。 </ins> <!--more-->

Discussion:
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
Change:
### Installer le binaire kubectl avec curl sur Windows <del> 1. Téléchargez la dernière version {{< param "fullversion" >}} depuis [ce lien](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Téléchargez la dernière version {{< skew currentPatchVersion >}} depuis [ce lien](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe). </ins> Ou si vous avez `curl` installé, utilisez cette commande: ``` <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> ``` Pour connaître la dernière version stable (par exemple, en scripting), jetez un coup d'oeil à [https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt).

Discussion:
This is a Bug Report Problem: The param is deprecated. Proposed Solution: Replace the shortcode (French pages), for example with when possible and append when needed. Part of /language fr /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
<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> - name: KubeCon 2024 China startTime: 2024-07-26T00:00:00  #Added in https://github.com/kubernetes/website/pull/46431 endTime: 2024-08-23T18:00:00 style: >- background: linear-gradient(90deg, rgba(229,64,216,1) 60%, rgba(0,212,255,1) 100%); color: #fffff; title: | <img src ="/images/announcements/kubecon-china-2024-white.svg" style="float: right; height: 100px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/">KubeCon + CloudNativeCon + Open Source Summit China 2024</a> message: | Join us for three days of incredible opportunities to collaborate, learn and share with the cloud native community.<br/> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/register/?utm_source=kubernetes&utm_medium=all&utm_campaign=kubeconcn24&utm_content=slim-banner"> Buy your ticket now! 21 - 23 August | Hong Kong </a> </ins>

Discussion:
This is a Feature Request What would you like to be Set a banner to announce KubeCon 2024 China Why is this needed We usually turn on a banner for the upcoming KubeCon about 4 weeks ahead of the event. for EU and NA, we did several times for 4 or 5 weeks. the first time for KubeCon China is the 2021 virtual KubeCon China, we have the banner for 2 weeks. 2-4 weeks are OK for me. Logos are not available yet: Also see the config from a previous year's KubeCon(KubeCon China 2021 for 2 weeks). Comments This change will need approval. I would like to set the banner to start on the July 26th, 2024 and to end on the August 23, 2024 at 1800 CST (UTC+8).
/committee steering /triage accepted
I can help with this. I helped with last Kubecon EU banner too. /assign
Ping , if you are busy, I would like to take this job :)
PR to add banner as requested (Sorry for the delay! I was waiting for the logo to be available)
Change:
{{< /caution >}} 1.  Apply the CNI plugin of your choice: <del> [Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network) to install the CNI provider. Make sure the configuration corresponds to the Pod CIDR specified in the kubeadm configuration file if applicable. </del> <ins> [Follow these instructions](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#pod-network) to install the CNI provider. Make sure the configuration corresponds to the Pod CIDR specified in the kubeadm configuration file if applicable. </ins> In this example we are using Weave Net:

Discussion:
This is a Bug Report Formatting is off (broken HTML rendering) on page since earlier this week (Wednesday sometime?) per my comment in - I'm adding as a separate ticket for tracking. Some fixes to Hugo were made in and but the issues on this page are persisting. Problem: Seeing poor formatting and plaintext HTML due to some incorrect syntax on the page: ! - screenshot taken in FireFox, but replicated in Chromium (Brave) as well. Page to Update: Thank you! [EDIT] heh - I switched GitHub accounts - the comments I was referring to were by my other account
thanks for the report. cc possibly caused by the hugo bump too? /sig docs cluster-lifecycle /kind bug
Relates to tracking issue
This is almost fixed. There are some leftovers related to the ordered list. /assign
Change:
path: /docs/getting-started-guides/ovirt/ - title: OpenStack Heat path: /docs/getting-started-guides/openstack-heat/ <del> - title: CoreOS on Multinode Cluster path: /docs/getting-started-guides/coreos/coreos_multinode_cluster/ </del> - title: rkt section: - title: Running Kubernetes with rkt

Discussion:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:
Change:
There are several different proxies you may encounter when using Kubernetes: <del> 1. The [kubectl proxy](#directly-accessing-the-rest-api): </del> <ins> 1. The [kubectl proxy](/docs/tasks/access-application-cluster/access-cluster/#directly-accessing-the-rest-api): </ins> - runs on a user's desktop or in a pod - proxies from a localhost address to the Kubernetes apiserver - client to proxy uses HTTP - proxy to apiserver uses HTTPS - locates apiserver - adds authentication headers <del> 1. The [apiserver proxy](#discovering-builtin-services): </del> <ins> 1. The [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster/#discovering-builtin-services): </ins> - is a bastion built into the apiserver - connects a user outside of the cluster to cluster IPs which otherwise might not be reachable - runs in the apiserver processes

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: The bullet points nested under numbered list aren't rendered as bulleted list: <img width="869" alt="screen shot 2017-06-10 at 2 15 49 pm" src="https://user-"Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
The sub-link isn't correct either. For example, kubectl proxy links to but should instead link to I guess it's because is split from () /assign
Change:
<div class="row"> <div class="col-md-9"> <h2>Kubernetes Basics</h2> <del> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its containerized applications for yourself.</p> </del> <ins> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its <a href="/docs/concepts/overview/what-is-kubernetes/#why-containers">containerized applications</a> for yourself.</p> </ins> <p>Using the interactive tutorials, you can learn to:</p> <ul> <li>Deploy a containerized application on a cluster</li>

Discussion:
This is a... [ x] Feature Request Problem: I am missing a definition of "containerized applications". Proposed Solution: It would be nice if this term ("containerized applications") would be a hyperlink to a place where I can find more details about what this term means in the context of kubernetes. Page to Update: