jiebi/CodeConvo huggingface dataset:
Change:
- Non-critical add-ons, e.g. for monitoring, logging, and visualization - Specific cloud provider integrations <del> Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/#kubernetes-control-plane). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation. </del> <ins> Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/overview/components/#control-plane-components). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation. </ins> ### What kubeadm's GA release means

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--Hyperlinks don't work Hyperlinks to topics <bKubernetes control plane</band <bKubernetes objects</btakes to back to <bConcepts</bpage rather than respective topics. Proposed Solution: Update linkw to point to correct content. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi If related documents are not missing, then Perhaps Kubernetes control plane should point to I noticed that the corresponding file , later than the link on page . And Kubernetes objects perhaps should point to . Seems a little bit weird. These documents should be in the same hierarchy I think. Let me create a PR to solve this issue. /assign
/kind bug
I think the link for Kubernetes control-plane should be to and I agree above that the link for Kubernetes objects should be to /assign
Hi Thanks for your PR! I submitted a PR (ref: ) to fix this issue about half a month ago, and just got approved 3 days ago. Since the CLA checking was missing after I migrated to a new github account, this PR was not merged until a few minutes ago after I let the robot recheck my CLA.
Change:
Check on the status of the Job with `kubectl`: <del> ```shell kubectl describe jobs/pi ``` The output is similar to this: ``` </del> <ins> {{< tabs name="Check status of Job" >}} {{< tab name="kubectl describe job pi" codelang="bash" >}} </ins> Name:           pi Namespace:      default Selector:       controller-uid=c9948307-e56d-4b5d-8302-ae2d7b7da67c

Discussion:
Why don't you just provide a completed example of a job with Labels, Parallelism, Completions instead of getting them from describing the job?
/kind feature /language en /priority backlog /triage accepted Nice suggestion. I don't suppose you'd be willing to open a pull request to make that change ? The source for that page is at
If I've understood what you were suggesting correctly, you would like to see what the of a Job looks like in the API. You (or anyone working on this improvement) could use to let the reader choose between using and (if you wanted examples of writing a spec for a parallel Job, then the section of that page has links to some examples already, and also links to the API reference for Job).
I would like to work on this. /assign
Change:
Some steps in this page use the `jq` tool. If you don't have `jq`, you can install it via your operating system's software sources, or fetch it from <del> [https://stedolan.github.io/jq/](https://stedolan.github.io/jq/). </del> <ins> [https://jqlang.github.io/jq/](https://jqlang.github.io/jq/). </ins> <!-- steps -->

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 download page for is now (previously ) Proposed Solution: Throughout the English pages, replace the old download URL with the new one. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The download page for is now (previously ) Throughout the English pages, replace the old download URL with the new one. <!--Kubernetes Version:--/language en /priority backlog /triage accepted /help </details
I want to help with this. /assign
Hello I would like to work on this issue are you working on the issue?
I have riasd PR to help with this issue.
Change:
server. If the Pod was still running on a node, that forcible deletion triggers the kubelet to begin immediate cleanup. <del> {{< note >}} You must specify an additional flag `--force` along with `--grace-period=0` </del> <ins> Using kubectl, You must specify an additional flag `--force` along with `--grace-period=0` </ins> in order to perform force deletions. <del> {{< /note >}} </del> When a force deletion is performed, the API server does not wait for confirmation from the kubelet that the Pod has been terminated on the node it was running on. It

Discussion:
work not well. Not sure how to fix it. This issue has spreaded to the currently. <img width="550" alt="image" src=""
/triage accepted
/language en
For a likely fix, see
Change:
To apply: 1. Open a pull request that adds your GitHub user name to a section of the <del> [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/main/OWNERS) file </del> <ins> [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/main/OWNERS_ALIASES) file </ins> in the `kubernetes/website` repository. {{< note >}}

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: In and , links go to , which is wrong. They should go to . Proposed Solution: Find , and replace with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /kind cleanup /good-first-issue
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In and , Find , and replace with . Page to Update: <!--Kubernetes Version:--/language en /kind cleanup /good-first-issue 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
/triage accepted
/assign
Change:
Prepare the node for maintenance by marking it unschedulable and evicting the workloads: ```shell <ins> # execute this command on a control plane node </ins> # replace <node-to-drain> with the name of your node you are draining kubectl drain <node-to-drain> --ignore-daemonsets ```

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: This is related to the page . The and commands should be executed on the controlplane node. This is not obvious from the documentation. A new user unfamiliar with the process of upgrade will invariably execute these commands on the worker node and will fail. Proposed Solution: Add instruction to execute the and commands from the controlplane node. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/sig docs /language en
/sig cluster-lifecycle /triage accepted
Change:
spec: accessModes: - ReadWriteOnce <ins> storageClassName: "" </ins> resources: requests: storage: 20Gi

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: I follow the instruction but when i create mysql deployment, kubernetes is actually creating new disk instead of using my . here is the output of Proposed Solution: Explain clearer how is working Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I dig deeper look like the PV i created in tutorial has empty . Thats why its not matched and new PV get created when i created PVC.
Pull Request submit
Closing because merged.
Change:
kubectl config view ``` <del> {{< note >}}For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/).{{< /note >}} </del> <ins> {{< note >}} For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/). {{< /note >}} </ins> ## Create a Service

Discussion:
This is a Bug Report <!--Required Information--Problem: Text formatting issue under the Create a Minikube cluster heading. The text is listed erroneously (this appears to be a simple authoring/build issue with the content. Proposed Solution: Fix the typo or the build issue for this section of the page. Page to Update:
/labels language/en /assign
Relevant to issue
/language en /kind bug /priority important-longterm
Change:
<ins> --- title: ボリュームヘルスモニタリング content_type: concept weight: 100 --- <!-- overview --> {{< feature-state for_k8s_version="v1.21" state="alpha" >}} {{< glossary_tooltip text="CSI" term_id="csi" >}}ボリュームヘルスモニタリングにより、CSIドライバーは、基盤となるストレージシステムから異常なボリューム状態を検出し、それらを{{< glossary_tooltip text="PVC" term_id= "persistent-volume-claim" >}}または{{< glossary_tooltip text="Pod" term_id="pod" >}}のイベントとして報告できます。 <!-- body --> ## ボリュームヘルスモニタリング Kubernetes _volume health monitoring_ は、KubernetesがContainerStorageInterface(CSI)を実装する方法の一部です。ボリュームヘルスモニタリング機能は、外部のヘルスモニターコントローラーと{{< glossary_tooltip term_id="kubelet" text="kubelet" >}}の2つのコンポーネントで実装されます。 CSIドライバーがコントローラー側からのボリュームヘルスモニタリング機能をサポートしている場合、CSIボリュームで異常なボリューム状態が検出されると、関連する{{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}}(PVC)でイベントが報告されます。 外部ヘルスモニター{{< glossary_tooltip text="コントローラー" term_id="controller" >}}も、ノード障害イベントを監視します。`enable-node-watcher`フラグをtrueに設定することで、ノード障害の監視を有効にできます。外部ヘルスモニターがノード障害イベントを検出すると、コントローラーは、このPVCを使用するポッドが障害ノード上にあることを示すために、PVCでイベントが報告されることを報告します。 CSIドライバーがノード側からのボリュームヘルスモニタリング機能をサポートしている場合、CSIボリュームで異常なボリューム状態が検出されると、PVCを使用するすべてのPodでイベントが報告されます。さらに、ボリュームヘルス情報はKubelet VolumeStatsメトリクスとして公開されます。新しいメトリックkubelet_volume_stats_health_status_abnormalが追加されました。このメトリックには`namespace`と`persistentvolumeclaim`の2つのラベルが含まれます。カウントは1または0です。1はボリュームが異常であることを示し、0はボリュームが正常であることを示します。詳細については、[KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor#kubelet-metrics-changes)を確認してください。 {{< note >}} ノード側からこの機能を使用するには、`CSIVolumeHealth`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)を有効にする必要があります。 {{< /note >}} ## {{% heading "whatsnext" %}} [CSIドライバーのドキュメント](https://kubernetes-csi.github.io/docs/drivers.html)を参照して、この機能を実装しているCSIドライバーを確認してください。 </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
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:
- Read the [contributor cheatsheet](https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet) to get involved with Kubernetes feature development. - Submit a [blog post or case study](/docs/contribute/new-content/blogs-case-studies/). --> <del> ## 其他贡献方式 </del> <ins> ## 其他贡献方式 {#other-ways-to-contribute} </ins> - 访问 [Kubernetes 社区网站](/zh/community/)。 参与 Twitter 或 Stack Overflow, 了解 Kubernetes 当地的聚会和活动, 等等。 <del> - 阅读[贡献者备忘单](https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet) ，参与 Kubernetes 功能开发。 </del> <ins> - 阅读[贡献者备忘单](https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet)，参与 Kubernetes 功能开发。 </ins> - 提交一篇[博客文章或案例研究](/zh/docs/contribute/new-content/blogs-case-studies/)。

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: Chinese page is different with English version page. Proposed Solution: Update Chinese page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
thanks reviews and approvement from xichengliudui, tengqm and idealhack
Change:
requests: cpu: 700m memory: 200Mi <del> ... </del> <ins> ... status: </ins> qosClass: Guaranteed ```

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 location of qosClass is not correct in the last example, which is a result of the following command: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en /priority backlog /sig scheduling
/help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /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
/assign
Change:
<a href="https://github.com/kubernetes/kubernetes" class="button">Contribute to the K8s codebase</a> </div> </div> <del> <div id="miceType" class="center">&copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Distributed under <a href="https://github.com/kubernetes/kubernetes.github.io/blob/master/LICENSE" class="light-text">CC BY 4.0</a></div> </del> <ins> <div id="miceType" class="center"> &copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Documentation Distributed under <a href="https://github.com/kubernetes/kubernetes.github.io/blob/master/LICENSE" class="light-text">CC BY 4.0</a> </div> <div id="miceType" class="center"> Copyright &copy; {{ 'now' | date: "%Y" }} The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">https://www.linuxfoundation.org/trademark-usage</a> </div> </ins> </main> </footer>

Discussion:
Add trademark footer to properly indicate trademark guidelines around kubernetes. Something like:
Do we want to remove " 2016 The Kubernetes Authors | Distributed under CC BY 4.0" or add to it?
I'd add to it. I'd also specify that "Documentation Distributed under CC BY 4.0" Other than that, LGTM!
Change:
kubectlは、ダッシュボードを http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/ で利用できるようにします。 <del> UIはコマンドを実行しているマシンから_のみ_ アクセスできます。オプションについては`kubectl proxy --help`を参照してください。 </del> <ins> UIはコマンドを実行しているマシンから _のみ_ アクセスできます。オプションについては`kubectl proxy --help`を参照してください。 </ins> {{< note >}} Kubeconfigの認証方法は、外部IDプロバイダーやx509証明書ベースの認証には対応していません。

Discussion:
ref: ! [x] [x] [x] [ ] content/ja/docs/concepts/configuration/manage-resources- [ ] [x] content/ja/docs/concepts/configuration/pod-priority- [x] [x] [ ] content/ja/docs/concepts/containers/runtime- [x] content/ja/docs/concepts/overview/kubernetes- [x] content/ja/docs/concepts/extend-kubernetes/api-extension/custom- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with-objects/common- [x] content/ja/docs/concepts/overview/working-with-objects/field- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with- [ ] content/ja/docs/concepts/scheduling-eviction/assign-pod- [ ] content/ja/docs/concepts/scheduling-eviction/kube- [x] content/ja/docs/concepts/scheduling-eviction/taint-and- [x] [x] content/ja/docs/concepts/security/pod-security- [x] content/ja/docs/concepts/services- [x] content/ja/docs/concepts/storage/persistent- [x] [x] content/ja/docs/concepts/workloads/controllers/cron- [x] [x] [x] [x] content/ja/docs/concepts/workloads/pods/pod- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster- [x] content/ja/docs/setup/production-environment/tools/kubeadm/troubleshooting- [ ] content/ja/docs/tasks/access-application-cluster/web-ui- [x] content/ja/docs/tasks/debug-application-cluster/get-shell-running- [x] content/ja/docs/tasks/run-application/horizontal-pod-autoscale- [x] content/ja/docs/tasks/run-application/run-single-instance-stateful- [x] content/ja/docs/tutorials/stateful-application/basic-stateful- [x] content/ja/docs/tutorials/stateful- (grep) /language ja
/triage accepted
/assign
/kind bug
I'm facing same issue lol :smiley: Feel free to mention me for review if create PRs for this.
Change:
[build.environment] NODE_VERSION = "10.20.0" <del> HUGO_VERSION = "0.82.0" </del> <ins> HUGO_VERSION = "0.87.0" </ins> RUBY_VERSION = "3.0.1" [context.production.environment]

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.
Change:
When restoring the cluster, use the `--data-dir` option to specify to which folder the cluster should be restored: ```shell <del> ETCDCTL_API=3 etcdctl --data-dir <data-dir-location> snapshot restore snapshot.db </del> <ins> etcdutl --data-dir <data-dir-location> snapshot restore snapshot.db </ins> ``` where `<data-dir-location>` is a directory that will be created during the restore process. <del> Yet another example would be to first export the `ETCDCTL_API` environment variable: </del> <ins> The below example depicts the usage of the `etcdctl` tool for the restore operation: {{< note >}} The usage of `etcdctl` for restoring has been deprecated since etcd v3.5.x and may be removed from a future etcd release. {{< /note >}} </ins> ```shell export ETCDCTL_API=3

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: This issue refers to the page Kubernetes Documentation Tasks Administer a Cluster Operating etcd clusters for Kubernetes In the section titled "Restoring an etcd cluster", the commands use the utility to restore from an existing snapshot. Using for restoring snapshots is deprecated since etcd version 3.5.x Usage of this command displays a deprecation warning and suggests to use utility instead as shown below. I feel this change is necessary as the etcd official documentation has already changed to reflect the use of the utility, as can be seen in the etcd documentation referenced in this section - Proposed Solution: I have raised a PR to depict the use of the utility for restoring from an existing snapshot. Before submitting the PR, I have tested the changes on a local Kubernetes cluster for v1.28.0 and I can confirm everything works as expected. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.28.x and above <!--Additional Information:--
/assign
I have raised a PR to depict the use of the etcdutl utility for restoring from an existing snapshot. Any comments or improvements are welcome.
/retitle Use etcdutl instead of etcdctl for restoring an etcd cluster /language en
/sig etcd
/triage accepted
Also see