jiebi/CodeConvo huggingface dataset:
Change:
``` NAME           TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE <del> frontend       ClusterIP   10.0.0.112   <none>       80/TCP   6s </del> <ins> frontend       ClusterIP   10.0.0.112   <none>        80/TCP         6s </ins> kubernetes     ClusterIP   10.0.0.1     <none>        443/TCP        4m mongo          ClusterIP   10.0.0.151   <none>        6379/TCP       2m ```

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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
Change:
Check that kubectl is properly configured by getting the cluster state: --> 为了让 kubectl 能发现并访问 Kubernetes 集群，你需要一个 <del> [kubeconfig 文件](/docs/zh/concepts/configuration/organize-cluster-access-kubeconfig/)， </del> <ins> [kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)， </ins> 该文件在 [kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh) 创建集群时，或成功部署一个 Miniube 集群时，均会自动生成。

Discussion:
404
The right URL is .
In , is wrong. [Suggested solution] Update the link to point . /triage accepted /kind bug /language zh
Hi Please change the title in English. We are sharing the repository and folks cannot easily understand purpose of this issue if you use your language in the title.
ok, thanks
Change:
``` To pull the image from the private registry, Kubernetes needs credentials. <del> The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`. </del> <ins> The `imagePullSecrets` field in the configuration file specifies that Kubernetes should get the credentials from a Secret named `regcred`. </ins> Create a Pod that uses your Secret, and verify that the Pod is running:

Discussion:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /assign
Change:
metadata: name: my-service annotations: <del> cloud.google.com/load-balancer-type: "Internal" </del> <ins> networking.gke.io/load-balancer-type: "Internal" </ins> [...] ```

Discussion:
<img width="1077" alt="Screenshot 2023-05-10 at 1 12 29 PM" src=""Please update the details as per (GKE 1.17 and later) (versions earlier than 1.17)
Page related to the issue: /retitle Update Internal Load Balancer annotation for GCP in accordance with Google Cloud Kubernetes Engine doc /language en
/triage accepted
/assign
Change:
<ins> --- title: "互动教程 - 配置 java 微服务" weight: 20 --- <!-- --- title: "Interactive Tutorial - Configuring a Java Microservice" weight: 20 --- --> <!DOCTYPE html> <html lang="en"> <body> <link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet"> <link href="/docs/tutorials/kubernetes-basics/public/css/overrides.css" rel="stylesheet"> <script src="https://katacoda.com/embed.js"></script> <div class="layout" id="top"> <main class="content katacoda-content"> <div class="katacoda"> <div class="katacoda__alert"> <!-- To interact with the Terminal, please use the desktop/tablet version --> 如需要与终端交互，请使用台式机/平板电脑版 </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/9" data-katacoda-color="326de6" data-katacoda-secondary="273d6d" data-katacoda-hideintro="false" data-katacoda-prompt="Kubernetes Bootcamp Terminal" style="height: 600px;"></div> </div> </main> </div> </body> </html> </ins>

Discussion:
Translate tutorials/configuration/configure-java-microservice/ into Chinese /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
Change:
by scheduler extenders, which handle the resource consumption and resource quota. You can specify the extended resources that are handled by scheduler extenders <del> in [scheduler policy configuration](/docs/reference/config-api/kube-scheduler-policy-config.v1/) </del> <ins> in [scheduler configuration](/docs/reference/config-api/kube-scheduler-config.v1beta3/) </ins> **Example:**

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 scheduler policy API was completely removed in 1.23. Proposed Solution: Revise concepts/configuration/manage-resources- to remove references to the scheduler policy API; Revise or even remove which is meaningless; Remove the kube-scheduler-policy- file from config API. Page to Update: See above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Related:
/sig scheduling /language en
/triage accepted
Change:
- [Hugo (Extended version)](https://gohugo.io/) - A container runtime, like [Docker](https://www.docker.com/). <ins> > [!NOTE] Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </ins> Before you start, install the dependencies. Clone the repository and navigate to the directory: ```bash

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: I tried to run the cloned website, which I forked on my Ubuntu Machine, but am getting error. I tried both running via docker and my running locally using Hugo but getting some issues in both. Following is the error while running via docker ! and this is while running locally via Hugo ! I also initialized modules by running the command: make module-init
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 support
I tried to analyze a bit. On first investigation, it seems like a valid issue. However, I do not know the root cause. I created a new Ubuntu VM, and tried to setup k/w from scratch. On running , the hugo command was stuck at: I then executed and managed to reproduce the issue you reported. (Note that at times this command gets stuck without an output as well). On my local machine, I have older versions of npm, hugo, go and docker and k/w builds fine. It could be related to one of the upgrades in the dependencies (most probably Hugo), however I cannot state for certain.
The issue is in the Hugo version. Upon changing the version, it worked perfectly. Thanks for your input. I think this issue should be raised.
Can you please mention the exact combination of versions (npm, Hugo, go, docker) that worked for you?
here, it is but I think the issue is with Hugo's version only.
Try whilst you have the latest main branch checked out. That works for me. You should find that you're using Hugo 0.121.2 (see ). If you want to test a Hugo upgrade, run before .
The instruction to install a specific Hugo extended version as defined in is mentioned in the section. However, I believe it would be helpful to move the instruction to the section.

This would prevent readers from inadvertently installing the latest Hugo extended version (currently v0.124.1) which is incompatible with k/w. I'll try to work on a PR for this.
/assign
Change:
--- title: Managing Resources for Containers content_template: templates/concept <del> weight: 20 </del> <ins> weight: 40 </ins> feature: title: Automatic bin packing description: >

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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
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
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!
Change:
{{< feature-state for_k8s_version="v1.19" state="stable" >}} {{< glossary_definition term_id="ingress" length="all" >}} <ins> {{< note >}} Ingress is frozen. New features are being added to the [Gateway API](/docs/concepts/services-networking/gateway/). {{< /note >}} </ins> <!-- body --> ## Terminology

Discussion:
This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new "Gateway API" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the "Ingress" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the "Service" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign
checkout the gateway API in the section and look out for the bugs
/triage accepted /priority important-longterm
How about adding a short link eg that redirects (302) to https://gateway- ?
I'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.
Also see
Change:
# i18n strings for the English (main) site. # 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 = "and" </ins> [caution] other = "Caution:"

Discussion:
When the following shortcode appears in a localized document... localized document displays English words such as: "Complete 1.24 and " Instances of the shortcode display English words in various localizations, such as: Is there a way to localize the languages these shortcodes display?
For instance, see
I have asked this question in the Hugo forum, here:
/assign
This is not a Hugo bug. is the file to localize.
partially fixes this issue. Each localization branch would need to merge PR and add corresponding entries to their files, such as: - -
Thanks, yes. I wasn't sure whom to ask, and generally try not to bother you with every question I have. The Hugo forum pointed us in the right direction, and quickly put together a PR solution.
Each localization branch would need to merge PR and add corresponding entries to their data/i18n/<lang/ files Once you PR merges, we should plan to add this topic to a localization meeting and post a message in the localization slack channel. We can also send an email, re post messages in slack for additional visibility. We should make sure the message includes all the steps needed o implement this and any urgency/priority around this change for the localization teams By a partial fix in your PR, do you mean that Localization teams will need to take additional steps to apply the changes to their localization, or are there additional file changes that need to be made?
Yes, exactly. Once this PR merges, I would do all the things you've suggested above or arrange with someone to do them. I'll create separate issues for each of the localization teams to update their branches as needed. This is not a breaking change, so there is no urgency.
I've tested to make sure this isn't a breaking change. If the file is missing the required entries, the page falls back and uses the entries from
/area localization
/triage accepted
Change:
### Migrating to the `systemd` driver in kubeadm managed clusters <del> Follow this [Migration guide](docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </del> <ins> Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver) </ins> if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters. ## Container runtimes

Discussion:
includes the deadlink:
/kind bug /triage accepted /language en
/sig cluster-lifecycle node i've LGTM on the pending PR.
/retitle container-runtime: migration guide points to a 404
this PR did not fix the problem: because it lacks a leading i will send a new one.
new fix is here:
Change:
该准入控制器为 Pod 设置默认的容忍度，在 5 分钟内容忍 `notready:NoExecute` 和 `unreachable:NoExecute` 污点。（如果 Pod 尚未容忍 `node.kubernetes.io/not-ready：NoExecute` 和 `node.alpha.kubernetes.io/unreachable：NoExecute` 污点的话） <del> ### DenyExecOnPrivileged {#denyexeconprivileged} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### DenyExecOnPrivileged {#denyexeconprivileged} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> <!-- This admission controller will intercept all requests to exec a command in a pod if that pod has a privileged container.

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:
<div class="row"> <div class="col-md-9"> <h2>Kubernetes Basics</h2> <del> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its containerized applications for yourself.</p> <p>Using the interactive tutorials, you can learn to:</p> </del> <ins> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and a tutorial for you to follow along.</p> <p>Using the tutorials, you can learn to:</p> </ins> <ul> <li>Deploy a containerized application on a cluster.</li> <li>Scale the deployment.</li>

Discussion:
In page , the first part describes that an online interative tutorial is included. But in fact, this tutorial was shutdown a few months ago. I think that may confuse some readers. !
/language en
Some replacement of words can fix this paragraph, but why katacoda/killercoda playgrounds are not used in these tutorial pages to make it interactive? /sig docs /kind feature
/assign
Seems like it's katacoda related.
Hi you don't need to translate anything. Just create a PR for english. (Optionally you can translate this if your know some other languages too. If you try to do so, raise a single PR per language.)
/assign
/kind bug /language en /remove-kind feature /triage accepted /priority important-longterm To discuss potential replacements for Katacoda (which has shut down), visit If anyone would like to support the Kubernetes project to set up or make use of a free replacement for Katacoda, you can: send financial to the Linux Foundation (very indirect support)
/assign
Change:
* One or more machines running Ubuntu 16.04+, Debian 9, CentOS 7, RHEL 7, Fedora 25/26 (best-effort) or HypriotOS v1.0.1+ * 1GB or more of RAM per machine (any less will leave little room for your apps) * Full network connectivity between all machines in the cluster (public or private network is fine) <del> * Unique MAC address and product_uuid for every node </del> <ins> * Unique hostname, MAC address, and product_uuid for every node </ins> * Certain ports are open on your machines. See the section below for more details * Swap disabled. You must disable swap in order for the kubelet to work properly. * Set `/proc/sys/net/bridge/bridge-nf-call-iptables` to `1` by running `sysctl net.bridge.bridge-nf-call-iptables=1`

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: kubectl get nodes seems to show the master is NotReady when a node is with the same hostname Proposed Solution: Make a unique hostname a requirement for every node just like MAC address and product_uuid. Possible the code should reflect that too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.8.1 <!--Additional Information:--
Thanks for the report If you think the code should be doing something different, please open a bug report for that code - either at , or in this case perhaps at I'll keep this report open to reflect the need in the documentation.
Change:
An example NetworkPolicy might look like this: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 - namespaceSelector: matchLabels: project: myproject - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 5978 ``` </del> <ins> {{< codenew file="service/networking/networkpolicy.yaml" >}} </ins> {{< note >}} POSTing this to the API server for your cluster will have no effect unless your chosen networking solution supports network policy.

Discussion:
While working through the Killer Shell scenario for NetworkPolicies to prep for my CKA, I used the example but it failed validation. When I looked at their solution it had one tiny difference, they had a - in front of "ports:" and you guys didn't. Based on the reference docs it appears ports does expect an array which would mean that you are missing the hyphen. docs: solution from
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
The indentation of list items may be the source of confusion. Once you indent all list items under a given key, the parent element of the 'ports' attribute becomes more evident. The example on the website is correct. I'm not sure about the solution from If you put as the first key of a list item object, if will carry the bar for that list item, if is not the the first key, you will indent it rather than adding another before it. Anyway, I'm fixing the example in hope things become clearer for readers.
Change:
<ins> --- title: Serviceトポロジーを有効にする content_type: task --- <!-- overview --> このページでは、Kubernetes上でServiceトポロジーを有効にする方法の概要について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- steps --> ## はじめに *Serviceトポロジー*は、クラスターのノードのトポロジーに基づいてトラフィックをルーティングできるようにする機能です。たとえば、あるServiceのトラフィックに対して、できるだけ同じノードや同じアベイラビリティゾーン上にあるエンドポイントを優先してルーティングするように指定できます。 ## 前提 トポロジーを考慮したServiceのルーティングを有効にするには、以下の前提を満たしている必要があります。 * Kubernetesバージョン1.17以降である * {{< glossary_tooltip text="Kube-proxy" term_id="kube-proxy" >}}がiptableモードまたはIPVSモードで稼働している * [Endpoint Slice](/docs/concepts/services-networking/endpoint-slices/)を有効にしている ## Serviceトポロジーを有効にする {{< feature-state for_k8s_version="v1.17" state="alpha" >}} Serviceトポロジーを有効にするには、すべてのKubernetesコンポーネントで`ServiceTopology`と`EndpointSlice`フィーチャーゲートを有効にする必要があります。 ``` --feature-gates="ServiceTopology=true,EndpointSlice=true" ``` ## {{% heading "whatsnext" %}} * [Serviceトポロジー](/ja/docs/concepts/services-networking/service-topology)のコンセプトについて読む * [Endpoint Slice](/docs/concepts/services-networking/endpoint-slices)について読む * [サービスとアプリケーションの接続](/ja/docs/concepts/services-networking/connect-applications-service/)を読む </ins>

Discussion:
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
/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
Change:
<del> Subproject commit 0f9c38b8daae932518bee269de2768395d2a2dc2 </del> <ins> Subproject commit f6a1870918520c83872fc07943a67a1d9d2a998c </ins>

Discussion:
Look into evaluating how we can make building the site take less memory / cpu. As has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build). This is all good though, it means we are adding content and localizations. Look into ways to reduce build time. A few options come to mind: Can we remove a large chunk of unused content? Can we build only a small subset of docs (easily and portable to the various localizations)? Are there any optimizations in hugo itself? There should be a way to reduce the amount of resources required to build . Considering there isn't a clear solution, I won't mark as good-first-issue. /sig docs /triage accepted
Idea: run the build localization-by-localization. I don't know if Hugo supports this but if it might let us run 14 shorter builds (potentially in parallel) rather than 1 long one. Idea: look for image resize options at build time. If reasonable to do so, replace the source image with what it gets resized to.
This might be an area where we could look for resources from CNCF to help with it - especially if the fix is applicable across multiple CNCF projects.