jiebi/CodeConvo huggingface dataset:
Code change:
<ins> --- title: 启用拓扑感知提示 content_type: task min-kubernetes-server-version: 1.21 --- <!-- --- reviewers: - robscott title: Enabling Topology Aware Hints content_type: task min-kubernetes-server-version: 1.21 --- --> <!-- overview --> {{< feature-state for_k8s_version="v1.21" state="alpha" >}} <!-- _Topology Aware Hints_ enable topology aware routing with topology hints included in {{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}. This approach tries to keep traffic close to where it originated from; you might do this to reduce costs, or to improve network performance. --> _拓扑感知提示_ 启用具有拓扑感知能力的路由，其中拓扑感知信息包含在 {{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}} 中。 此功能尽量将流量限制在它的发起区域附近； 可以降低成本，或者提高网络性能。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- The following prerequisite is needed in order to enable topology aware hints: * Configure the {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to run in iptables mode or IPVS mode * Ensure that you have not disabled EndpointSlices --> 为了启用拓扑感知提示，先要满足以下先决条件： * 配置 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} 以 iptables 或 IPVS 模式运行 * 确保未禁用 EndpointSlices <!-- ## Enable Topology Aware Hints --> ## 启动拓扑感知提示 {#enable-topology-aware-hints} <!-- To enable service topology hints, enable the `TopologyAwareHints` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kube-apiserver, kube-controller-manager, and kube-proxy: --> 要启用服务拓扑感知，请启用 kube-apiserver、kube-controller-manager、和 kube-proxy 的 [特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/) `TopologyAwareHints`。 ``` --feature-gates="TopologyAwareHints=true" ``` ## {{% heading "whatsnext" %}} <!-- * Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints) for Services * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/) --> * 参阅面向服务的[拓扑感知提示](/zh/docs/concepts/services-networking/topology-aware-hints) * 参阅[用服务连通应用](/zh/docs/concepts/services-networking/connect-applications-service/) </ins>

Related discussion:
text: This is a Feature Request translate /docs/tasks/administer-cluster/enabling-topology-aware- into Chinese. What would you like to be /zh/docs/tasks/administer-cluster/enabling-topology-aware- /language zh /assign
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
Code change:
## Logs and auditing - [ ] Audit logs, if enabled, are protected from general access. <del> - [ ] The `/logs` API is disabled (you are running kube-apiserver with `--enable-logs-handler=false`). Kubernetes includes a `/logs` API endpoint, enabled by default, that lets users request the contents of the API server's `/var/log` directory over HTTP. Accessing that endpoint requires authentication. Allowing broad access to Kubernetes logs can make security information available to a potential attacker. As a good practice, set up a separate means to collect and aggregate control plane logs, and do not use the `/logs` API endpoint. Alternatively, if you run your control plane with the `/logs` API endpoint and limit the content of `/var/log` (within the host or container where the API server is running) to Kubernetes API server logs only. </del> ## Pod placement

Related discussion:
text: <brThere is no flag for , it seems to have already been removed from the code but not from the documentation.
/language en /sig docs /sig security Let this be a good first issue if triaged.
/assign
/triage accepted
Code change:
body.cid-community .community-section#events { <del> width: 100vw; </del> <ins> width: 100%; </ins> max-width: initial; margin-bottom: 0;

Related discussion:
text: 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: Proposed Solution: Page to Update: /assign
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
During my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.
/area web-development
I tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.
I see, In that case I'll try to find anymore pages that might be having the same issue.
Similar issue is present in case study
Code change:
- "`Default`": The Pod inherits the name resolution configuration from the node that the pods run on. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for more details. - "`ClusterFirst`": Any DNS query that does not match the configured cluster domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#effects-on-pods) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for details on how DNS queries are handled in those cases. - "`ClusterFirstWithHostNet`": For Pods running with hostNetwork, you should explicitly set its DNS policy "`ClusterFirstWithHostNet`".

Related discussion:
text: says: Pod's DNS Policy : The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details. “Related discussion” is a hyperlink to : Any DNS query that does not match the configured cluster domain suffix, such as "", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases. “Related discussion” is a hyperlink to Both hyper targets do not exist in the destination webpage (so that the browser scrolls to the right place). contains a hyperlink “See Inheriting DNS from the node” → , which as above does not exist.
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
/sig docs
Code change:
<p>If you haven't worked through the earlier sections, start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">Using minikube to create a cluster</a>.</p> <p><em>Scaling</em> is accomplished by changing the number of replicas in a Deployment</p> <ins> <p> <b> NOTE </b> If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, you may need to start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">creating a cluster</a> as the services may have been deleted </p> </ins> </div> <div class="col-md-4"> <div class="content__box content__box_lined">

Related discussion:
text: Kindly note that you asked us to delete the service in the previous section. Please update the docs by asking to restore the service first before running this command.
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
Could you please provide some details on the issue in the section? /triage needs-information
Page related to the issue: /language en /sig autoscaling
/kind bug
/assign
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: nginx spec: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: disktype operator: In values: - ssd containers: - name: nginx image: nginx imagePullPolicy: IfNotPresent </ins>

Related discussion:
text: This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Code change:
## 논 그레이스풀 노드 셧다운 {#non-graceful-node-shutdown} <del> {{< feature-state state="alpha" for_k8s_version="v1.24" >}} </del> <ins> {{< feature-state state="beta" for_k8s_version="v1.26" >}} </ins> 전달한 명령이 kubelet에서 사용하는 금지 잠금 메커니즘(inhibitor locks mechanism)을 트리거하지 않거나, 또는 사용자 오류(예: ShutdownGracePeriod 및 ShutdownGracePeriodCriticalPods가 제대로 설정되지 않음)로 인해

Related discussion:
text: This is a Feature Request Korean Localization for branch. What would you like to be Any localization contributions for Korean. Comments This issue is to notify the schedule of Korean localization to contributors. is the current work branch for Korean localization. Important dates A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch)  2~3 , main . PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /language ko /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 : ## In English is the current work branch for Korean localization.A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch) PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /help </details
/milestone dev-1.26-ko.1
/triage accepted
Outdated Korean contents in the dev-1.26-ko.1
Code change:
• [VirtualBox](https://www.virtualbox.org/wiki/Downloads) <del> {{< note >}} minikubeは、VMではなくホストでKubernetesコンポーネントを実行する`--vm-driver=none`オプションもサポートしています。 </del> <ins> Minikubeは、VMではなくホストでKubernetesコンポーネントを実行する`--vm-driver=none`オプションもサポートしています。 </ins> このドライバーを使用するには、[Docker](https://www.docker.com/products/docker-desktop)とLinux環境が必要ですが、ハイパーバイザーは不要です。 <del> noneドライバーを使用する場合は、[Docker](https://www.docker.com/products/docker-desktop)からdockerのaptインストールを使用することをおすすめします。 dockerのsnapインストールは、minikubeでは機能しません。 {{< /note >}} </del> <ins> Debian系のLinuxで`none`ドライバーを使用する場合は、snapパッケージではなく`.deb`パッケージを使用してDockerをインストールしてください。snapパッケージはMinikubeでは機能しません。 [Docker](https://www.docker.com/products/docker-desktop)から`.deb`パッケージをダウンロードできます。 {{< caution >}} `none` VMドライバーは、セキュリティとデータ損失の問題を引き起こす可能性があります。 `--vm-driver=none`を使用する前に、詳細について[このドキュメント](https://minikube.sigs.k8s.io/docs/reference/drivers/none/) を参照してください。 {{< /caution >}} MinikubeはDockerドライバーと似たような`vm-driver=podman`もサポートしています。Podmanを特権ユーザー権限(root user)で実行することは、コンテナがシステム上の利用可能な機能へ完全にアクセスするための最もよい方法です。 {{< caution >}} `podman` ドライバーは、rootでコンテナを実行する必要があります。これは、通常のユーザーアカウントが、コンテナの実行に必要とされるすべてのOS機能への完全なアクセスを持っていないためです。 {{< /caution >}} </ins> ### パッケージを利用したMinikubeのインストール

Related discussion:
text: 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 Update tasks/tools/install- to follow v1.17 of the original (Englist) text. Why is this needed content/ja/docs/tasks/tools/install- is outdated. Comments /language ja /good-first-issue File to update Original https://v1- diff between translated and v1.17 Note Currently, we use branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
This request has been marked as suitable for new contributors. 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. --Update tasks/tools/install- to follow v1.17 of the original (Englist) text. content/ja/docs/tasks/tools/install- is outdated. /language ja /good-first-issue Currently, we use branch. Please open a PR targeting the branch. 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
/close
Closing this issue. <detailsIn response to : /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
Code change:
message: | 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> May 16 - 20, 2022. <ins> - name: Kubecon 2022 NA startTime: 2022-10-17T00:00:00 # Added in https://github.com/kubernetes/website/pull/36107 endTime: 2022-10-29T00:00:00 style: >- background: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(114,114,255) 100%); color: #fff; title: | <img src="/images/announcements/kccnc-na-2022-white.svg" style="float: right; height: 80px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon NA 2022</a> <em>Detroit, Michigan + Virtual</em>. message: | 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> October 24 - 28, 2022. </ins>

Related discussion:
text: 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 An announcement banner for KubeCon NA 2022 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed KubeCon NA 2022 is around the corner. It is important we start informing the community about this amazing event by displaying a banner on the Kubernetes website. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This change will need steering committee approval. I would set the banner to start on the 22nd of August and end on the 28th of October, 2022 at 18:00 CEST /priority important-soon
Thanks for filing this I think the banner should start on the 15th of October. How does that sound? /priority important-longterm /remove-priority important-soon
15th sounds great!
/triage accepted
/assign
Code change:
sudo apt-get update sudo apt-get install -y kubectl ``` <ins> {{< note >}} In releases older than Debian 12 and Ubuntu 22.04, `/etc/apt/keyrings` does not exist by default. You can create this directory if you need to, making it world-readable but writeable only by admins. {{< /note >}} </ins> {{% /tab %}}

Related discussion:
text: 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 documentation recommends installing the repository signing key to . This is contrary to the recommendation in the Debian documentation : There is no keyring package in the k8s repository that would replace and (when necessary) update a keyring installed to , so the keyring should go to . Proposed Solution: Replace with in the instructions for setting up the apt package repository. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This is a reasonable change. We could also mention that and document how to make sure it exists. /language en /sig cluster-lifecycle /remove-kind bug It's not exactly a bug, and it's not a feature either. Let's not choose. /triage accepted /priority backlog /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 : This is a reasonable change. We could also mention that In releases older than Debian 12 and Ubuntu 22.04, does not exist by default. /sig cluster-lifecycle /priority backlog /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
please update the issue description to not mention updating the localized versions. Localization teams pick those changes up and will file their own issues if needed.
I've removed the mention of localization.
I will give a try on this. /assign
Thank you very much! :slightlysmilingface:
Code change:
- [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.html)についてもっと学習しましょう。 - [コンテナランタイム](/ja/docs/concepts/architecture/cri)についてもっと学習しましょう。 <del> - [cgroupドライバー](/docs/setup/production-environment/container-runtimes#cgroup-drivers)についてもっと学習しましょう。 </del> <ins> - [cgroupドライバー](/ja/docs/setup/production-environment/container-runtimes#cgroup-drivers)についてもっと学習しましょう。 </ins>

Related discussion:
text: 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 Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref. /language ja
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 want to work on this. Have you already started working on it? It seems that some pages linked from here are not translated yet: dockershim-removal template For now, I'm going to start working on dockershim related contents. Feel free to notify me if this conflicts with your work.
I'll assign myself since you haven't assigned youself to this issue. Please tell me if this conflicts with you work. /assign
Code change:
communicates with). 1. (Recommended) If you have plans to upgrade this single control-plane `kubeadm` cluster <del> to high availability you should specify the `--control-plane-endpoint` to set the shared endpoint for all control-plane nodes. Such an endpoint can be either a DNS name or an IP address of a load-balancer. </del> <ins> to [high availability](/docs/setup/production-environment/tools/kubeadm/high-availability/) you should specify the `--control-plane-endpoint` to set the shared endpoint for all control-plane nodes. Such an endpoint can be either a DNS name or an IP address of a load-balancer. </ins> 1. Choose a Pod network add-on, and verify whether it requires any arguments to be passed to `kubeadm init`. Depending on which third-party provider you choose, you might need to set the `--pod-network-cidr` to

Related discussion:
text: Please note: This issue is not suitable for new contributors since you need some familiarity with how Kubernetes works. The Kubernetes website currently lacks a guide on creating Windows/Linux nodes. See for more details. SIG Windows opted to remove the guide that did exist for creating Windows nodes, in PR Write a new task page about creating nodes for all operating systems. This could, potentially, be in a tabbed format as mentions in the issue referenced above. We would also need the entry reflected on the creates the Linux task page by moving / refactoring the existing "join node" contents from the "create a cluster" page: creates the Windows task page by taking the content from at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: adds tabs in the to choose between OS for joining nodes. /priority backlog /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 : Problem Statement: /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
/triage accepted Thank you for filing this
/sig cluster-lifecycle
If you know how to set up new nodes (with, at least, the tool): you can work on this issue. You don't need anyone's permission to open a pull request. All we ask is that you read our and that you abide by the project's code of conduct.
/assign
Relevant to
Are you still working on this issue?
/assign sending PR soon.