jiebi/CodeConvo huggingface dataset:
Code 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: Using chrome (120.0.6099.129 (Official Build) (x86_64)) on macOS (12.7.1 (21G920)) and hitting the link from the , I hit the documentation for Kubernetes 1.29 and I can only see the navigation with the list of objects. <img width="1595" alt="image" src=""I have observed the same problem on safari ( 17.1.2 (.2.9.11.12, )): <img width="1587" alt="image" src=""And Firefox (121.0 (64-bit)): <img width="1266" alt="image" src=""Proposed Solution: Get the content back as in the : <img width="1585" alt="image" src=""Page to Update:
/retitle One-page API reference missing for Kubernetes v1.29
The API reference for v1.29 was successfully generated in PR , as evidenced by the verified information in the . It appears that we're encountering a rendering glitch.
Upon further investigation, it seems that the page data isn't rendering correctly in dark mode (sort of). I switched my device/browser theme to light mode, and the page info became visible (Refer below screenshot). It seems like there might be some missing CSS and scripts causing this issue. <img width="1278" alt="api-refence-light-mode" src=""
This is definitely something we should address. (cc: /triage accepted
/retitle Content of 'One-page API Reference for v1.29' not rendering properly in dark mode
/assign
The original description of the issue is proper and correct, I don't know why you are so akin to change these issue descriptions. I'm raising this question because when an issue title is changed, my email client won't treat the issues as the same one. The "conversation" mode no longer works. I'm receiving emails for every comment as a separate email. It is not a big deal but it is really annoying.
Ah, does the API reference have special support for dark mode, separate from Assuming that this is the case: /kind bug /area web-development A short-term fix would be to drop the dark mode support, pending an implementation that works right. Let's see if sorts it out.
For what it's worth, I agree with the title change in The bug was about dark mode rendering and not that the reference was completely missing.

Related discussion:
text: display: block; height: 100%; position: fixed; <del> width: 100%; z-index: 1; </del> top: 0; left: 0; background-color: rgba(51, 113, 227, 3%); border-right: 1px solid #dee2e6; <del> overflow-x: hidden; </del> <ins> overflow-x: scroll; </ins> padding-top: .5rem; }
Code change:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign
/unassign

Related discussion:
text: <ins> apiVersion: apps/v1 kind: Deployment metadata: name: patch-demo spec: replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: patch-demo-ctr image: nginx tolerations: - effect: NoSchedule key: dedicated value: test-team </ins>
Code change:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign
/unassign

Related discussion:
text: <ins> apiVersion: apps/v1 kind: Deployment metadata: name: retainkeys-demo spec: selector: matchLabels: app: nginx strategy: rollingUpdate: maxSurge: 30% template: metadata: labels: app: nginx spec: containers: - name: retainkeys-demo-ctr image: nginx </ins>
Code change:
apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
Use kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
provide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information
Page related to the issue :
/language zh
/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm
/triage accepted /assign

Related discussion:
text: # Replace the value of "containerRuntimeEndpoint" for a different container runtime if needed. ``` --> ```sh cat << EOF > /etc/systemd/system/kubelet.service.d/kubelet.conf # 将下面的 "systemd" 替换为你的容器运行时所使用的 cgroup 驱动。
Code change:
apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
Use kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
provide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information
Page related to the issue :
/language zh
/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm
/triage accepted /assign

Related discussion:
text: # Create temp directories to store files that will end up on other hosts mkdir -p /tmp/${HOST0}/ /tmp/${HOST1}/ /tmp/${HOST2}/ --> ```sh # 使用你的主机 IP 更新 HOST0、HOST1 和 HOST2 的 IP 地址 export HOST0=10.0.0.6
Code change:
The following links for Weave Net are no longer viable, and should either be updated (e.g. pointing to the GitHub repo where it is now maintained, , which again, admittedly needs to be updated, but puts the onus on the project itself), or the page should be completely removed: Google link-to-highlight: ,by%20the%20policies. This issue resembles
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
Submitted PR with fix for review and merge. Can also remove page and associated links if this is regarded as a type of technical debt.
Page mentioned in the issue: /language en /kind bug

Related discussion:
text: ## Install the Weave Net addon <del> Follow the [Integrating Kubernetes via the Addon](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/) guide. </del> <ins> Follow the [Integrating Kubernetes via the Addon](https://github.com/weaveworks/weave/blob/master/site/kubernetes/kube-addon.md#-installation) guide. </ins> The Weave Net addon for Kubernetes comes with a <del> [Network Policy Controller](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#npc) </del> <ins> [Network Policy Controller](https://github.com/weaveworks/weave/blob/master/site/kubernetes/kube-addon.md#network-policy) </ins> that automatically monitors Kubernetes for any NetworkPolicy annotations on all namespaces and configures `iptables` rules to allow or block traffic as directed by the policies.
Code change:
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 Document (and register) the legacy annotation The page to change is: Why is this needed We try to document all of our annotations, even the ones we ask people to stop using. Comments /language en /lifecycle frozen /sig network cloud-provider
Could be useful, let's consider doing this. /triage accepted /priority backlog
I'd like to work on it /assign I'll share the findings here so the content is confirmed first.
How's this :
I got reference from cloud-provider-azure and Microsoft docs.
From it looks like we need a pile of other issues about unregistered annotations for this cloud provider.
Yes, you can find the other annotations here: https://cloud-provider-

Related discussion:
text: details. {{< /caution >}} <ins> ### service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset (deprecated) {#service-beta-kubernetes-azure-load-balancer-disble-tcp-reset} Example: `service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset: "false"` Used on: Service This annotation only works for Azure standard load balancer backed service. This annotation is used on the Service to specify whether the load balancer should disable or enable TCP reset on idle timeout. If enabled, it helps applications to behave more predictably, to detect the termination of a connection, remove expired connections and initiate new connections. You can set the value to be either true or false. See [Load Balancer TCP Reset](https://learn.microsoft.com/en-gb/azure/load-balancer/load-balancer-tcp-reset) for more information. {{< note >}} This annotation is deprecated. {{< /note >}} </ins> ### pod-security.kubernetes.io/enforce Type: Label
Code change:
FEATURE STATE for feature says According to page it is still alpha, being first introduced in 1.22. Should not the FEATURE STATE line then say ?
Page related to issue: /language en
/retitle Empty feature state tag for "Memory QoS with cgroup v2" in "Pod Quality of Service Classes" page /kind bug
We should fix so that the correct feature state is reflected. /priority backlog /triage accepted
It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /help
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 : It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /help 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
I will want help with this. /assign

Related discussion:
text: ## Memory QoS with cgroup v2 <del> {{< feature-state feature-gate-name="MemoryQoS" >}} </del> <ins> {{< feature-state feature_gate_name="MemoryQoS" >}} </ins> Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes. Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`
Code change:
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. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted

Related discussion:
text: ### はじめに Bashにおけるkubectlの補完スクリプトは`kubectl completion bash`コマンドで生成できます。 <del> シェル内で補完スクリプトをsourceすることでkubectlの自動補完が有効になります。 </del> <ins> 補完スクリプトをシェル内に読み込ませることでkubectlの自動補完が有効になります。 </ins> ただし、補完スクリプトは[**bash-completion**](https://github.com/scop/bash-completion)に依存しているため、事前にインストールしておく必要があります。
Code change:
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. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted

Related discussion:
text: ### kubectlの自動補完を有効にする <del> すべてのシェルセッションにてkubectlの補完スクリプトをsourceできるようにしなければなりません。 </del> <ins> 次に、kubectl補完スクリプトがすべてのシェルセッションで読み込まれるように設定する必要があります。 </ins> これを行うには複数の方法があります: <del> - 補完スクリプトを`~/.bash_profile`内でsourceする: </del> <ins> - 補完スクリプトを`~/.bash_profile`内で読み込ませる: </ins> ```bash echo 'source <(kubectl completion bash)' >>~/.bash_profile
Code change:
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. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted

Related discussion:
text: この場合、なにも操作する必要はありません。 {{< note >}} <del> Homebrewでインストールしたbash-completion v2は`BASH_COMPLETION_COMPAT_DIR`ディレクトリ内のすべてのファイルをsourceするため、後者の2つの方法が機能します。 </del> <ins> Homebrewでインストールしたbash-completion v2は`BASH_COMPLETION_COMPAT_DIR`ディレクトリ内のすべてのファイルを読み込むため、後者の2つの方法が機能します。 </ins> {{< /note >}} どの場合でも、シェルをリロードしたあとに、kubectlの自動補完が機能するはずです。
Code change:
This is a Bug Report The link provided for [Node Lease objects] is wrong <!--Required Information--Problem: The provided link is navigating to top of the page not to corresponding sub section. Proposed Solution: URL link should be 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

Related discussion:
text: the `spec.renewTime` field for the Lease. The Kubernetes control plane uses the time stamp of this field to determine the availability of this `Node`. <del> See [Node Lease objects](/docs/concepts/architecture/nodes/#heartbeats) for more details. </del> <ins> See [Node Lease objects](/docs/concepts/architecture/nodes/#node-heartbeats) for more details. </ins> ## Leader election
Code change:
This is a Bug Report The glossary tooltip for is referencing section, instead it should reference to page.
/sig docs /language en
/assign
fixed
/retitle Incorrect glossary tooltip link for 'Container runtime interface' /priority backlog /triage accepted

Related discussion:
text: [cAdvisor](https://github.com/google/cadvisor) that runs within the kubelet. If you enable the `PodAndContainerStatsFromCRI` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in your cluster, and you use a container runtime that supports statistics access via <del> {{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI), then </del> <ins> {{< glossary_tooltip term_id="container-runtime-interface" text="Container Runtime Interface">}} (CRI), then </ins> the kubelet [fetches Pod- and container-level metric data using CRI](/docs/reference/instrumentation/cri-pod-container-metrics), and not via cAdvisor. ## {{% heading "whatsnext" %}}
Code change:
Hi, In k8s v1.30 documentation page , in the top FEATURE STATE line, the indicated Kubernetes version where this feature reached "stable/GA" is said to be 1.30; if you check which it is in k8s v1.29 doc page: it says 1.29 .... for 1.28 doc it says GA/stable was reached in 1.28 ... and so for the previous releases ... It looks there is a wrong moving version for this, pointing to the current one "owning" the doc page. According to it should say: FEATURE STATE: Kubernetes v1.14 [stable]
Page reported in issue: /language en /kind bug
We should correct this discrepancy in the feature state. /priority backlog /triage accepted
I try to help with this. /assign

Related discussion:
text: --- <!-- overview --> <del> {{< feature-state state="stable" >}} </del> <ins> {{< feature-state feature_gate_name="HugePages" >}} </ins> Kubernetes supports the allocation and consumption of pre-allocated huge pages by applications in a Pod. This page describes how users can consume huge pages.
Code change:
Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /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 : Note that this issue is for Japanese Speaker Original: /language ja /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
/triage accepted
/assign
san, can you please review the PR

Related discussion:
text: <ins> --- title: フィーチャーゲート(Feature gate) id: feature-gate date: 2023-01-12 full_link: /ja/docs/reference/command-line-tools-reference/feature-gates/ short_description: > 特定のKubernetes機能を有効にするかどうかを制御する方法。 aka: tags: - fundamental - operation --- フィーチャーゲートはクラスター内でどのKubernetes機能を有効にするかを制御するために使用できるキー(不透明な文字列値)のセットです。 <!--more--> 各Kubernetesコンポーネントで`--feature-gates`コマンドラインフラグを使用して、これらの機能をオンまたはオフにすることができます。 各Kubernetesコンポーネントでは、そのコンポーネントに関連する一連のフィーチャーゲートを有効または無効にすることができます。 Kubernetesのドキュメントには、現在のすべての[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)とその制御対象がリストされています。 </ins>
Code 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 annotation is unregistered, but used in Kubernetes code. The says: However, we don't have a mechanism to register annotations that are not also documented. So, it needs registering. Proposed Solution: Register the annotation, by mentioning it in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node Required for
/assign
/priority backlog /triage accepted
/lifecycle frozen
/assign
/unassign Unassigning my self as PR is already raised by PR raised for this issue

Related discussion:
text: Note the [PodIndexLabel](/docs/reference/command-line-tools-reference/feature-gates/) feature gate must be enabled for this label to be added to pods. <ins> ### resource.kubernetes.io/pod-claim-name Type: Annotation Example: `resource.kubernetes.io/pod-claim-name: "my-pod-claim"` Used on: ResourceClaim This annotation is assigned to generated ResourceClaims. Its value corresponds to the name of the resource claim in the `.spec` of any Pod(s) for which the ResourceClaim was created. This annotation is an internal implementation detail of [dynamic resource allocation](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/). You should not need to read or modify the value of this annotation. </ins> ### cluster-autoscaler.kubernetes.io/safe-to-evict Type: Annotation
Code change:
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. --In the document , it would be helpful to link to the . Why is this needed I was studying for the CKA exam, and was practicing only using the pages to search for info about CertificateSigningRequests. The doc came up readily, but the was not so easily discoverable via a search using only the search interface. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted

Related discussion:
text: {{< feature-state for_k8s_version="v1.19" state="stable" >}} <del> A CertificateSigningRequest (CSR) resource is used to request that a certificate be signed </del> <ins> A [CertificateSigningRequest](/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/) (CSR) resource is used to request that a certificate be signed </ins> by a denoted signer, after which the request may be approved or denied before finally being signed.
Code change:
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. --In the document , it would be helpful to link to the . Why is this needed I was studying for the CKA exam, and was practicing only using the pages to search for info about CertificateSigningRequests. The doc came up readily, but the was not so easily discoverable via a search using only the search interface. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted

Related discussion:
text: ### Create a CertificateSigningRequest {#create-certificatessigningrequest} <del> Create a CertificateSigningRequest and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the CertificateSigningRequest. </del> <ins> Create a [CertificateSigningRequest](/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/) and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the CertificateSigningRequest. </ins> ```shell cat <<EOF | kubectl apply -f -