jiebi/CodeConvo huggingface dataset:
Change:
<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta4<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>UpgradeConfiguration<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apply</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">diff</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">node</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">plan</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span></pre><p>The <code>UpgradeConfiguration</code> structure includes a few substructures that only apply to different subcommands of <code>kubeadm upgrade</code>. For example, the <code>apply</code> substructure will be used with the <code>kubeadm upgrade apply</code> subcommand and all other substructures will be ignored in such a case.</p>

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.
Change:
title: ConfigMap id: configmap date: 2018-04-12 <del> full_link: /docs/tasks/configure-pod-container/configure-pod-configmap/ </del> <ins> full_link: /docs/concepts/configuration/configmap/ </ins> short_description: > <del> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a volume. </del> <ins> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or configuraton files in a volume. </ins> aka: tags: - core-object --- <del> An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {{< glossary_tooltip text="volume" term_id="volume" >}}. </del> <ins> An API object used to store non-confidential data in key-value pairs. {{< glossary_tooltip text="Pods" term_id="pod" >}} can consume ConfigMaps as environment variables, command-line arguments, or as configuration files in a {{< glossary_tooltip text="volume" term_id="volume" >}}. </ins> <!--more--> <del> Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/). </del> <ins> A ConfigMap allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="image" >}}, so that your applications are easily portable. </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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!
Change:
if [ -d "$1" ] ; then SYNCED=1 for f in `find $1 -name "*.md"` ; do <del> EN_VERSION=`echo $f | sed "s/content/..//content/en//g"` </del> <ins> EN_VERSION=`echo $f | sed "s/content/.{2,5}//content/en//g"` </ins> if [ ! -e $EN_VERSION ]; then echo -e "**removed**t$EN_VERSION" SYNCED=0

Discussion:
This is a Bug Report cannot sync files under correctly. This problem should exist with $LOCALIZED more than 2 characters. When happened when zh -zh-cn see <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Proposed Solution:** needs to be updated to <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/cc /language zh
/triage accepted
I found this problem when reviewing this PR , the commit time of the version is later than the version, but did not correctly find the difference between the 2 versions.
nice catch!
When the script was developed, I was only focusing on markdown files.
Change:
ヘルプが必要な場合は、ターミナルウィンドウから`kubectl help`を実行してください。 <ins> ## クラスター内認証と名前空間のオーバーライド {#in-cluster-authentication-and-namespace-overrides} デフォルトでは、`kubectl`は最初にPod内で動作しているか、つまりクラスター内で動作しているかどうかを判断します。まず、`KUBERNETES_SERVICE_HOST`と`KUBERNETES_SERVICE_PORT`の環境変数を確認し、サービスアカウントのトークンファイルが`/var/run/secrets/kubernetes.io/serviceaccount/token`に存在するかどうかを確認します。3つともクラスター内で見つかった場合、クラスター内認証とみなされます。 後方互換性を保つため、クラスター内認証時に`POD_NAMESPACE`環境変数が設定されている場合には、サービスアカウントトークンのデフォルトの名前空間が上書きされます。名前空間のデフォルトに依存しているすべてのマニフェストやツールは、この影響を受けます。 **`POD_NAMESPACE`環境変数** `POD_NAMESPACE`環境変数が設定されている場合、名前空間に属するリソースのCLI操作は、デフォルトで環境変数の値になります。例えば、変数に`seattle`が設定されている場合、`kubectl get pods`は、`seattle`名前空間のPodを返します。これは、Podが名前空間に属するリソースであり、コマンドで名前空間が指定されていないためです。`kubectl api-resources`の出力を見て、リソースが名前空間に属するかどうかを判断してください。 明示的に`--namespace <value>`を使用すると、この動作は上書きされます。 **kubectlによるServiceAccountトークンの処理方法** 以下の条件がすべて成立した場合、 * `/var/run/secrets/kubernetes.io/serviceaccount/token`にマウントされたKubernetesサービスアカウントのトークンファイルがある * `KUBERNETES_SERVICE_HOST`環境変数が設定されている * `KUBERNETES_SERVICE_PORT`環境変数が設定されている * kubectlコマンドラインで名前空間を明示的に指定しない kubectlはクラスター内で実行されているとみなして、そのServiceAccountの名前空間(これはPodの名前空間と同じです)を検索し、その名前空間に対して機能します。これは、クラスターの外の動作とは異なります。kubectlがクラスターの外で実行され、名前空間を指定しない場合、kubectlコマンドは、クライアント構成の現在のコンテキストに設定されている名前空間に対して動作します。kubectlのデフォルトの名前空間を変更するには、次のコマンドを使用できます。 ```shell kubectl config set-context --current --namespace=<namespace-name> ``` </ins> ## 操作 以下の表に、`kubectl`のすべての操作の簡単な説明と一般的な構文を示します。

Discussion:
This is a Feature Request What would you like to be Add the describe of in-cluster to kubectl document in Japanese. The target file is Why is this needed There is that describe in English. Comments /language ja /assign
/triage accepted
Change:
to track changes. That mechanism has been superseded by [Server-side apply](/docs/reference/using-api/server-side-apply/). <ins> ### kubectl.kubernetes.io/restartedAt {#kubectl-k8s-io-restart-at} Type: Annotation Example: `kubectl.kubernetes.io/restartedAt: "2024-06-21T17:27:41Z"` Used on: Deployment, ReplicaSet, StatefulSet, DaemonSet, Pod This annotation contains the latest restart time of a resource (Deployment, ReplicaSet, StatefulSet or DaemonSet), where kubectl triggered a rollout in order to force creation of new Pods. The command `kubectl rollout restart <RESOURCE>` triggers a restart by patching the template metadata of all the pods of resource with this annotation. In above example the latest restart time is shown as 21st June 2024 at 17:27:41 UTC. You should not assume that this annotation represents the date / time of the most recent update; a separate change could have been made since the last manually triggered rollout. If you manually set this annotation on a Pod, nothing happens. The restarting side effect comes from how workload management and Pod templating works. </ins> ### endpoints.kubernetes.io/over-capacity Type: Annotation

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: Kubernetes defined an annotation, . For example, this annotation is set during rolling restarts. That annotation is unregistered because it doesn't appear inside Proposed Solution: Register the annotation, by documenting it in&hellip; Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig architecture /sig cli /language en
/assign
/lgtm /assign
I am happy to work on this issue once triage accepted, thanks.
Unassigning myself as PR is already raised by
/triage accepted
/priority backlog
PR that is working on this issue .
PRs to fix this are welcome. what are your plans for ?
hi are you still working on the issue?
How about this
Let me know if no one's working on the issue currently then i can raise this PR. I already have this in my local branch
a PR is welcome if you have code for it, nearly always. It's also polite to try to liaise with anyone else who's mentioned that they plan to do work on the same issue. In this case, you can see things have gone quiet. Opening a PR here can't reasonably be seen as thoughtlessly barging in.
Thanks for confirmation .
Raised the PR for this annotation, please take a look. I'll be happy to improve it based on your reviews.
Change:
### Reclaim Policy PersistentVolumes that are dynamically created by a StorageClass will have the <del> reclaim policy specified in the `reclaimPolicy` field of the class, which can be </del> <ins> [reclaim policy](/docs/concepts/storage/persistent-volumes/#reclaiming) specified in the `reclaimPolicy` field of the class, which can be </ins> either `Delete` or `Retain`. If no `reclaimPolicy` is specified when a StorageClass object is created, it will default to `Delete`.

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
Change:
* Read about [Ingress](/docs/concepts/services-networking/ingress/), which exposes HTTP and HTTPS routes from outside the cluster to Services within your cluster. <del> * Read about [Gateway](https://gateway-api.sigs.k8s.io/), an extension to </del> <ins> * Read about [Gateway](/docs/concepts/services-networking/gateway/), an extension to </ins> Kubernetes that provides more flexibility than Ingress. For more context, read the following:

Discussion:
This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new "Gateway API" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the "Ingress" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the "Service" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign
checkout the gateway API in the section and look out for the bugs
/triage accepted /priority important-longterm
How about adding a short link eg that redirects (302) to https://gateway- ?
I'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.
Also see
Change:
{{ if not $is_valid }} {{ errorf "%q is not a valid feature-state, use one of %q" $state $valid_states }} {{ else }} <del> <div class="my-2 feature-state-notice feature-{{ $state }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]</code> </div> </del> <ins> <div class="my-2 feature-state-notice feature-{{ $state }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]</code> </div> </ins> {{ end }} {{- else -}}

Discussion:
This is a Bug Report <!--Required Information--Problem: Documentation layout issue in page under IngressClass scope Namespaced section, see following screenshot: <img width="912" alt="image" src=""Proposed Solution: I would like to create a PR to fix it, the solution is to remove and outside of template Page to Update: Documentation layout issue in Ingress.
Change:
## Kubeadm <del> [`kubeadm`](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)은 물리적 환경, 클라우드 서버, 또는 가상머신 상에서 안전한 쿠버네티스를 쉽게 프로비저닝하기 위한 커맨드라인 툴이다(현재는 알파 상태). </del> <ins> [`kubeadm`](/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)은 물리적 환경, 클라우드 서버, 또는 가상머신 상에서 안전한 쿠버네티스를 쉽게 프로비저닝하기 위한 커맨드라인 툴이다(현재는 알파 상태). </ins> ## Minikube

Discussion:
<!-- 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 link href is (English). The of is recently in . Proposed Solution: In , Before: After: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
/language ko
/triage accepted
Resolved by
Change:
<head> {{ partial "head.html" . }} </head> <del> <body class="td-{{ .Kind }}{{- if ne .Params.cid "" -}}{{- printf " cid-%s" (lower .Params.cid) -}}{{- end -}}"> </del> <ins> <body class="td-search {{- if ne .Params.cid "" -}}{{- printf " cid-%s" (lower .Params.cid) -}}{{- end -}}"> </ins> <header> {{ partial "navbar.html" . }} <ins> <div class="header-filler"></div> </ins> </header> {{ block "announcement" . }} {{ if .IsHome }}

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: Navbar prevents search input field from being clicked on Can reproduce on Firefox, Chrome on latest builds Proposed Solution: Remove navbar from search page Page to Update: !
is not supposed to look like that screenshot /kind bug /priority critical-urgent /area web-development Thanks for reporting this.
/triage accepted
/retitle Navbar prevents search inputfield from being clicked
Actually /retitle Search page rendering incorrectly
Change:
## APIグループ <del> [API groups](https://git.k8s.io/community/contributors/design-proposals/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </del> <ins> [API groups](https://git.k8s.io/design-proposals-archive/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </ins> APIグループは、RESTパスとシリアル化されたオブジェクトの`apiVersion`フィールドで指定されます。 KubernetesにはいくつかのAPIグループがあります:

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. --We need to update some links in because these links are broken. True) False) True) False) Why is this needed These links are broken. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
About aggregator - is certainly correct, but we would like to match the English page first. You already did so in PR .
Thank you for your advice! The URL listed in the Issue was incorrect and has been corrected. As you said, PR already uses this URL.
/triage accepted
Change:
For instructions on creating and working with cron jobs, and for an example of CronJob manifest, see [Running automated tasks with cron jobs](/docs/tasks/job/automated-tasks-with-cron-jobs).

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:
## {{% heading "prerequisites" %}} <del> These instructions are for Kubernetes {{< skew currentVersion >}}. If you want to check the integrity of components for a different version of Kubernetes, check the documentation for that Kubernetes release. </del> You will need to have the following tools installed: - `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/)) - `curl` (often provided by your operating system) <ins> - `jq` ([download jq](https://stedolan.github.io/jq/download/)) </ins> ## Verifying binary signatures

Discussion:
This is a Feature Request After release, we don't need . We should update the instructions on the task to include verification using cosign 2.0 <!-- 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 <details<summaryverification using cosign 2.0</summaryAdd a note if cosign version < 2.0 </details<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed There are some breaking changes in cosign 2.0 and we should update the instruction for the verification of images. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/sig release /sig security /retitle Update page Verify Signed Kubernetes Artifacts for cosign 2.0 /kind bug /remove-kind feature /language en /triage accepted Thanks
:+1:
I can work on this /assign
Hey Are you still working on this issue? If not, can I work on this?
Haven't gotten to it as I expected to. Please feel free to work on it /unassign
/assign
FYI
Apologies for not being able to review the PR. I am going through University exams which is ending tomorrow. I just rushed through the changes that you made and you really did awesome work on this. I'll look more into this after the exams. Thanks for working on this.