jiebi/CodeConvo huggingface dataset:
Change:
REVISION  CHANGE-CAUSE 1   <none> ``` <del> * Get the rollout status to ensure that the Deployment is updated successfully: </del> <ins> * Get the rollout status to verify that the existing ReplicaSet has not changed: </ins> ```shell kubectl get rs ```

Discussion:
suggests: Do changes, then The output is equivalent to the previous run of . I do not see, how this output can confirm, that the Deployment was updated.
Welcome and thanks for contributing your first issue here! This sentence does seem confusing to me. I will improve it. /triage accepted /kind bug /assign
/sig apps
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
Change:
* [Borg](https://research.google.com/pubs/pub43438.html) * [Marathon](https://mesosphere.github.io/marathon/docs/rest-api.html) * [Omega](https://research.google/pubs/pub41684/) <del> * [Tupperware](https://engineering.fb.com/data-center-engineering/tupperware/). </del>  No newline at end of file <ins> * [Tupperware](https://engineering.fb.com/data-center-engineering/tupperware/). </ins>

Discussion:
Hello! in the Pod OS section of this page, it says: ... **Editing for clarity: Forgive me if I'm misunderstanding, but kube-scheduler should pick a node for the Pod to run on, and not the other way around? The way the above sentence is worded sounds like kube-scheduler picks Pods to run nodes.
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
these two statements donot contradict as first one say that selecton of node by kube-scheduler is not based on . kube-scheduler pick a node of run based on various other creterias but not consider frield
I think you might correct the text might need some correction.
Let me see if I can help with this. /assign
Change:
- [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md#runtimeclass-scheduling) - Read about the [Pod Overhead](/docs/concepts/scheduling-eviction/pod-overhead/) concept - [PodOverhead Feature Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md)

Discussion:
RuntimeClass feature gate is GA in 1.20. According to , a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.
triage/accepted
/language en
/triage accepted
/assign
Change:
{{- $single := .Get "single" | default "false" -}} <ins> {{- $vendor_message := .Get "vendor" | default "false" -}} </ins> <div class="alert alert-secondary callout third-party-content" role="alert"> {{- if not (eq $single "true" ) -}} <strong>{{ T "note" | safeHTML }}</strong> <del> {{ T "thirdparty_message" | safeHTML }} </del> <ins> {{- if (eq $vendor_message "true" ) -}} {{ T "thirdparty_message_vendor" | safeHTML }} {{- else -}} {{ T "thirdparty_message" | safeHTML }} {{- end -}} </ins> {{- else -}} {{ T "thirdparty_message_single_item" | safeHTML }} {{- end -}}

Discussion:
This is a Refactor request <!-- 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 overview page at is a bit out of date: no reference to I'm not convinced that the “Four Cs of cloud native security” model is useful for readers to learn Does not align with other CNCF documents, such as Proposed Solution: Either: remove outright migrate content from into several destinations (keep this brief but on-point) &hellip;and then redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig docs /sig security /language en
If we keep the link to then we should update it to be as this is the English docs.
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
Also see
/assign
I'd appreciate a (fresh) review on .
Change:
You can [download Kubernetes](/releases/download/) to deploy a Kubernetes cluster on a local machine, into the cloud, or for your own datacenter. <del> Several [Kubernetes components](/docs/concepts/overview/components/) such as `kube-apiserver` or `kube-proxy` can also be </del> <ins> Several [Kubernetes components](/docs/concepts/overview/components/) such as {{< glossary_tooltip text="kube-apiserver" term_id="kube-apiserver" >}} or {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} can also be </ins> deployed as [container images](/releases/download/#container-images) within the cluster. It is **recommended** to run Kubernetes components as container images wherever

Discussion:
What would you like to be Under page, provide hyperlink for Why is this needed Adding the hyperlink will helps the readers to know about kube-apiserver. Comments /sig docs /language en /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
/assign
/remove-good-first-issue
/sig docs
I'd use a .
shall i proceed with glossary tooltip?
Change:
## {{% heading "whatsnext" %}} <del> * [attaching handlers to Container lifecycle events](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </del> <ins> * [コンテナライフサイクルイベントへのハンドラー紐付け](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </ins> <del> * [Configure Liveness, Readiness and Startup Probes](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)のハンズオンをやってみる </del> <ins> * [Liveness Probe、Readiness ProbeおよびStartup Probeを使用する](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)のハンズオンをやってみる </ins> <del> * [Container lifecycle hooks](/ja/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </del> <ins> * [コンテナライフサイクルフック](/ja/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </ins> <del> * APIのPod/コンテナステータスの詳細情報は[PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core)および[ContainerStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerstatus-v1-core)を参照してください </del> <ins> * APIにおけるPodとコンテナのステータスに関する詳細情報は、Podの[`.status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus)に書かれているAPIリファレンスドキュメントを参照してください。 </ins>

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted
Change:
Kubernetesプロジェクトでは、最新の3つのマイナーリリースについてリリースブランチを管理しています。 <del> セキュリティフィックスを含む適用可能な修正は、重大度や実行可能性によってはこれら3つのリリースブランチにバックポートされることもあります。パッチリリースは、定期的または必要に応じてこれらのブランチから分岐されます。[パッチリリースマネージャー](https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/patch-release-manager/README.md#release-timing)がこれを決定しています。パッチリリースマネージャーは[各リリースのリリースチーム](https://github.com/kubernetes/sig-release/tree/master/releases/)のメンバーです。 </del> <ins> セキュリティフィックスを含む適用可能な修正は、重大度や実行可能性によってはこれら3つのリリースブランチにバックポートされることもあります。パッチリリースは、[定期的](https://git.k8s.io/sig-release/releases/patch-releases.md#cadence)または必要に応じてこれらのブランチから分岐されます。[リリースマネージャー](https://git.k8s.io/sig-release/release-managers.md)グループがこれを決定しています。 </ins> <del> マイナーリリースは約3ヶ月ごとに行われるため、それぞれのリリースブランチは約9ヶ月間メンテナンスされます。 </del> <ins> 詳細は、Kubernetes[パッチリリース](https://git.k8s.io/sig-release/releases/patch-releases.md)ページを参照してください。 </ins> ## サポートされるバージョンの差異

Discussion:
Follow PR
/language ja
/assign
We can close this issue by
/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:
`replace`        | `kubectl replace -f FILENAME` |  基于文件或标准输入替换资源。 `rollout`    | `kubectl rollout SUBCOMMAND [options]` | 管理资源的上线。有效的资源类型包括：Deployment、 DaemonSet 和 StatefulSet。 `run`        | <code>kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server &#124; client &#124; none] [--overrides=inline-json] [flags]</code> | 在集群上运行指定的镜像。 <del> <!-- `scale`        | <code>kubectl scale (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags]</code> | Update the size of the specified replication controller. `set`    | `kubectl set SUBCOMMAND [options]` | Configure application resources. `taint`    | `kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]` | Update the taints on one or more nodes. `top`    | `kubectl top [flags] [options]` | Display Resource (CPU/Memory/Storage) usage. `uncordon`    | `kubectl uncordon NODE [options]` | Mark node as schedulable. `version`        | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server. `wait`    | <code>kubectl wait ([-f FILENAME] &#124; resource.group/resource.name &#124; resource.group [(-l label &#124; --all)]) [--for=delete&#124;--for condition=available] [options]</code> | Experimental: Wait for a specific condition on one or many resources. --> </del> `scale`        | <code>kubectl scale (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags]</code> | 更新指定副本控制器的大小。 `set`    | `kubectl set SUBCOMMAND [options]` | 配置应用资源。 `taint`    | `kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]` | 更新一个或多个节点上的污点。

Discussion:
web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted
Change:
kubectl delete deployment hello-node ``` <del> (オプション)Minikubeの仮想マシン(VM)を停止します: </del> <ins> (オプション)minikubeの仮想マシン(VM)を停止します: </ins> ```shell minikube stop ``` <del> (オプション)MinikubeのVMを削除します: </del> <ins> (オプション)minikubeのVMを削除します: </ins> ```shell minikube delete

Discussion:
This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Change occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted
Change:
role: db ingress: - from: <del> podSelector: matchLabels: role: frontend </del> <ins> - podSelector: matchLabels: role: frontend </ins> ports: - protocol: tcp port: 6379

Discussion:
When I try creating the example given in that page, I get this error: Indeed, after I change the value of from a map to a list containing that map, the create succeeds. Here is the corrected source:
Change:
## コンテナのステータス {#container-states} <del> Pod全体の[フェーズ](#pod-phase)と同様に、KubernetesはPod内の各コンテナの状態を追跡します。[container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/)を使用して、コンテナのライフサイクルの特定のポイントで実行するイベントをトリガーできます。 </del> <ins> Pod全体の[フェーズ](#pod-phase)と同様に、KubernetesはPod内の各コンテナの状態を追跡します。[container lifecycle hooks](/ja/docs/concepts/containers/container-lifecycle-hooks/)を使用して、コンテナのライフサイクルの特定のポイントで実行するイベントをトリガーできます。 </ins> Podが{{< glossary_tooltip text="scheduler" term_id="kube-scheduler" >}}によってNodeに割り当てられると、kubeletは{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}を使用してコンテナの作成を開始します。コンテナの状態は`Waiting`、`Running`または`Terminated`の3ついずれかです。

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update some links and fix some expressions. Why is this needed Some of the links have already been translated Also, some expressions were not official. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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:
This command checks that your cluster can be upgraded, and fetches the versions you can upgrade to. <del> {{< note >}} `kubeadm upgrade` also automatically renews the certificates that it manages on this node. To opt-out of certificate renewal the flag `--certificate-renewal=false` can be used. For more information see the [certificate management guide](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs). {{</ note >}} </del> <ins> {{< note >}} `kubeadm upgrade` also automatically renews the certificates that it manages on this node. To opt-out of certificate renewal the flag `--certificate-renewal=false` can be used. For more information see the [certificate management guide](/docs/tasks/administer-cluster/kubeadmkubeadm-certs). {{</ note >}} </ins> <del> 1.  Choose a version to upgrade to, and run the appropriate command. For example: </del> <ins> -  Choose a version to upgrade to, and run the appropriate command. For example: </ins> ```shell # replace x with the patch version you picked for this upgrade

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.
Change:
## Creating a Deployment <del> Before creating a Deployment define an [environment variable](/docs/tasks/inject-data-application/define-environment-variable-container/#define-an-environment-variable-for-a-container) for a container. </del> The following is an example of a Deployment. It creates a ReplicaSet to bring up three `nginx` Pods: {{< codenew file="controllers/nginx-deployment.yaml" >}}

Discussion:
It is unclear what is meant by The statement appears directly under the heading "Creating a Deployment." It is confusing, and it is unclear what relevance defining an "environment variable" has to do with a deployment. Could it be that the author intended to present an action item of defining a pod, and linked to another article that coincidentally contained markup to do so? Suggestion is to clean up the paragraph, and link it to an appropriate article on defining pods, if so.
/sig apps
/retitle Unclear text in “Creating a Deployment” section of Deployment concept
/language en /help /triage accepted
I recommend removing from the page. That's a small fix that doesn't need us to work on the rest of
/assign
page to be updated:
Looks similar (possibly duplicate) of issue we already have
True. /triage duplicate
/remove-triage accepted
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
/remove-help Oops
Change:
In Kubernetes, there are two ways to expose Pod and container fields to a running container: <del> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/#the-downward-api) </del> <ins> * as [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/) </ins> * as [files in a `downwardAPI` volume](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) Together, these two ways of exposing Pod and container fields are called the

Discussion:
This is a Bug Report <!--Required Information--Problem: The link is dead. The content from the section seems moved into top of the document and glossary in . Proposed Solution: remove fragment from the link change link to or Page to Update: /docs/concepts/workloads/pods/downward-api /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information /docs/tasks/job/indexed-parallel-processing-static
/assign
/language en /triage accepted /help We should find existing hyperlinks to and replace those with links to
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 : /language en /triage accepted /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
/unassign As has already opened a PR
/assign
GitHub didn't allow me to assign the following users: hs0210. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Change:
<link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet"> <link href="/docs/tutorials/kubernetes-basics/public/css/overrides.css" rel="stylesheet"> <del> <script src="https://katacoda.com/embed.js"></script> </del> <ins> {{< katacoda-tutorial >}} </ins> <div class="layout" id="top">

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 For pages that use Katacoda, add a warning about its removal. Why is this needed Prompted by and Comments /priority critical-urgent /language en /triage accepted
Change:
### Volume Binding Mode <del> The `volumeBindingMode` field controls when [volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default. </del> <ins> The `volumeBindingMode` field controls when [volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default. </ins> The `Immediate` mode indicates that volume binding and dynamic provisioning occurs once the PersistentVolumeClaim is created. For storage

Discussion:
There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted