jiebi/CodeConvo huggingface dataset:
Change:
This is a Feature Request What would you like to be Add the following hyperlink to under the in reference docs. Why is this needed Adding the hyperlink will help the readers to know about RFC3339. Proposed Solution: Where to add this link: In above code instead of it should be Comments /sig docs /language en
/sig auth /triage accepted /good-first-issue Please save this for a new contributor to the Kubernetes documentation. This is a great opportunity for new contributor to make their first contribution to the k8s project.
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 : /sig auth /triage accepted /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

Discussion:
The `expiration` field controls the expiry of the token. Expired tokens are rejected when used for authentication and ignored during ConfigMap signing. <del> The expiry value is encoded as an absolute UTC time using RFC3339. Enable the </del> <ins> The expiry value is encoded as an absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339). Enable the </ins> `tokencleaner` controller to automatically delete expired tokens. ## Token Management with kubeadm
Change:
in this page the link about Verify Signed Kubernetes Artifacts for install cosign changed --- !
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
It is a documentation issue, Docs issues are implemented in . Please open in this repo.
/transfer website
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig doc 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 /kind documentation

Discussion:
You will need to have the following tools installed: <del> - `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/)) </del> <ins> - `cosign` ([install guide](https://docs.sigstore.dev/cosign/system_config/installation/)) </ins> - `curl` (often provided by your operating system) - `jq` ([download jq](https://jqlang.github.io/jq/download/))

--certificate-identity krel-staging@k8s-releng-prod.iam.gserviceaccount.com  --certificate-oidc-issuer https://accounts.google.com  "$VERSION.spdx" <del> ``` </del>  No newline at end of file <ins> ``` </ins>
Change:
Page: I have problems understanding this text. First: If I read that, then I think Finalizers seem to get ignored if you use background-deletion. But I don't think so. Second: "... the controller cleans up the dependent objects". What is "the controller" here? If I have a custom controller for my CRDs. Is that meant with "the controller"?
/language en
I also agree there is room of improving the existing content in the page.
Finalizers are not ignored during background deletion. The owner object is marked for deletion, but finalizers still execute before fully deleting it. The controller refers to the Kubernetes controller that manages the lifecycle of resources, which could include your custom controller for CRDs. It's responsible for cleaning up dependent objects in the background.
/retitle Garbage Collection: Background deletion explanation is hard to understand
/triage accepted /priority backlog
If there is still room to work on this issue, I would like to work on this. Kindly /assign this to me

Discussion:
### Background cascading deletion {#background-deletion} In background cascading deletion, the Kubernetes API server deletes the owner <del> object immediately and the controller cleans up the dependent objects in the background. By default, Kubernetes uses background cascading deletion unless </del> <ins> object immediately and the garbage collector controller (custom or default) cleans up the dependent objects in the background. If a finalizer exists, it ensures that objects are not deleted until all necessary clean-up tasks are completed. By default, Kubernetes uses background cascading deletion unless </ins> you manually use foreground deletion or choose to orphan the dependent objects. See [Use background cascading deletion](/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)
Change:
This is a Bug Report Problem: The description and its proceeding text on the scheduling index page are almost duplicated. Proposed Solution: The following text on the index page needs to be removed: Page to Update: /language en
/assign
I have a specific fix in mind: suppress the display of the page description at the start of the page. That way, we retain the tooltips that we want, and we avoid the duplication.
/language en /priority backlog /triage accepted

Discussion:
title: "Scheduling, Preemption and Eviction" weight: 95 content_type: concept <del> description: > In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that the kubelet can run them. Preemption is the process of terminating Pods with lower Priority so that Pods with higher Priority can schedule on Nodes. Eviction is the process of proactively terminating one or more Pods on resource-starved Nodes. </del> no_list: true ---
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: In the Chinese docs, the link to the etcd FAQ starts with a forward slash This is causing Hugo to error out when building in Windows. Since this line has been there for quite a few years, I don't know how Hugo kept building till now. Anyway, this slash is creating the wrong link in production itself. ! Proposed Solution: Just removing the slash is enough. Page to Update: This issue is present in the docs for older versions too. Should we look into fixing it for other branches? <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Should I look into fixing this issue in older versions of the page?
/assign
backport fixes are welcome, but we don't require them.
I guess, I will leave them be then

Discussion:
也可以运行在不同的机器上以获得更好的安全性和可用性。 因为 etcd 存储着集群的配置数据，应该经常性地对 etcd 数据库进行备份， 以确保在需要的时候你可以修复该数据库。与配置和使用 etcd 相关的细节可参阅 <del> [etcd FAQ](/https://etcd.io/docs/v3.5/faq/)。 </del> <ins> [etcd FAQ](https://etcd.io/docs/v3.5/faq/)。 </ins> 更多的细节可参阅[为 Kubernetes 运维 etcd 集群](/zh-cn/docs/tasks/administer-cluster/configure-upgrade-etcd/) 和[使用 kubeadm 配置高可用的 etcd 集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)。 <!--
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 zh translation of the blog post "10 Years of Kubernetes" has a link which repeats the part of it and thus directs to an inaccessible page. Proposed Solution: Just removing the repetition. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--This issue is similar to
/assign
/priority backlog /triage accepted

Discussion:
[Kubernetes 历史上最大的迁移](/zh-cn/blog/2024/05/20/completing-cloud-provider-migration/)中，大约删除了 150 万行代码，将核心组件的二进制文件大小减小了约 40%。在项目早期，很明显可扩展性是成功的关键。 然而，如何实现这种可扩展性并不总是很清楚。此次迁移从核心 Kubernetes 代码库中删除了各种特定于供应商的功能。 <del> 现在，特定于供应商的功能可以通过其他可插拔的扩展功能或模式更好地提供，例如[自定义资源定义（CRD）](https://https://kubernetes.io/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-resources/) </del> <ins> 现在，特定于供应商的功能可以通过其他可插拔的扩展功能或模式更好地提供，例如[自定义资源定义（CRD）](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) </ins> 或 [Gateway API](https://gateway-api.sigs.k8s.io/) 等 API 标准。 Kubernetes 在为其庞大的用户群体提供服务时也面临着新的挑战，社区正在相应地进行调整。其中一个例子是将镜像托管迁移到新的、由社区拥有的 registry.k8s.io。为用户提供预编译二进制镜像的出口带宽和成本已经变得非常巨大。这一新的仓库变更使社区能够以更具成本效益和性能高效的方式继续提供这些便利的镜像。