jiebi/CodeConvo huggingface dataset:
Change:
The supported formats for the name segment of the URL are: * `<service_name>` - proxies to the default or unnamed port using http <del> * `<service_name>:<port_name>` - proxies to the specified port using http </del> <ins> * `<service_name>:<port_name>` - proxies to the specified port name or port number using http </ins> * `https:<service_name>:` - proxies to the default or unnamed port using https (note the trailing colon) <del> * `https:<service_name>:<port_name>` - proxies to the specified port using https </del> <ins> * `https:<service_name>:<port_name>` - proxies to the specified port name or port number using https </ins> ##### Examples

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. --The is lacking clarity that both the port name or port number can be used when proxying to a service. The documentation should mention the field represented by can either be the name of a port in a service or the port number of a service for both forms and . Why is this needed The apiserver proxy endpoint supports using either a to locate the service to proxy to. The alternative form of using the port number could be useful if migrating from an unnamed/default service port to a named service port. Example: The following api server request could be used to proxy either form of the following service object since it references the port number, . If the query was constructed as , only the unnamed port would return a result. Conversely, if was used in the query only the named port would return a result. default/unnamed: named: Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/kind cleanup
/triage accepted
/priority backlog
Change:
replicas | 레플리카 | ReplicationController | 레플리케이션컨트롤러(ReplicationController) | API 오브젝트인 경우 repository | 리포지터리 | <ins> request | 요청(request) | 리소스의 개수나 용량에 대한 요청 수치를 표현하기 위해 사용된 경우 선택적으로 사용 (API 오브젝트 속성으로 request를 사용한 경우는 가능한 영문을 유지) </ins> resource | 리소스 | <del> Resource Limit | 리소스 상한 | </del> ResourceQuota | 리소스쿼터(ResourceQuota) | API 오브젝트인 경우 return | 반환하다 | revision | 리비전 |

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: / . '' '' . English | -- | -- Default Limit | Default Request | max limit/request ratio | / Resource Limit | Proposed Solution: / '' '' , . LimitRange API yaml English -- -- Default Limit Default Request max limit/request ratio Resource Limit limit ResourceQuota, LimitRange request ResourceQuota, LimitRange Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
. before : LimitRange after : ResourceQuota, LimitRange LimitRange ResourceQuota .
Change:
### Menginstal program kubectl dengan curl pada Windows <del> 1. Unduh versi terbarunya {{< param "fullversion" >}} dari [tautan ini](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Unduh versi terbarunya {{< skew currentPatchVersion >}} dari [tautan ini](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe). </ins> Atau jika sudah ada `curl` pada mesin kamu, jalankan perintah ini: ``` <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> ``` Untuk mendapatkan versi stabil terakhir (misalnya untuk _scripting_), lihat di [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 [id] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/id" /home/rdlugyhe/kubernetes/k8s-website/content/id/docs/tasks/tools/install- 34: Misalnya, untuk mengunduh versi {{< param "fullversion" }} di Linux, ketik: 37: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 114: Misalnya, untuk mengunduh versi {{< param "fullversion" }} pada macOS, ketik: 117: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 179: 1. Unduh versi terbarunya {{< param "fullversion" }} dari tautan ini /sig docs /sig localization /language id cc:
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: Page to Update: /home/rdlugyhe/kubernetes/k8s-website/content/id/docs/concepts/extend-kubernetes/compute-storage-net/network- /sig localization /language id cc: 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 /area localization /priority backlog
Change:
<del> --- --- This document summarizes known issues with existing Kubernetes releases. Please consult this document before filing new bugs. ### Release 1.0.1 * `exec` liveness/readiness probes leak resources due to Docker exec leaking resources (#10659) * `docker load` sometimes hangs which causes the `kube-apiserver` not to start.  Restarting the Docker daemon should fix the issue (#10868) * The kubelet on the master node doesn't register with the `kube-apiserver` so statistics aren't collected for master daemons (#10891) * Heapster and InfluxDB both leak memory (#10653) * Wrong node cpu/memory limit metrics from Heapster (https://github.com/GoogleCloudPlatform/heapster/issues/399) * Services that set `type=LoadBalancer` can not use port `10250` because of Google Compute Engine firewall limitations * Add-on services can not be created or deleted via `kubectl` or the Kubernetes API (#11435) * If a pod with a GCE PD is created and deleted in rapid succession, it may fail to attach/mount correctly leaving PD data inaccessible (or corrupted in the worst case). (http://issue.k8s.io/11231#issuecomment-122049113) * Suggested temporary work around: introduce a 1-2 minute delay between deleting and recreating a pod with a PD on the same node. * Explicit errors while detaching GCE PD could prevent PD from ever being detached (#11321) * GCE PDs may sometimes fail to attach (#11302) * If multiple Pods use the same RBD volume in read-write mode, it is possible data on the RBD volume could get corrupted. This problem has been found in environments where both apiserver and etcd rebooted and Pods were redistributed. * A workaround is to ensure there is no other Ceph client using the RBD volume before mapping RBD image in read-write mode. For example, `rados -p poolname listwatchers image_name.rbd` can list RBD clients that are mapping the image. </del>

Discussion:
This page is woefully out of date: docs/user-guide/known-issues/ We should move the content to the 1.0 release notes and delete the page. cc
already contains this info. I'll delete the file.
cc I can't see how to delete a file using this new edit-in-place interface. Maybe it's a permission issue?
These items are all in flight - But I have no power to assign or merge anything.
Nice work, David. :)
Change:
```shell kubectl get csr <ins> ``` ```console </ins> NAME        AGE     SIGNERNAME                        REQUESTOR                      CONDITION csr-9wvgt   112s    kubernetes.io/kubelet-serving     system:node:worker-1           Pending csr-lz97v   1m58s   kubernetes.io/kubelet-serving     system:node:control-plane-1    Pending

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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
- `CustomResourceWebhookConversion`: Enable webhook-based conversion on resources created from [CustomResourceDefinition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/). troubleshoot a running Pod. <del> - `DisableAcceleratorUsageMetrics`: [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/monitoring.md). </del> <ins> - `DisableAcceleratorUsageMetrics`: [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/system-metrics/). </ins> - `DevicePlugins`: Enable the [device-plugins](/docs/concepts/cluster-administration/device-plugins/) based resource provisioning on nodes. - `DefaultPodTopologySpread`: Enables the use of `PodTopologySpread` scheduling plugin to do

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: Line 426: broken link - : [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-). Line 477: duplicated - : When  is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. Proposed Solution: Line 426: - : [Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/system-metrics/). Line 477: - : When  is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
Cuidado. {{< /warning >}} <del> ### Ambiente de teste embutido do Katacoda Este botão permite aos usuários executar o Minikube dentro dos seus navegadores utilizando o terminal do Katacoda. Ele diminui a barreira de entrada permitindo que as pessoas utilizem o Minikube com um único clique ao invés de precisar fazer todo o processo de instalação e configuração das ferramentas Minikube e Kubectl na máquina local. O ambiente de teste embutido está configurado para executar `minikube start` e permite aos usuários completar tutoriais na mesma janela que a documentação. {{< caution >}} Esta sessão é limitada a 15 minutos. {{< /caution >}} Por exemplo: ``` {{</* kat-button */>}} ``` The output is: {{< kat-button >}} </del> ## Problemas comuns com _shortcodes_ {#common-shortcode-issues} ### Listas ordenadas

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
<!-- body --> ## Control Plane Components <del> The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). </del> <ins> The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a Deployment's `{{< glossary_tooltip text="replicas" term_id="replica" >}}` field is unsatisfied). </ins> Control plane components can be run on any machine in the cluster. However, for simplicity, set up scripts typically start all control plane components on

Discussion:
Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign
Change:
<!-- Now modify your nginx replicas to start an https server using the certificate in the secret, and the Service, to expose both ports (80 and 443): --> <del> 现在修改 Nginx 副本，启动一个使用在秘钥中的证书的 https 服务器和 Servcie，都暴露端口（80 和 443）： </del> <ins> 现在修改 nginx 副本，启动一个使用在秘钥中的证书的 HTTPS 服务器和 Servcie，暴露端口（80 和 443）： </ins> {{< codenew file="service/networking/nginx-secure-app.yaml" >}}

Discussion:
Nginx https 404
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
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
<ins> apiVersion: v1 kind: Service metadata: name: mongo labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: ports: - port: 27017 targetPort: 27017 selector: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend </ins>

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
Change:
You can modify Node objects regardless of the setting of `--register-node`. For example, you can set labels on an existing Node, or mark it unschedulable. --> <del> #### 手动节点管理 </del> <ins> ### 手动节点管理 </ins> 你可以使用 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 来创建和修改 Node 对象。

Discussion:
The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.
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 zh
this is fixed here
Change:
and all are used to determine which issuers are accepted. --> 服务帐号令牌颁发者的标识符。 <del> 颁发者将在已办法令牌的 "iss" 声明中检查此标识符。 </del> <ins> 颁发者将在已颁发令牌的 "iss" 声明中检查此标识符。 </ins> 此值为字符串或 URI。 如果根据 OpenID Discovery 1.0 规范检查此选项不是有效的 URI，则即使特性门控设置为 true， ServiceAccountIssuerDiscovery 功能也将保持禁用状态。

Discussion:
<html <!--StartFragment----service-account-issuer strings | "iss" URI OpenID Discovery 1.0 URI true ServiceAccountIssuerDiscovery OpenID service-account-issuer HTTPS URL URL {service-account-issuer}/.well-known/openid-configuration OpenID <!--EndFragment--“” </body</html
/language zh I assume this is a bug report. If possible, clarify whether the issue is with the upstream (English) docs or with the way those docs have been localized. /triage needs-information
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage bug 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 bug /triage accepted
/assign
Change:
# change is that the Hugo version is now an overridable argument rather than a fixed # environment variable. <del> FROM docker.io/library/golang:1.20-alpine </del> <ins> FROM docker.io/library/golang:1.23.0-alpine3.20 </ins> LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>"

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: You cannot run to get a local website preview, nor can you run to build the container locally. Proposed Solution: Fix local previewing by ensuring that builds a working container image <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: This is relevant to contributor experience. Optionally, we could run CI tests whenever there is a change to , or , and verify that we can: build a container image run Hugo inside that image (smoke test)
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
I am unable to produce this because being blocked to , the command never worked for me (in China). I'm curious though what kind of errors we have encountered and why an upgrade of Go is required.
you can read more on this thread TLDR; the error was: ! Due to the latest Hugo upgrade that requires Golang 1.23 when building the image. The fix works locally: ! +1 to running a test in the CI. Would that be something completely new or a pre-existing pipeline to enhance? Asking because I don't see any other GitHub workflow aside from . Note: I'm still getting accustomed to the codebase so this question might sound silly._
Got it. A change to Go version is necessary.
To test the container image build locally, run . You need access to the Docker registry; you don't need access to push to Google.
Change:
<ins> --- title: 节点资源管理器 content_type: concept weight: 50 --- <!-- --- reviewers: - derekwaynecarr - klueska title: Node Resource Managers content_type: concept weight: 50 --- --> <!-- overview --> <!-- In order to support latency-critical and high-throughput workloads, Kubernetes offers a suite of Resource Managers. The managers aim to co-ordinate and optimise node's resources alignment for pods configured with a specific requirement for CPUs, devices, and memory (hugepages) resources. --> Kubernetes 提供了一组资源管理器，用于支持延迟敏感的、高吞吐量的工作负载。 资源管理器的目标是协调和优化节点资源，以支持对 CPU、设备和内存（巨页）等资源有特殊需求的 Pod。 <!-- body --> <!-- The main manager, the Topology Manager, is a Kubelet component that co-ordinates the overall resource management process through its [policy](/docs/tasks/administer-cluster/topology-manager/). The configuration of individual managers is elaborated in dedicated documents: --> 主管理器，也叫拓扑管理器（Topology Manager），是一个 Kubelet 组件， 它通过[策略](/zh/docs/tasks/administer-cluster/topology-manager/)， 协调全局的资源管理过程。 各个管理器的配置方式会在专项文档中详细阐述： <!-- - [CPU Manager Policies](/docs/tasks/administer-cluster/cpu-management-policies/) - [Device Manager](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager) - [Memory Manger Policies](/docs/tasks/administer-cluster/memory-manager/) --> - [CPU 管理器策略](/zh/docs/tasks/administer-cluster/cpu-management-policies/) - [设备管理器](/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#device-plugin-integration-with-the-topology-manager) - [内存管理器策略](/zh/docs/tasks/administer-cluster/memory-manager/) </ins>

Discussion:
This is a Feature Request translate /docs/concepts/policy/node-resource- into Chinese. What would you like to be /zh/docs/concepts/policy/node-resource-
/triage accepted