jiebi/CodeConvo huggingface dataset:
Change:
<!-- overview --> <del> Kubernetes runs your workload by placing containers into Pods to run on _Nodes_. </del> <ins> Kubernetes runs your {{< glossary_tooltip text="workload" term_id="workload" >}} by placing containers into Pods to run on _Nodes_. </ins> A node may be a virtual or physical machine, depending on the cluster. Each node is managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}

Discussion:
This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :
/sig docs / language en /assign
If triage is accepted, i would be happy to contribute on it. PTAL.
/language en Fixed here .
/triage accepted
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: volume-test spec: containers: - name: container-test image: busybox volumeMounts: - name: all-in-one mountPath: "/projected-volume" readOnly: true volumes: - name: all-in-one projected: sources: - secret: name: mysecret items: - key: username path: my-group/my-username - secret: name: mysecret2 items: - key: password path: my-group/my-password mode: 511 </ins>

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
```shell # This assumes you are using filesystem-hosted static Pod configuration <del> # Run these commands on the node where the kubelet is running </del> <ins> # Run these commands on the node where the container is running </ins> # mv /etc/kubernetes/manifests/static-web.yaml /tmp sleep 20

Discussion:
This is a Bug Report There is a section named in page, we should add log info observation for static pod as well in the page for user benefits. Also there is already a page with a section dedicated to it. I think that will be really useful. Problem: No log observation method mentioned in the Observe static pod behaviour section Proposed Solution: Add a reference link directing to in the aforementioned section 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
/sig docs /language en
/assign
Would we also want to document how to work out which container ID is the right one to check?
Hi , This section might be explaining subtly how to see your container. would you like a detailed version of how this can be defined?
Hi , I already started working on this issue yesterday, is it okay if I carry forward or you want to take this up?
is a glimpse of what i in the static-pod docs Also there can be more addition to the reference section i.e. section. I some links that can be useful for understanding more about static pod.
/unassign
Change:
1. Tải về phiên bản mới nhất với câu lệnh: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/`curl -LS https://dl.k8s.io/release/stable.txt`/bin/linux/amd64/kubectl </ins> ``` <del> Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` trong câu lệnh với một phiên bản cụ thể. </del> <ins> Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -LS https://dl.k8s.io/release/stable.txt)` trong câu lệnh với một phiên bản cụ thể. </ins> Ví dụ như, để tải về phiên bản {{< param "fullversion" >}} trên Linux, hãy nhập như sau: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </ins> ``` 2. Tạo kubectl binary thực thi.

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 are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
* `initialDelaySeconds`: Number of seconds after the container has started before startup, liveness or readiness probes are initiated. If a startup  probe is defined, liveness and <del> readiness probe delays do not begin until the startup probe has succeeded. Defaults to 0 seconds. Minimum value is 0. </del> <ins> readiness probe delays do not begin until the startup probe has succeeded. If the value of `periodSeconds` is greater than `initialDelaySeconds` then the `initialDelaySeconds` would be ignored. Defaults to 0 seconds. Minimum value is 0. </ins> * `periodSeconds`: How often (in seconds) to perform the probe. Default to 10 seconds. The minimum value is 1. * `timeoutSeconds`: Number of seconds after which the probe times out.

Discussion:
This is a Bug Report Problem: The intial definiton given in doesn't describe that if the first probe time will be = . For example: The pod will be marked as after 60s, (tested in k8s v1.22.10). Moreover, the given if i read this code correctly, then the check is done for and the check for is done after assuming that value of Proposed Solution: Allign code and the documentation. Page to Update:
/sig docs /language en
/assign
I did tested this on the k8s 1.27 and it's still same.
I believe this is a corner case. Why do you set initialDelaySeconds to be shorter than perdioSeconds in the first place? I'm not objecting the clarification, BTW. What I am wondering is if there is a real case people will do this.
Okay. I get it now. The example manifest has a problem to fix. Thanks for raising up this.
/triage accepted
thanks :)
Change:
--- <del> title: "Scheduling and Eviction" </del> <ins> title: "Scheduling, Preemption and Eviction" </ins> weight: 90 description: > <del> In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that the kubelet can run them. Eviction is the process of proactively failing one or more Pods on resource-starved Nodes. </del> <ins> In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that the kubelet can run them. Preemption is the process of terminating Pods with lower Priority so that Pods with higher Priority can schedule on Nodes. Eviction is the process of proactively terminating one or more Pods on resource-starved Nodes. </ins> ---

Discussion:
Suggestion from in /sig docs /assign 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
I think this makes sense. I'd like to keep the URL but change the display title to Scheduling, Preemption and Eviction.
sgtm
Change:
mkdir -p /opt/bin ARCH="amd64" cd /opt/bin <del> curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </del> <ins> curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </ins> chmod +x {kubeadm,kubelet,kubectl} RELEASE_VERSION="v0.2.7"

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 are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
[release_full_details_initial_text] other = "Complete" <ins> [release_information_navbar] other = "Release Information" </ins> [release_minor_version] other = "Minor Version"

Discussion:
You can only get to the localized version of the page by going to the English version, and then clicking on the language dropdown to find a translation. If you are already on a localized version of the site, and the page exists in the selected language, it redirects you to the English version. See this comment for more info: Originally posted by in /area web-development
/area localization
/triage accepted
/priority important-longterm
/assign
Change:
</tr> <tr> <ins> <td colspan="2">--skip_headers</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true, avoid header prefixes in the log messages</p></td> </tr> <tr> <td colspan="2">--skip_log_headers</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true, avoid headers when opening log files</p></td> </tr> <tr> <td colspan="2">--stderrthreshold int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 2</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>logs at or above this threshold go to stderr</p></td> </tr> <tr> </ins> <td colspan="2">--udp-timeout duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 250ms</td> </tr> <tr>

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
<tr> <td style="white-space: nowrap">HostProcess</td> <td> <del> <p>Windows pods offer the ability to run <a href="/docs/tasks/configure-pod-container/create-hostprocess-pod">HostProcess containers</a> which enables privileged access to the Windows node. Privileged access to the host is disallowed in the baseline policy. {{< feature-state for_k8s_version="v1.23" state="beta" >}}</p> </del> <ins> <p>Windows pods offer the ability to run <a href="/docs/tasks/configure-pod-container/create-hostprocess-pod">HostProcess containers</a> which enables privileged access to the Windows node. Privileged access to the host is disallowed in the baseline policy. {{< feature-state for_k8s_version="v1.26" state="stable" >}}</p> </ins> <p><strong>Restricted Fields</strong></p> <ul> <li><code>spec.securityContext.windowsOptions.hostProcess</code></li>

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: states However, this feature is in fact GA in v1.26 and cannot be disabled, so we should tweak that wording. Proposed Solution: Tweak that wording. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 26 (unreleased at time issue was filed) Additional Information: /sig node /sig windows If making changes before the v1.26 release, file a PR against the dev-1.26 branch.
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
PR could have included this update.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten
Change:
/docs/reference/deprecation-policy/     /docs/reference/using-api/deprecation-policy/ 301 <ins> /docs/reference/generated/kubectl/kubectl-commands/     /docs/reference/kubectl/ 301 </ins> /docs/reference/generated/cloud-controller-manager/     /docs/reference/command-line-tools-reference/cloud-controller-manager/ 301 /docs/reference/generated/kubelet/     /docs/reference/command-line-tools-reference/kubelet/ 301 /docs/reference/generated/kube-apiserver/     /docs/reference/command-line-tools-reference/kube-apiserver/ 301

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 Replace with a redirect to Why is this needed We the generator for Comments /language en /priority backlog /lifecycle frozen we should definitely clean this up one day
/retitle Drop legacy kubectl reference page
/triage accepted
I want to try to help with this. /assign
a redirect; we should also delete the page we're redirecting people away from.
Change:
<ins> apiVersion: v1 kind: Service metadata: name: my-service labels: app: MyApp spec: ipFamily: IPv6 type: LoadBalancer selector: app: MyApp ports: - protocol: TCP port: 80 targetPort: 9376 </ins>  No newline at end of file

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
Change:
The Dashboard UI is not deployed by default. To deploy it, run the following command: ``` <del> kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.5.0/aio/deploy/recommended.yaml </del> <ins> kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.6.1/aio/deploy/recommended.yaml </ins> ``` ## Accessing the Dashboard UI

Discussion:
Please update page, it should be instead of
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:
<ins> --- title: 新しいコンテンツの貢献 weight: 20 --- </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
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:
labels: app: cassandra spec: <del> terminationGracePeriodSeconds: 1800 </del> <ins> terminationGracePeriodSeconds: 500 </ins> containers: - name: cassandra image: gcr.io/google-samples/cassandra:v13

Discussion:
When running this command: The grace period it was going to sleep was 1800s (30m), so after all resources were deleted (about 5-6s), I hit Ctrl-C, then manually ran the line after the sleep: kubectl delete persistentvolumeclaim -l app=cassandra Recommend adding a note to avoid having the student wait 30m for a command to finish that might only take a few seconds.
Related page: /language en
I think we can improve the advice, or change the grace period to be quite a bit shorter. Not sure which is better.
/triage accepted either way
/retitle [Unclear] example: Deploying Cassandra with a StatefulSet
I have tried to reproduce the issue with a grace period of 300 seconds. And I observed that all my related resources were deleted in under 10 seconds. It will be better if we reduce the to some shorter value like or .
I would like to work on this issue. /assign /sig apps /sig storage
/assign
Change:
## kind [`kind`](https://kind.sigs.k8s.io/) lets you run Kubernetes on <del> your local computer. This tool requires that you have [Docker](https://docs.docker.com/get-docker/) installed and configured. </del> <ins> your local computer. This tool requires that you have either [Docker](https://www.docker.com/) or [Podman](https://podman.io/) installed. </ins> The kind [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/) page shows you what you need to do to get up and running with kind.

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: states that kind requires Docker. This isn't right as I understand it; you can actually use with Podman, even if you don't have Docker installed at all. Proposed Solution: check what's right update the docs to match the truth Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
/assign
according to my knowledge we can use Buildah for managing container images and Podman for managing containers if someone is looking for an alternative to docker. But these can be used only on Linux, so for windows or mac a Linux VM will be used to run these and I am thinking to put this in a note. Your suggestions?
(yes) Also see Kubernetes itself doesn't require any of the listed tools (Podman, Docker, Buildah); for example, you might use CRI-O and runsc and the kubelet, but no Docker Engine.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
/triage accepted
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
Podman now has documentation on how to work with the and plug-ins: https://podman-
/assign
Change:
--> 可以组合使用 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

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