jiebi/CodeConvo huggingface dataset:
Change:
Last paragraph, last code example should be in the first example the result is the in the second now it is
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
Page related to issue: /language en
/kind bug
/assign

Discussion:
kubectl get pods -o jsonpath='{.items[?(@.metadata.name=~/^test$/)].metadata.name}' # The following command achieves the desired result <del> kubectl get pods -o json | jq -r '.items[] | select(.metadata.name | test("test-")).spec.containers[].image' </del> <ins> kubectl get pods -o json | jq -r '.items[] | select(.metadata.name | test("test-")).metadata.name' </ins> ``` {{< /note >}}
Change:
<brConsider using the English-language version of the link for Huawei Cloud: The current link is Chinese.
Page related to issue: /language en
/assign
/kind bug /good-first-issue /triage accepted
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 : /kind bug /good-first-issue /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
Anyone is welcome to work on this. it sounds like you plan to open a pull request? (other contributors: it's polite to try to liaise with ahead of starting work)
, yes i would like to work on this and going to open a pull request.
/assign
Hey Please assign this issue to me, I am a new contributor
Anyone is welcome to work on this. (it's polite to try to liaise with contributors who've previously expressed an interest in working on this, and ideally to consider collaborating)
, Kindly next time liaise with previous assigned user first before you assign youself and start work. This will show some courtesy.

Discussion:
Alibaba Cloud | https://www.alibabacloud.com/trust-center | Amazon Web Services | https://aws.amazon.com/security | Google Cloud Platform | https://cloud.google.com/security | <del> Huawei Cloud | https://www.huaweicloud.com/securecenter/overallsafety | </del> <ins> Huawei Cloud | https://www.huaweicloud.com/intl/en-us/securecenter/overallsafety | </ins> IBM Cloud | https://www.ibm.com/cloud/security | Microsoft Azure | https://docs.microsoft.com/en-us/azure/security/azure-security | Oracle Cloud Infrastructure | https://www.oracle.com/security |
Change:
<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

Discussion:
## 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
Change:
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

Discussion:
- 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 的数量与

--> 如果你希望新来的 Pod 均匀分布在现有的可用区域，则可以按如下设置其清单： <del> {{< codenew file="pods/topology-spread-constraints/one-constraint.yaml" >}} </del> <ins> {{% code file="pods/topology-spread-constraints/one-constraint.yaml" %}} </ins> <!-- From that manifest, `topologyKey: zone` implies the even distribution will only be applied

--> 可以组合使用 2 个拓扑分布约束来控制 Pod 在节点和可用区两个维度上的分布： <del> {{< codenew file="pods/topology-spread-constraints/two-constraints.yaml" >}} </del> <ins> {{% code file="pods/topology-spread-constraints/two-constraints.yaml" %}} </ins> <!-- In this case, to match the first constraint, the incoming Pod can only be placed onto

以便将 Pod `mypod` 放置在可用区 `B` 上，而不是可用区 `C` 上。 同样，Kubernetes 也会一样处理 `spec.nodeSelector`。 <del> {{< codenew file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" >}} </del> <ins> {{% code file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" %}} </ins> <!-- ## Implicit conventions
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The release blog has this section: Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 a.m. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the on the CNCF Online Programs site. This currently has a broken link to the event page. Proposed Solution: Once the event is live on CNCF we should fix this in the blog or at least remove the link until then. Page to Update: /cc
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
Thanks confirmed it is broken talking with CNCF now regarding it. Will do a PR to remove for now
/assign

Discussion:
## Upcoming Release Webinar <del> Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 a.m. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](https://community.cncf.io/events/details/cncf-cncf-online-programs-presents-cncf-live-webinar-kubernetes-v128-release/) on the CNCF Online Programs site. </del> <ins> Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 A.M. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](https://community.cncf.io/events/) on the CNCF Online Programs site. </ins> ## Get Involved
Change:
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 the docs for server-side apply to mention that for a does not work well with - Update the docs for Secrets to mention that for a does not work well with Why is this needed etc Comments /language en /kind feature /triage accepted /priority backlog
See for more detail:
/assign I would raise a PR for fixing this issue.
This is only partially resolved by ...
Hi, , What do you mean "partially resolved"? I checked the list and only found 2 references, which have been fixed by Or anything else I missed?
I don't think we have address all cases. Am I missing anything?
Thanks . I am afraid that you are right. I will open another PR for fixing the other 2 links with hints.

Discussion:
`*`, `=`, and `!` in your strings. If you don't, your shell will interpret these characters. <ins> {{< note >}} The `stringData` field for a Secret does not work well with server-side apply. {{< /note >}} </ins> ### Use source files 1. Store the credentials in files:

literal values. For example, the following instructions create a Kustomization file for the username `admin` and the password `1f2d1e2e67df`. <ins> {{< note >}} The `stringData` field for a Secret does not work well with server-side apply. {{< /note >}} </ins> ### Create the Kustomization file {{< tabs name="Secret data" >}}
Change:
to /assign
Page related to issue: /language en
/retitle Update hyperlinks in 'Amadeus Case Study' page to utilize HTTPS instead of HTTP
Which is the page we should fix?
/triage accepted

Discussion:
<h2>Solution</h2> <del> <p>Mountain has been overseeing the company's migration to <a href="http://kubernetes.io/">Kubernetes</a>, using <a href="https://www.openshift.org/">OpenShift</a> Container Platform, <a href="https://www.redhat.com/en">Red Hat</a>'s enterprise container platform.</p> </del> <ins> <p>Mountain has been overseeing the company's migration to <a href="https://kubernetes.io/">Kubernetes</a>, using <a href="https://www.openshift.org/">OpenShift</a> Container Platform, <a href="https://www.redhat.com/en">Red Hat</a>'s enterprise container platform.</p> </ins> <h2>Impact</h2>

<p>While mainly a C++ and Java shop, Amadeus also wanted to be able to adopt new technologies more easily. Some of its developers had started using languages like <a href="https://www.python.org/">Python</a> and databases like <a href="https://www.couchbase.com/">Couchbase</a>, but Mountain wanted still more options, he says, "in order to better adapt our technical solutions to the products we offer, and open up entirely new possibilities to our developers." Working with recent technologies and cool new things would also make it easier to attract new talent.</p> <del> <p>All of those needs led Mountain and his team on a search for a new platform. "We did a set of studies and proofs of concept over a fairly short period, and we considered many technologies," he says. "In the end, we were left with three choices: build everything on premise, build on top of <a href="http://kubernetes.io/">Kubernetes</a> whatever happens to be missing from our point of view, or go with <a href="https://www.openshift.com/">OpenShift</a> and build whatever remains there."</p> </del> <ins> <p>All of those needs led Mountain and his team on a search for a new platform. "We did a set of studies and proofs of concept over a fairly short period, and we considered many technologies," he says. "In the end, we were left with three choices: build everything on premise, build on top of <a href="https://kubernetes.io/">Kubernetes</a> whatever happens to be missing from our point of view, or go with <a href="https://www.openshift.com/">OpenShift</a> and build whatever remains there."</p> </ins> <p>The team decided against building everything themselves—though they'd done that sort of thing in the past—because "people were already inventing things that looked good," says Mountain.</p>
Change:
According to the documentation, the certificate requires , but how can it be needed if etcd doesn't take this into account? Perhaps should be removed for the certificate and then I can create an issue on the kubeadm repo like like I created earlier.
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
Page related to issue: /language en
/retitle Inconsistency in doc for kube-apiserver-etcd-client Certificate requirement /sig cluster-lifecycle
/sig api-machinery auth
+1 PRs welcome thanks
sorry but I don't understand what do you mean — just agreement or confirmation about what should be done? :) You seem to confirm that is indeed not required in the certificate, but I'm not sure because there are still no updates in the issue and the documentation is still not changed. So, I can't figure out if I should create an issue in the kubeadm repository.
yes, you can log the issue in k/kubeadm. in terms of updating the docs, i said "prs welcome", thus if you l'd like to help us you can send the docs change / pull request.

Discussion:
| kube-etcd                     | etcd-ca                   |                | server, client   | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` | | kube-etcd-peer                | etcd-ca                   |                | server, client   | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` | | kube-etcd-healthcheck-client  | etcd-ca                   |                | client           |                                                     | <del> | kube-apiserver-etcd-client    | etcd-ca                   | system:masters | client           |                                                     | </del> <ins> | kube-apiserver-etcd-client    | etcd-ca                   |                | client           |                                                     | </ins> | kube-apiserver                | kubernetes-ca             |                | server           | `<hostname>`, `<Host_IP>`, `<advertise_IP>`, `[1]`  | | kube-apiserver-kubelet-client | kubernetes-ca             | system:masters | client           |                                                     | | front-proxy-client            | kubernetes-front-proxy-ca |                | client           |                                                     |
Change:
According to the "DisableAcceleratorUsageMetrics" feature gate has already been removed, so the section "Disable accelerator metrics" needs to be updated.
/sig node instrumentation /language en /kind bug /help /triage accepted
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 : /sig node instrumentation /language en /kind bug /help /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
/assign

Discussion:
`1.12`, you should set hidden metrics via command line: `--show-hidden-metrics=1.12` and remember to remove this metric dependency before upgrading to `1.14` <del> ## Disable accelerator metrics The kubelet collects accelerator metrics through cAdvisor. To collect these metrics, for accelerators like NVIDIA GPUs, kubelet held an open handle on the driver. This meant that in order to perform infrastructure changes (for example, updating the driver), a cluster administrator needed to stop the kubelet agent. The responsibility for collecting accelerator metrics now belongs to the vendor rather than the kubelet. Vendors must provide a container that collects metrics and exposes them to the metrics service (for example, Prometheus). The [`DisableAcceleratorUsageMetrics` feature gate](/docs/reference/command-line-tools-reference/feature-gates/) disables metrics collected by the kubelet, with a [timeline for enabling this feature by default](https://github.com/kubernetes/enhancements/tree/411e51027db842355bd489691af897afc1a41a5e/keps/sig-node/1867-disable-accelerator-usage-metrics#graduation-criteria). </del> ## Component metrics ### kube-controller-manager metrics
Change:
This sentence is unclear because of the word "link", which calls into question the early notion of data flows between the Kubernetes components, container runtime and OpenTelemetry collector. You're trying to rethink how data flows and where traces might be linked. Connected [to kubelet?] container runtimes like CRI-O and containerd can link [how?] the traces [traces from Kubernetes?] to their exported spans [exported to whom?] to provide additional context of information. Does this mean that if tracing is enabled for kubelet, it forces the container runtime to send its traces to kubelet? But how can a container runtime link its traces with external traces without receiving them, since kubelet is the initiator, not the container runtime? Or are the kubelet and container traces independently sent to the trace backend (using collectors) where they can be linked somehow? So many assumptions, please add clarification. UPDATE: I was wrong about the initiator, according to I think a container runtime might be it.
/language en
/sig-docs /area docs /retitle Unclear documentation on system traces
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig-docs /area docs /retitle Unclear documentation on system traces 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
Re-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /sig-docs /area docs /retitle Unclear documentation on system traces 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
/sig docs
/retitle Unclear documentation about trace linking between Kubernetes components, container runtime and OpenTelemetry collector
/sig node /sig instrumentation
/priority backlog /triage accepted If this rots out, I recommend not removing the staleness marker. We may not have enough volunteers to cover every improvement. Help is, of course, very welcome!
/triage accepted /assign

Discussion:
The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from the garbage collection, pod synchronization routine as well as every gRPC <del> method. Connected container runtimes like CRI-O and containerd can link the traces to their exported spans to provide additional context of information. </del> <ins> method. The kubelet propagates trace context with gRPC requests so that container runtimes with trace instrumentation, such as CRI-O and containerd, can associate their exported spans with the trace context from the kubelet. The resulting traces will have parent-child links between kubelet and container runtime spans, providing helpful context when debugging node issues. </ins> Please note that exporting spans always comes with a small performance overhead on the networking and CPU side, depending on the overall configuration of the
Change:
The "KubeletPodResourcesDynamiceResources" feature gate is not in the feature gates tables ( or ), it's only on the . I think it should be 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
/language en
is a typo, notice the extra before the last word. PRs welcome.
I have raised PR to fix the typo
I should have mentioned the page where I saw the typo — there are still two typos there.
These typos should be fixed now after merge of PR

Discussion:
- `KubeletPodResourcesGetAllocatable`: Enable the kubelet's pod resources `GetAllocatableResources` functionality. This API augments the [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) <del> - `KubeletPodResourcesDynamiceResources`: Extend the kubelet's pod resources gRPC endpoint to </del> <ins> - `KubeletPodResourcesDynamicResources`: Extend the kubelet's pod resources gRPC endpoint to </ins> to include resources allocated in `ResourceClaims` via `DynamicResourceAllocation` API. See [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) for more details. with informations about the allocatable resources, enabling clients to properly
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: "Home" button at footer is linked to docs home page instead of K8s site home page Proposed Solution: Either that button should be linked to K8s site home page or that button should be renamed to "Documentation" instead of "Home" ! <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Thanks I'd change it to read “Documentation”. /priority backlog /help /triage accepted /language en
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 : Thanks I'd change it to read “Documentation”. /priority backlog /help /triage accepted /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

Discussion:
cid: docsHome layout: docsportal_home class: gridPage gridPageHome <del> linkTitle: "Home" </del> <ins> linkTitle: "Documentation" </ins> main_menu: true weight: 10 hide_feedback: true