jiebi/CodeConvo huggingface dataset:
Change:
{% capture whatsnext %} * See [Using ConfigMap Data in Pods](/docs/tasks/configure-pod-container/configure-pod-configmap). <ins> * Follow a real world example of [Configuring Redis using a ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/). </ins> {% endcapture %} {% include templates/task.md %}

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done
Change:
<del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: frontend

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: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--
Change:
| Elixir               | [github.com/coryodaniel/k8s](https://github.com/coryodaniel/k8s) |

Discussion:
They library is mildly defunct now The following project: has been forked and is meant to replace the former per Please update the documentation
Thanks for the suggestion I think we'd be happy to link to an extra project. I'm more wary of removing a project from the list because someone has forked it. If were marked as archived, it'd be easy to agree with the removal. If not, well, maybe we should leave it in and let the reader decide.
OK, with the understanding that we'll add an extra link but won't remove the old one: /triage accepted /language en
/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:
</span></pre><p>The KubeletConfiguration type should be used to change the configurations that will be passed to all kubelet instances deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.</p> <p>See https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ or <del> https://godoc.org/k8s.io/kubelet/config/v1beta1#KubeletConfiguration </del> <ins> https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration </ins> for kubelet official documentation.</p> <p>Here is a fully populated example of a single YAML file containing multiple configuration types to be used during a <code>kubeadm init</code> run.</p>

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: According to and , so updated the generator and opened a PR which replaces most of string with , but and remain in these files: - Proposed Solution: Maybe we need to check/update the generator again, and then generate references again. Or, if the generator is fine, then we might update those files manually. Page to Update: ,,- ,,- ,meta/v1.Duration,-cacheDuration%20indicates%20the
for kubeadm, the change ~must~ can be done here: but we are in code freeze for 1.24, so let's wait until code freeze is lifted (19th of April) /sig cluster-lifecycle
/triage accepted
/sig node
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 /assign
/reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed.
Reopened this issue. <detailsIn response to : /reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed. 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
But I didn't find the link in this file . ,meta/v1.Duration,-cacheDuration%20indicates%20the page points to There are the only links that still exist in this directory : // For semantics around ctx use and closing/ending streaming RPCs, please refer to for example (Code generated by protoc-gen-gogo.

DO NOT EDIT.) If these links need to be updated, they need to be updated in or repository. This part of the update should be beyond the scope of Kubernetes.
Change:
trace spans. As with the apiserver, the endpoint and sampling rate are configurable. Trace context propagation is also configured. A parent span's sampling decision is always respected. A provided tracing configuration sampling rate will apply to spans without a parent. <del> Enabled without a configured endpoint, the default OpenTelemetry Collector reciever address of "localhost:4317" is set. </del> <ins> Enabled without a configured endpoint, the default OpenTelemetry Collector receiver address of "localhost:4317" is set. </ins> #### Enabling tracing in the kubelet

Discussion:
What would you like to be The spelling of the receiver i.e is wrong Why is this needed Fix Spelling Comments /language en /assign
/retitle Spelling mistake in Traces For Kubernetes System Components page
oh its already underway, don't mind me.
Hi can I work on this ?
/assign
actually, there already exists an open PR () that opened. /assign
Ok, Should I unassign myself ?
/unassign
/triage accepted
/kind bug /sig docs
Change:
`Terminated`状態のコンテナは実行されて、完了したときまたは何らかの理由で失敗したことを示します。`Terminated`状態のコンテナを持つPodに対して`kubectl`コマンドを使用すると、いずれにせよ理由と終了コード、コンテナの開始時刻と終了時刻が表示されます。 <del> コンテナがTerminatedに入る前に`preStop`フックがあれば実行されます。 </del> <ins> コンテナが`Terminated`に入る前に`preStop`フックがあれば実行されます。 </ins> ## コンテナの再起動ポリシー {#restart-policy}

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:
```shell ETCDCTL_API=3 etcdctl --endpoints 10.2.0.9:2379 snapshot restore snapshotdb ``` <ins> Another example for restoring using etcdutl options: ```shell ETCDCTL_API=3 etcdutl --data-dir <data-dir-location> snapshot restore snapshotdb ``` </ins> For more information and examples on restoring a cluster from a snapshot file, see [etcd disaster recovery documentation](https://etcd.io/docs/current/op-guide/recovery/#restoring-a-cluster).

Discussion:
maybe adding an example with data dir for restore
/triage accepted
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]:
Change:
<del> --- title: "Clusters" weight: 60 --- </del>

Discussion:
This is a Feature Request What would you like to be Post-merge of , move the tutorials under into Merge clusters section into security section here: Why is this needed Issue description is a slight modification from original request in the comment Comments /hold for /cc /sig docs security
this might be a good first issue for new contributors in sig-security-docs /triage accepted
Hi, I would like to work on this issue. /assign
/kind cleanup
Hi , I a query: moving the tutorials from the cluster sub-directory into the security sub-directory, the cluster sub-directory will only have its file so do I need to do something regarding it ( file)? Thanks
Whenever you are free can you please help me with the above mentioned query. Thanks
Change:
<ins> --- title: Kubeletの証明書のローテーションを設定する content_type: task --- <!-- overview --> このページでは、kubeletの証明書のローテーションを設定する方法を説明します。 {{< feature-state for_k8s_version="v1.8" state="beta" >}} ## {{% heading "prerequisites" %}} * Kubernetesはバージョン1.8.0以降である必要があります。 <!-- steps --> ## 概要 kubeletは、Kubernetes APIへの認証のために証明書を使用します。デフォルトでは、証明書は1年間の有効期限付きで発行されるため、頻繁に更新する必要はありません。 Kubernetes 1.8にはベータ機能の[kubelet certificate rotation](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/)が含まれているため、現在の証明書の有効期限が近づいたときに自動的に新しい鍵を生成して、Kubernetes APIに新しい証明書をリクエストできます。新しい証明書が利用できるようになると、Kubernetes APIへの接続の認証に利用されます。 ## クライアント証明書のローテーションを有効にする `kubelet`プロセスは`--rotate-certificates`という引数を受け付けます。この引数によって、現在使用している証明書の有効期限が近づいたときに、kubeletが自動的に新しい証明書をリクエストするかどうかを制御できます。証明書のローテーションはベータ機能であるため、`--feature-gates=RotateKubeletClientCertificate=true`を使用してフィーチャーフラグを有効にする必要もあります。 `kube-controller-manager`プロセスは、`--experimental-cluster-signing-duration`という引数を受け付け、この引数で証明書が発行される期間を制御できます。 ## 証明書のローテーションの設定を理解する kubeletが起動すると、ブートストラップが設定されている場合(`--bootstrap-kubeconfig`フラグを使用した場合)、初期証明書を使用してKubernetes APIに接続して、証明書署名リクエスト(certificate signing request、CSR)を発行します。証明書署名リクエストのステータスは、次のコマンドで表示できます。 ```sh kubectl get csr ``` ノード上のkubeletから発行された証明書署名リクエストは、初めは`Pending`状態です。証明書署名リクエストが特定の条件を満たすと、コントローラーマネージャーに自動的に承認され、`Approved`状態になります。次に、コントローラーマネージャーは`--experimental-cluster-signing-duration`パラメーターで指定された有効期限で発行された証明書に署名を行い、署名された証明書が証明書署名リクエストに添付されます。 kubeletは署名された証明書をKubernetes APIから取得し、ディスク上の`--cert-dir`で指定された場所に書き込みます。その後、kubeletは新しい証明書を使用してKubernetes APIに接続するようになります。 署名された証明書の有効期限が近づくと、kubeletはKubernetes APIを使用して新しい証明書署名リクエストを自動的に発行します。再び、コントローラーマネージャーは証明書のリクエストを自動的に承認し、署名された証明書を証明書署名リクエストに添付します。kubeletは新しい署名された証明書をKubernetes APIから取得してディスクに書き込みます。その後、kubeletは既存のコネクションを更新して、新しい証明書でKubernetes APIに再接続します。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
and if `concurrencyPolicy` is set to `Allow`, the jobs will always run at least once. <ins> {{< caution >}} If `startingDeadlineSeconds` is set to a value less than 10 seconds, the CronJob may not be scheduled. This is because the CronJob controller checks things every 10 seconds. {{< /caution >}} </ins> For every CronJob, the CronJob {{< glossary_tooltip term_id="controller" >}} checks how many schedules it missed in the duration from its last scheduled time until now. If there are more than 100 missed schedules, then it does not start the job and logs the error ````

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: can be set to any value, but . If it's set to any value less than 10s the CronJob will be never scheduled. Proposed Solution: Force the value to be always greater than 10, or warn people there are non-working values Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.15.12
/kind cleanup /language en /triage accepted
Thanks
Relevant to
I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. Specifically I would add a callout, with text similar to: /good-first-issue /sig apps
This request has been marked as suitable for new contributors. 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 : I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. if is set to a value less than 10 seconds then the CronJob may not be scheduled. /sig apps 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:
也可以运行在不同的机器上以获得更好的安全性和可用性。 因为 etcd 存储着集群的配置数据，应该经常性地对 etcd 数据库进行备份， 以确保在需要的时候你可以修复该数据库。与配置和使用 etcd 相关的细节可参阅 <del> [etcd FAQ](/https://etcd.io/docs/v3.5/faq/)。 </del> <ins> [etcd FAQ](https://etcd.io/docs/v3.5/faq/)。 </ins> 更多的细节可参阅[为 Kubernetes 运维 etcd 集群](/zh-cn/docs/tasks/administer-cluster/configure-upgrade-etcd/) 和[使用 kubeadm 配置高可用的 etcd 集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)。 <!--

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 the Chinese docs, the link to the etcd FAQ starts with a forward slash This is causing Hugo to error out when building in Windows. Since this line has been there for quite a few years, I don't know how Hugo kept building till now. Anyway, this slash is creating the wrong link in production itself. ! Proposed Solution: Just removing the slash is enough. Page to Update: This issue is present in the docs for older versions too. Should we look into fixing it for other branches? <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Should I look into fixing this issue in older versions of the page?
/assign
backport fixes are welcome, but we don't require them.
I guess, I will leave them be then
Change:
Add-ons extend the functionality of Kubernetes. <del> This page lists some of the available add-ons and links to their respective installation instructions. </del> <ins> This page lists some of the available add-ons and links to their respective installation instructions. The list does not try to be exhaustive. </ins> <!-- body -->

Discussion:
This is a Feature Request Update to either remove all vendor specific information or link to 3rd party documentation. Related: Why is this needed Update the docs to match our . /sig docs /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 Feature Request /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
/triage accepted Everyone: If you have questions about how to work on this, or you're not sure whether a piece of text does or doesn't comply with the policy on 3rd party content: go ahead and reply here to ask for that help. SIG Docs reviewers are here to offer you that kind of advice.
Should I remove all links which aren't pointing to a page in For eg. should I remove all links in paragraph and just remain normal texts ?
/assign
I would like work on this but can you help with the information regarding projects that are necessary for kubernetes to function. I get the idea of removing unnecessary links but dont know which project to act on, so i will be looking forward to your reply :)
Here's my attempt to solve this issue. Please guide me if there's something more to do or if I have removed something very important :)
/assign
Hey I'm interested in contributing to this repo, but I have no idea on how to go about it, please can someone help by putting me through?
I'll highlight your request to the documentation special interest group
did you have any specific questions about how to get started?
Hey , I'd be happy to work on this. Please guide me on how to get started here.
/ assign
hey can you please elaborate what exactly is vendor specific information so that i can edit it out of the documentation?
Change:
CNI 제공자가 데몬셋(DaemonSet)으로 실행되는 경우 추가 컨트롤 플레인 노드에는 이 단계가 필요하지 않다. <del> 1.  컨트롤 플레인 노드에 적용된 cordon을 해제한다. </del> <ins> -  컨트롤 플레인 노드에 적용된 cordon을 해제한다. </ins> ```shell # <cp-node-name>을 컨트롤 플레인 노드 이름으로 바꾼다.

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: Broken layout on "kubeadm " ! Proposed Solution: Check and apply upstream changes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
/unassign This issue already has been assigned to .
Change:
kubernetesVersion: v1.16.0 scheduler: extraArgs: <del> bind-address: 0.0.0.0 config: /home/johndoe/schedconfig.yaml kubeconfig: /home/johndoe/kubeconfig.yaml </del> <ins> config: /etc/kubernetes/scheduler-config.yaml extraVolumes: - name: schedulerconfig hostPath: /home/johndoe/schedconfig.yaml mountPath: /etc/kubernetes/scheduler-config.yaml readOnly: true pathType: "File" </ins> ```

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 example at shows in the being used without . Because (by default?) sets up the scheduler to run inside a pod, it is necessary to use to mount the config file into the pod. Using the example as given will cause the scheduler to fail to start, even if the referenced config file exists on the host. It is also not mentioned here that providing a config file (now?) causes the scheduler to ignore several of the flags (like and ) that kubeadm sets the scheduler up with, so any config file passed needs to duplicate those settings if the scheduler is to work as kubeadm intends. In particular, without setting a , the scheduler will not come up. This documentation is especially important because doesn't necessarily work before the scheduler can schedule enough Kubernetes components to start up TLS, so it can be nearly impossible to debug what is wrong with a non-working scheduler pod without a lot of documentation. Proposed Solution: A working example that lets the scheduler come up with a nontrivial configuration change seems to be: Scheduler config file on host in e.g. : Config file for to point to and mount it: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.19.3 <!--Additional Information:--
no other ways are supported, by kubeadm. i can see how the kubeadm example may be bogus in that regard. if scheduler config overrides flags that is an artifact of the kube-scheduler. normally flags should override config, or the mixture should just error out. if some kube-scheduler specifics are not documented they should go here: or here: kubeadm just allows you to configure it and i don't think we should special case the component a lot here: having the following minimal example makes sense to me: ^ this sentence can also be extended to link to /sig cluster-lifecycle scheduling /triage accepted PRs are welcome.
/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
perhaps pages like: should start linking to the respective component config pages too:
/assign
Change:
controller: true kind: ReplicaSet name: frontend <del> uid: f391f6db-bb9b-4c09-ae74-6a1f77f3d5cf </del> <ins> uid: e129deca-f864-481b-bb16-b27abfd92292 </ins> ... ```

Discussion:
Hi Currently we obsrved that following image is not availble
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 /sig docs
can you please provide the page link of the issue?
HI Kubernetes/Website PFA link
/retitle Container image is not available for /kind bug
This looks similar to issue we already have I think it is a duplicate. /triage duplicate
Thanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned
Closing this issue, marking it as "Not Planned". <detailsIn response to : Thanks for raising this! 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