jiebi/CodeConvo huggingface dataset:
Change:
### Loadbalancing <del> An Ingress controller is bootstrapped with some load balancing policy settings that it applies to all Ingress, such as the load balancing algorithm, backend weight scheme, and others. More advanced load balancing concepts (e.g.: persistent sessions, dynamic weights) are not yet exposed through the Ingress. You can still get these features through the [service loadbalancer](https://git.k8s.io/contrib/service-loadbalancer). With time, we plan to distill load balancing patterns that are applicable cross platform into the Ingress resource. </del> <ins> An Ingress controller is bootstrapped with some load balancing policy settings that it applies to all Ingress, such as the load balancing algorithm, backend weight scheme, and others. More advanced load balancing concepts (e.g.: persistent sessions, dynamic weights) are not yet exposed through the Ingress. You can still get these features through the [service loadbalancer](https://github.com/kubernetes/ingress-nginx/blob/master/docs/catalog.md). With time, we plan to distill load balancing patterns that are applicable cross platform into the Ingress resource. </ins> It's also worth noting that even though health checks are not exposed directly through the Ingress, there exist parallel concepts in Kubernetes such as [readiness probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) which allow you to achieve the same end result. Please review the controller specific docs to see how they handle health checks ([nginx](https://git.k8s.io/ingress-nginx/README.md), [GCE](https://git.k8s.io/ingress-gce/README.md#health-checks)).

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: Ingress documentation contains a link to a project () that is deprecated. Proposed Solution: Update the link and the docs to point , which lists non-cloud ingress alternatives. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
## Multi-architecture Images with Manifests <del> As well as providing binary images, a container registry can also server a [container image manifest](https://github.com/opencontainers/image-spec/blob/master/manifest.md). A manifest can reference image manifests for architecturew-specific versions of an container. The idea is that you can have a name for an image (for example: `pause`, `example/mycontainer`, `kube-apiserver`) and allow different systems to fetch the right binary image for the machine architecture they are using. </del> <ins> As well as providing binary images, a container registry can also server a [container image manifest](https://github.com/opencontainers/image-spec/blob/master/manifest.md). A manifest can reference image manifests for architecture-specific versions of an container. The idea is that you can have a name for an image (for example: `pause`, `example/mycontainer`, `kube-apiserver`) and allow different systems to fetch the right binary image for the machine architecture they are using. </ins> Kubernetes itself typically names container images with a suffix `-$(ARCH)`. For backward compatibility, please generate the older images with suffixes. The idea is to generate say `pause` image which has the manifest for all the arch(es) and say `pause-amd64` which is backwards compatible for older configurations or YAML files which may have hard coded the images with suffixes.

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: There seems to be a wrong spelling in concepts/containers/images/#multi-architecture-images-with-manifests Proposed Solution: Correct the typo Before: A manifest can reference image manifests for architecturew-specific versions of an container After A manifest can reference image manifests for architecture-specific versions of an container Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 <!--Additional Information:--
Thanks /help /kind bug /priority backlog /language en
This request has been marked as needing help from a contributor. 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 : Thanks /help /kind bug /priority backlog /language en 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
/assign
Change:
To use this repository, you need the following installed locally: <del> - [yarn](https://yarnpkg.com/) </del> - [npm](https://www.npmjs.com/) - [Go](https://golang.org/) - [Hugo (Extended version)](https://gohugo.io/)

Discussion:
This is a Bug Report As discussed in the SIG-Docs meeting, the current steps for building doc website in README is incomplete in the following point of views. It requires yarn on top of npm, but is missing and package- is there. did not work for me but I need further investigation on it. The build step is going to be equal in containerized and local in , but yarn installation or npm ci is currently missing in . <!--Required Information--Proposed Solution: and remove yarn from the dependency the npm command inside of the container Page to Update: N/A
Here's my cat picture after the sig-docs meeting lol !
AIUI, the live website build (within Netlify) relies on , and does not use Yarn.
/area web-development
Could you have a quick look if npm ci in local works just fine?
Yes, I believe so.
worked in my local environment
/kind bug /priority important-longterm
/sig contributor-experience I suppose
Change:
The kubelet automatically tries to create a {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}} on the Kubernetes API server for each static Pod. This means that the Pods running on a node are visible on the API server, <del> but cannot be controlled from there. </del> <ins> but cannot be controlled from there. See the guide [Create static Pods](/docs/tasks/configure-pod-container/static-pod) for more information. </ins> {{< note >}} The `spec` of a static Pod cannot refer to other API objects

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 Change to link to Why is this needed This change will help readers to find relevant documentation. Comments /language en /triage accepted /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 Feature Request <!-- See for guidance on writing an actionable issue description. --Change to link to This change will help readers to find relevant documentation. /language en /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
This is a good first issue. If you have already worked on an issue for Kubernetes docs, please save this issue for someone who has not.
I would like to work on this issue /assign
:exclamation: please read
I would like to work on this issue /assign
/assign
Change:
During the two-month maintenance mode period, Release Managers may cut additional maintenance releases to resolve: <del> - CVEs (under the advisement of the Product Security Committee) </del> <ins> - CVEs (under the advisement of the Security Response Committee) </ins> - dependency issues (including base image updates) - critical core component issues

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 change We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. Why is this needed renamed the product security committee to “Security Response Committee” Comments /language en /sig docs /sig security /help /triage accepted Relevant to
This request has been marked as needing help from a contributor. 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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --We should find the term “product security committee” anywhere within the English-language docs, and replace that term with “security response committee”. We don't need to revise any blog articles. If we feel there are some blog articles where an exception is justified, I'd revise those in a separate PR per article as the review process is different. renamed the product security committee to “Security Response Committee” /language en /sig docs /sig security /help /triage accepted Relevant to 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
thanks , PR's are incoming org wide for the change.
Hi, I would like to take this up /assign
Change:
</div> <div class="content__box content__box_fill"> <p><i> <del> Kubernetesは、コンピュータクラスター内およびコンピュータクラスター間でのアプリケーションコンテナの配置(スケジューリング)および実行を調整する、プロダクショングレードのオープンソースプラットフォームです。 </del> <ins> Kubernetesは、コンピュータークラスター内およびコンピュータークラスター間でのアプリケーションコンテナの配置(スケジューリング)および実行を調整する、プロダクショングレードのオープンソースプラットフォームです。 </ins> </i></p> </div> </div>

Discussion:
This is a Feature Request What would you like to be fix the notation variations of the term "computer" valid: invalid: | Why is this needed In Japanese documents, There are notation variations. The Japanese localization of k/website has rules, so we want to follow them. Comments FYI: Japanese Localization document: command /language ja /area localization /help /good-first-issue
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
PTAL before woking
PR
/remove-help
Change:
- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) <del> LoggingConfiguration contains logging options Refer [Logs Options](https://github.com/kubernetes/component-base/blob/master/logs/options.go) for more information. </del> <ins> MemoryReservation specifies the memory reservation of different types for each NUMA node </ins> <table class="table"> <thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. 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
I would like to take up this ticket.
Change:
# i18n strings for the Korean translation. # NOTE: Please keep the entries in alphabetical order when editing <ins> # Avoid using conjunction_1. # Must match the context in layouts/shortcodes/release-data.html # Appears on https://kubernetes.io/releases/ # For example the "and" in "Complete 1.25 Schedule and Changelog" [conjunction_1] other = "및" </ins> [caution] other = "주의:"

Discussion:
What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language ko
/triage accepted Thanks !
/assign
Change:
and **will require changes** for users who were previously using the in-tree provider integrations. The legacy integrations offered compatibility with Azure, AWS, GCE, OpenStack, and vSphere; however for AWS and OpenStack the <del> compiled-in integrations were removed in Kubernetes versions 1.26 and 1.27, </del> <ins> compiled-in integrations were removed in Kubernetes versions 1.27 and 1.26, </ins> respectively. ## What has changed?

Discussion:
in this sentence the AWS and OpenStack positions at the end should be swapped, or perhaps clarified. OpenStack was removed in 1.25 (gone in 1.26) and AWS was removed in 1.26 (gone in 1.27).
Blog related to the issue: /language en
/area blog
/triage accepted
Change:
<ins> --- title: Turnkey 云解决方案 content_type: concept weight: 30 --- <!-- --- title: Turnkey Cloud Solutions content_type: concept weight: 30 --- --> <!-- overview --> <!-- This page provides a list of Kubernetes certified solution providers. From each provider page, you can learn how to install and setup production ready clusters. --> 本页列示 Kubernetes 认证解决方案供应商。 在每一个供应商分页，你可以学习如何安装和设置生产就绪的集群。 <!-- body --> {{< cncf-landscape helpers=true category="certified-kubernetes-hosted" >}} </ins>

Discussion:
translate setup/production-environment/turnkey- into Chinese
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
Change:
## 每个准入控制器的作用是什么？ <del> ### AlwaysAdmit {#alwaysadmit} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### AlwaysAdmit {#alwaysadmit} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> 该准入控制器会允许所有的 pod 接入集群。已废弃，因为它的行为根本就和没有准入控制器一样。

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
<li data-type="histogram"><label class="metric_detail">Type:</label> <span class="metric_type">Histogram</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">jwt_issuer_hash</span><span class="metric_label">result</span></li></ul> </div><div class="metric" data-stability="alpha"> <ins> <div class="metric_name">apiserver_authorization_config_controller_automatic_reload_last_timestamp_seconds</div> <div class="metric_help">Timestamp of the last automatic reload of authorization configuration split by status and apiserver identity.</div> <ul> <li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li> <li data-type="gauge"><label class="metric_detail">Type:</label> <span class="metric_type">Gauge</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span><span class="metric_label">status</span></li></ul> </div><div class="metric" data-stability="alpha"> <div class="metric_name">apiserver_authorization_config_controller_automatic_reloads_total</div> <div class="metric_help">Total number of automatic reloads of authorization configuration split by status and apiserver identity.</div> <ul> <li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li> <li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span><span class="metric_label">status</span></li></ul> </div><div class="metric" data-stability="alpha"> </ins> <div class="metric_name">apiserver_authorization_decisions_total</div> <div class="metric_help">Total number of terminal decisions made by an authorizer split by authorizer type, name, and decision.</div> <ul>

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: removed metric from the documented metrics for Kubernetes v1.30, but the metric is still collected for the API server (ref: and ). Proposed Solution: Reinstate the documentation for such metric. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.30 <!--Additional Information:--
/sig instrumentation
/triage accepted
This metrics exists in the file generated by . Or there is a problem with the file generated by before. Let me generate the metrics file again and see. /assign
After I re-ran the script, some metrics were indeed missing (not just metrics ), it was a problem with the generated script, I will take a closer look.
Change:
- if you select `whenUnsatisfiable: ScheduleAnyway`, the scheduler gives higher precedence to topologies that would help reduce the skew. --> <del> - **maxSkew** 描述这些 Pod 可能被均匀分布的程度。你必须指定此字段且该数值必须大于零。 </del> <ins> - **maxSkew** 描述这些 Pod 可能被不均匀分布的程度。你必须指定此字段且该数值必须大于零。 </ins> 其语义将随着 `whenUnsatisfiable` 的值发生变化： - 如果你选择 `whenUnsatisfiable: DoNotSchedule`，则 `maxSkew` 定义目标拓扑中匹配 Pod 的数量与

Discussion:
the Chinese translation is wrong, "" should be "" see from English site:
/language zh
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn </details
/language zh
/sig docs
/triage accepted
/assign
Change:
to create an `Eviction` object that triggers graceful pod termination. --> API 发起的驱逐是一个先调用 <del> [Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/create-eviction-pod-v1-core) 创建驱逐对象，再由该对象体面地中止 Pod 的过程。 </del> <ins> [Eviction API](/docs/reference/generated/kubernetes-api/{{<param "version">}}/#create-eviction-pod-v1-core) 创建 `Eviction` 对象，再由该对象体面地中止 Pod 的过程。 </ins> <!--more-->

Discussion:
There is a bug: "Eviction API"'s hyperlink status is 404, it should be changed 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
/kind bug /language zh
/assign
Change:
#### Install Snapshot Beta CRDs - `kubectl create -f config/crd` <del> - [https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd](https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd) </del> <ins> - [https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd](https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd) </ins> - Do this once per cluster

Discussion:
Links are broken on this page:
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 Broken link in article /language en /area blog
/assign
will you please test the fix @ https://deploy-preview---kubernetes-io-master-
Change:
## ステートフルアプリケーション <del> * [StatefulSetの基本](/docs/tutorials/stateful-application/basic-stateful-set/) </del> <ins> * [StatefulSetの基本](/ja/docs/tutorials/stateful-application/basic-stateful-set/) </ins> <del> * [例: 永続ボリュームを使ったWordPressとMySQLのデプロイ](/ja/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) </del> <ins> * [例: Persistent Volumeを使用したWordpressとMySQLをデプロイする](/ja/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) </ins> <del> * [例: Stateful Setsを使ったCassandraのデプロイ](/docs/tutorials/stateful-application/cassandra/) </del> <ins> * [例: Stateful Setを使用したCassandraのデプロイ](/ja/docs/tutorials/stateful-application/cassandra/) </ins> * [CP(一貫性＋分断耐性)分散システムZooKeeperの実行](/docs/tutorials/stateful-application/zookeeper/) <del> ## クラスター * [AppArmor](/docs/tutorials/clusters/apparmor/) * [seccomp](/docs/tutorials/clusters/seccomp/) </del> ## サービス <ins> * [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) </ins> * [Source IPを使う](/ja/docs/tutorials/services/source-ip/) <ins> ## セキュリティ * [クラスターレベルのPod Securityの標準の適用](/docs/tutorials/security/cluster-level-pss/) * [NamespaceレベルのPod Securityの標準の適用](/docs/tutorials/security/ns-level-pss/) * [AppArmor](/docs/tutorials/security/apparmor/) * [seccomp](/docs/tutorials/security/seccomp/) </ins> ## {{% heading "whatsnext" %}} チュートリアルのページタイプについての情報は、[Content Page Types](/docs/contribute/style/page-content-types/)を参照してください。

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. --Update Japanese translation of Why is this needed It seems be outdated a bit Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted