jiebi/CodeConvo huggingface dataset:
Change:
--> * 了解 Kubernetes 中的[属主与依赖](/zh/docs/concepts/overview/working-with-objects/owners-dependents/) * 了解 Kubernetes [finalizers](/zh/docs/concepts/overview/working-with-objects/finalizers/) <del> * 了解[垃圾收集](/zh/docs/concepts/workloads/controllers/garbage-collection/). </del> <ins> * 了解[垃圾收集](/zh/docs/concepts/architecture/garbage-collection/). </ins>

Discussion:
There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /close 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
Change:
This label has been deprecated. Please use `kubernetes.io/os` instead. <ins> ### kube-aggregator.kubernetes.io/automanaged {#kube-aggregator-kubernetesio-automanaged} Example: `kube-aggregator.kubernetes.io/automanaged: "onstart"` Used on: APIService The `kube-apiserver` sets this label on any APIService object that the API server has created automatically. The label marks how the control plane should manage that APIService. You should not add, modify, or remove this label by yourself. {{< note >}} Automanaged APIService objects are deleted by kube-apiserver when it has no built-in or custom resource API corresponding to the API group/version of the APIService. {{< /note >}} There are two possible values: - `onstart`: The APIService should be reconciled when an API server starts up, but not otherwise. - `true`: The API server should reconcile this APIService continuously. </ins> ### kubernetes.io/hostname {#kubernetesiohostname} Example: `kubernetes.io/hostname: "ip-172-20-114-199.ec2.internal"`

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: Code from the Kubernetes project sets (or previously did set) a label, This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. If it's deprecated, we should mark it as deprecated but still document it. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog
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
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /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
Created a , Havent seen any document for it's deprecation . Please let me know if any change is needed.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
Since this issue's PR is already merged. i'd like to close it
/close
Closing this issue. <detailsIn response to : /close </details
Change:
See [Enforcing Pod Security at the Namespace Level](/docs/concepts/security/pod-security-admission) for more information. <ins> ### rbac.authorization.kubernetes.io/autoupdate Example: `rbac.authorization.kubernetes.io/autoupdate: "false"` Used on: ClusterRole, ClusterRoleBinding, Role, RoleBinding When this annotation is set to `"true"` on default RBAC objects created by the kube-apiserver, they are automatically updated at server start to add missing permissions and subjects (extra permissions and subjects are left in place). To prevent autoupdating a particular role or rolebinding, set this annotation to `"false"`. If you create your own RBAC objects and set this annotation to `"false"`, `kubectl auth reconcile` (which allows reconciling arbitrary RBAC objects in a {{< glossary_tooltip text="manifest" term_id="manifest" >}}) respects this annotation and does not automatically add missing permissions and subjects. </ins> ### kubernetes.io/psp (deprecated) {#kubernetes-io-psp} Example: `kubernetes.io/psp: restricted`

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: Kubernetes can use an annotation, , but this is not registered or documented. Proposed Solution: Document the annotation in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig auth
mentions this annotation, so it has been used in the past (and, I suspect, it is still used).
/assign
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/lifecycle frozen /priority backlog
Thanks SIG Auth folks!
Change:
LOCALIZED="$1" # Try get the English version <del> EN_VERSION=`echo $LOCALIZED | sed "s/content/..//content/en//g"` </del> <ins> EN_VERSION=`echo $LOCALIZED | sed "s/content/.{2,5}//content/en//g"` </ins> if [ ! -e $EN_VERSION ]; then echo "$EN_VERSION has been removed." exit 3

Discussion:
This is a Bug Report cannot sync files under correctly. This problem should exist with $LOCALIZED more than 2 characters. When happened when zh -zh-cn see <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Proposed Solution:** needs to be updated to <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/cc /language zh
/triage accepted
I found this problem when reviewing this PR , the commit time of the version is later than the version, but did not correctly find the difference between the 2 versions.
nice catch!
When the script was developed, I was only focusing on markdown files.
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> ### 手动节点管理 {#manual-node-administration} </ins> 你可以使用 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 来创建和修改 Node 对象。

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 #self-registration-of-nodes #manual-node-administration # # Proposed Solution: {#self-registration-of-nodes} {#manual-node-administration} 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 zh /assign
Change:
`attach` and `port-forward` requests. - `SupportIPVSProxyMode`: Enable providing in-cluster service load balancing using IPVS. <del> See [service proxies](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) for more details. </del> <ins> See [service proxies](/docs/reference/networking/virtual-ips/) for more details. </ins> - `SupportNodePidsLimit`: Enable the support to limiting PIDs on the Node.  The parameter `pid=<number>` in the `--system-reserved` and `--kube-reserved` options can be specified to

Discussion:
This is a Bug Report Problem: The link for under is wrong. It is redirected to the instead of that it should redirect to the . It is due to the following PR: Proposed Solution: It should redirect to instead of Page to Update:
/assign /sig docs
/retitle Incorrect link for Service Proxies /language en /triage accepted /priority backlog
Fixed it here:
Change:
returned. In this case, the client will need to start from the beginning or omit the `limit` parameter. <del> For example, if there are 1,253 pods on the cluster and you wants to receive chunks </del> <ins> For example, if there are 1,253 pods on the cluster and you want to receive chunks </ins> of 500 pods at a time, request those chunks as follows: 1. List all of the pods on a cluster, retrieving up to 500 pods each time.

Discussion:
in
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 /sig docs
I would to like to work on this issue.
/assign
The issue is fixed .
Change:
--> 此页面显示如何创建公开外部 IP 地址的 Kubernetes 服务对象。 ## {{% heading "prerequisites" %}} <!-- * Install [kubectl](/docs/tasks/tools/install-kubectl/).

Discussion:
This is a Bug Report Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- outdated <!-- 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: Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- is different with English version page. Proposed Solution: Update Chinese page Page to Update: contentzhdocstutorialsstateless-applicationexpose-external-ip- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
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. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign
Change:
} ``` <del> If the application is deployed as a Pod in the cluster, see [Accessing the API from within a Pod](#accessing-the-api-from-within-a-pod). </del> <ins> If the application is deployed as a Pod in the cluster, see [Accessing the API from within a Pod](/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod). </ins> #### Python client

Discussion:
Link broken or pointing to a wrong link. Under section: Programmatic access to the API. The link provided in the below line seems to be broken to wrong.
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 think this report is about the page can you paste in the text (or HTML source) of the broken hyperlink /triage needs-information
Change:
<ins> --- title: Affinity id: affinity date: 2019-01-11 full_link: /docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity short_description: > Rules used by the scheduler to determine where to place pods aka: tags: - fundamental --- In Kubernetes, _affinity_ is a set of rules that give hints to the scheduler about where to place pods. <!--more--> There are two kinds of affinity: * [node affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) * [pod-to-pod affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity) The rules are defined using the Kubernetes {{< glossary_tooltip term_id="label" text="labels">}}, and {{< glossary_tooltip term_id="selector" text="selectors">}} specified in {{< glossary_tooltip term_id="pod" text="pods" >}}, and they can be either required or preferred, depending on how strictly you want the scheduler to enforce them. </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 should use a glossary tooltip for “affinity” Why is this needed Kubernetes uses the term “affinity” to mean a specific thing. A tooltip (and the hyperlink it implies) helps a reader learn more about this term if they are not sure. Comments /language en
/triage accepted
Hey, I will like to work on this !! Please let me know how can I proceed with this !! !!
/assign
Change:
description: "プロジェクトに不慣れでも、長い間関わっていたとしても、誰でもコントリビュートすることができます。" button: "ドキュメントにコントリビュートする" button_path: /docs/contribute <del> - name: release-notes title: "K8sリリースノート" </del> <ins> - name: training title: "トレーニング" description: "Kubernetesの資格を取得して、クラウドネイティブプロジェクトを成功させます！" button: "トレーニングを見る" button_path: "/training" - name: Download title: "Kubernetesをダウンロードする" </ins> description: "もしKubernetesをインストールする、また最新バージョンにアップグレードする場合、最新のリリースノートを参照してください。" button: "Kubernetesをダウンロードする" button_path: "/releases/download"

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:
title: "bash auto-completion on macOS" description: "Some optional configuration for bash auto-completion on macOS." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- ### Introduction

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:
* Kubernetes API Versions * [1.6](/docs/api-reference/v1.6/) * [1.5](/docs/api-reference/v1.5/) <del> * Federation API * [v1 Operations](docs/reference/federation/v1/operations.html) * [v1 Model Definitions](docs/reference/federation/v1/definitions.html) * [federation/v1beta1 Operations](docs/reference/federation/v1beta1/operations.html) * [federation/v1beta1 Model Definitions](docs/reference/federation/v1beta1/definitions.html) * [extensions/v1beta1 Operations](docs/reference/federation/extensions/v1beta1/operations.html) * [extensions/v1beta1 Model Definitions](docs/reference/federation/extensions/v1beta1/definitions.html) </del> ## CLI Reference

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 points to non-existent page Proposed Solution: Fix the link. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
* 'Distribute volume': `volumetype: none` 有关可用的卷类型和管理选项， <del> 请参阅[管理指南](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/part-Overview.html)。 </del> <ins> 请参阅[管理指南](https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/)。 </ins> 更多相关的参考信息， 请参阅[如何配置 Heketi](https://github.com/heketi/heketi/wiki/Setting-up-the-topology)。

Discussion:
stay In the page, the link at the text "vSphereVolume CSI " should be -csi-migration
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
/language zh
Are you still working on it?
I submitted PR to solve this issue and put you as the co-author.
Change:
cd "hugo-${HUGO_VERSION}" &&  go install --tags extended <del> FROM docker.io/library/golang:1.20-alpine </del> <ins> FROM docker.io/library/golang:1.23.0-alpine3.20 </ins> RUN apk add --no-cache  runuser 

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.