jiebi/CodeConvo huggingface dataset:
Change:
defaultValue: true fromVersion: "1.24" --- <del> Allow fine-tuing of experimental, beta-quality logging options. </del> <ins> Allow fine-tuning of experimental, beta-quality logging options. </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. --:information_source: If you have already worked on a docs issue for Kubernetes, you should strongly consider leaving this good first issue for someone who has not. <!--Required Information--Problem: The page has a typo in it, repeatedly: “fine-tuing” Proposed Solution: find files within that contain the typo correct the spelling Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /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: The page has a typo in it, repeatedly: “fine-tuing” find files within that contain the typo correct the spelling Page to Update: <!--Kubernetes Version:--/language en /good-first-issue </details
/triage accepted
I'm new here but I want to contribute to this. I cant see option to assign the issue to me.
Update: Just seen how other issues are assigned. /assign
We have a policy of “no cookie licking”. Anyone is welcome to open a pull request that fixes this - and I hope you will do so. See for extra guidance. It's polite to mark when you start work, just like has; if another contributor wants to work on this as well, you can - but the polite thing to do is to liaise with the person who's already working on that. Maybe they are already well on their way to submitting a change.

Welcome to Kubernetes docs
Hey , I'm a first time contributor , can i take up this issue if it hasn't been already solved?
you should read which covers your question. TL;DR: yes, but it might be a bit unhelpful if you do.
Okay , are there other good first issues that i can work on ?
to find issues labelled as “good first issues”, start from (this includes all languages, so you might want to filter it further, and it also includes issues where people have said they have begun work)
Hey, How is it going on?
PR submitted for this issue.
Change:
`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. <del> `top`    | `kubectl top [flags] [options]` | Display Resource (CPU/Memory/Storage) usage. </del> <ins> `top`    | `kubectl top (POD | NODE) [flags] [options]` | Display Resource (CPU/Memory/Storage) usage of pod or node. </ins> `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.

Discussion:
This is a Bug Report Improvements needed on the page : <!--Required Information--Problem: On Section Explain and top syntax needs to be corrected. kubectl explain [--recursive=false] [flags] kubectl top [flags] [options] Some grammatical improvements needed in section. Proposed Solution: For operations: kubectl explain TYPE [--recursive=false] [flags] kubectl top POD/NODE [flags] [options] Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /area kubectl
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language en /area kubectl 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
I will be glad to contribute to the changes if triage is accepted.
Raised a reference
I agree we should update those commands, with out adding the parameters kubectl will just ask for them. I'm not sure of the exact grammatical errors you're referring to though. /triage accepted
Change:
[release_date_format] other = "2006-01-02" <ins> # Deprecated. Planned for removal in a future release. # Use [release_full_details_initial_text] instead. [release_complete] other = "Complete" # Replace [release_complete] with [release_full_details_initial_text] [release_full_details_initial_text] other = "Complete" [release_schedule] other = "Schedule" [release_changelog] other = "Changelog" </ins> [seealso_heading] other = "See Also"

Discussion:
When the following shortcode appears in a localized document... localized document displays English words such as: "Complete 1.24 and " Instances of the shortcode display English words in various localizations, such as: Is there a way to localize the languages these shortcodes display?
For instance, see
I have asked this question in the Hugo forum, here:
/assign
This is not a Hugo bug. is the file to localize.
partially fixes this issue. Each localization branch would need to merge PR and add corresponding entries to their files, such as: - -
Thanks, yes. I wasn't sure whom to ask, and generally try not to bother you with every question I have. The Hugo forum pointed us in the right direction, and quickly put together a PR solution.
Each localization branch would need to merge PR and add corresponding entries to their data/i18n/<lang/ files Once you PR merges, we should plan to add this topic to a localization meeting and post a message in the localization slack channel. We can also send an email, re post messages in slack for additional visibility. We should make sure the message includes all the steps needed o implement this and any urgency/priority around this change for the localization teams By a partial fix in your PR, do you mean that Localization teams will need to take additional steps to apply the changes to their localization, or are there additional file changes that need to be made?
Yes, exactly. Once this PR merges, I would do all the things you've suggested above or arrange with someone to do them. I'll create separate issues for each of the localization teams to update their branches as needed. This is not a breaking change, so there is no urgency.
I've tested to make sure this isn't a breaking change. If the file is missing the required entries, the page falls back and uses the entries from
/area localization
/triage accepted
Change:
targetDate: 2024-01-17 maintenanceModeStartDate: 2024-12-28 endOfLifeDate: 2025-02-28 <ins> previousPatches: - release: 1.29.0 targetDate: 2023-12-13 </ins> - release: 1.28 releaseDate: 2023-08-15 next:

Discussion:
Hello, on the current date (13 Dec 2023) there is a bug on the page The bug is for example here: Download the latest 1.29 patch release: ). %!f(string=1.).0 is in all links - so it's not possible to download Please fix. Thank you.
Page reported in issue: /language en /sig docs
It appears that there may be an issue with the shortcode responsible for generating the version on our page. While this issue has been reported for a single page, it is a site-wide issue affecting multiple pages that use the shortcode. /kind bug /triage accepted
I'll try to investigate this issue and see if I can offer assistance. /assign
/retitle Broken info in “Install and Set Up kubectl on Windows”
Change:
Here's an example of an object configuration file: <del> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/concepts/tools/simple_deployment.yaml" %} </del> <ins> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/tutorials/object-management-kubectl/simple_deployment.yaml" %} </ins> Create the object using `kubectl apply`: ```shell <del> kubectl apply -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml </del> <ins> kubectl apply -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml </ins> ``` Print the live configuration using `kubectl get`: ```shell <del> kubectl get -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml -o yaml </del> <ins> kubectl get -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml -o yaml </ins> ``` The output shows that the `kubectl.kubernetes.io/last-applied-configuration` annotation

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: 404 on Proposed Solution: Update location of Page to Update:
Change:
[vSphere CSI driver](https://github.com/kubernetes-sigs/vsphere-csi-driver) must be installed on the cluster. You can find additional advice on how to migrate in-tree `vsphereVolume` in VMware's documentation page <del> [Migrating In-Tree vSphere Volumes to vSphere Container Storage lug-in](https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.0/vmware-vsphere-csp-getting-started/GUID-968D421F-D464-4E22-8127-6CB9FF54423F.html). </del> <ins> [Migrating In-Tree vSphere Volumes to vSphere Container Storage Plug-in](https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.0/vmware-vsphere-csp-getting-started/GUID-968D421F-D464-4E22-8127-6CB9FF54423F.html). </ins> If vSphere CSI Driver is not installed volume operations can not be performed on the PV created with the in-tree `vsphereVolume` type. You must run vSphere 7.0u2 or later in order to migrate to the vSphere CSI driver.

Discussion:
Under , the hyper link is missing a "P" in "Plug-in". Corrected:
related page :
/language en
/kind bug
/assign
/triage accepted
Thanks
Change:
PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: <del> https://kubernetes.io/docs/contribute/suggest-improvements/ </del> <ins> https://kubernetes.io/docs/contribute/suggesting-improvements/ </ins> Use the default base branch, “main”, if you're documenting existing features in the English localization.

Discussion:
This is a Bug Report Hi Team, Hope you're all doing well. Problem: When raising a PR for kubernetes/website, the guiding text is as follows - The URL listed, sadly, gives a 404. Proposed Solution: Either we fix the target url or update to an alternative location. Thoughts? Best Regards James Spurin
The URL works. Fixes welcome.
/triage accepted
I would like to work on this issue. Thanks. /assign
Change:
</a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> {{ $p := . }} <del> <a class="dropdown-item" href="/releases">Release Information</a> </del> <ins> <a class="dropdown-item" href="{{ "releases" | relLangURL }}">{{ i18n "release_information_navbar" . }}</a> </ins> {{ range .Site.Params.versions }} <a class="dropdown-item" href="{{ .url }}{{ $p.RelPermalink }}">{{ .version }}</a> {{ end }} <del> </div> </del>  No newline at end of file <ins> </div> </ins>

Discussion:
You can only get to the localized version of the page by going to the English version, and then clicking on the language dropdown to find a translation. If you are already on a localized version of the site, and the page exists in the selected language, it redirects you to the English version. See this comment for more info: Originally posted by in /area web-development
/area localization
/triage accepted
/priority important-longterm
/assign
Change:
#### Spécifier la version de Kubernetes Vous pouvez spécifier la version de Kubernetes pour Minikube à utiliser en ajoutant la chaîne `--kubernetes-version` à la commande `minikube start`. <del> Par exemple, pour exécuter la version {{< param "fullversion" >}}, procédez comme suit: </del> <ins> Par exemple, pour exécuter la version {{< skew currentPatchVersion >}}, procédez comme suit: </ins> ```shell <del> minikube start --kubernetes-version {{< param "fullversion" >}} </del> <ins> minikube start --kubernetes-version v{{< skew currentPatchVersion >}} </ins> ``` #### Spécification du pilote de machine virtuelle

Discussion:
This is a Bug Report Problem: The param is deprecated. Proposed Solution: Replace the shortcode (French pages), for example with when possible and append when needed. Part of /language fr /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:
--> ## 不健康的 Pod 驱逐策略   {#unhealthy-pod-eviction-policy} <del> {{< feature-state for_k8s_version="v1.26" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.27" state="beta" >}} </ins> {{< 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: The feature state is not consistent between English version (v1.27 beta) and Chinese version (v1.26 beta). Proposed Solution: Make the translation(s) be consistent. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hey If you want to work on this issue then you may assign it. /sig docs /language zh
/triage accepted /assign
/retitle [zh] Stale feature state for Chinese version of “Specifying a Disruption Budget for your Application”
Change:
{{< feature-state for_k8s_version="v1.18" state="beta" >}} <del> startupProbeは、サービスの開始に時間がかかるコンテナを持つポッドに役立ちます。livenessProbeの間隔を長く設定するのではなく、コンテナの起動時に別のProbeを構成して、livenessProbeの間隔よりも長い時間を許可できます。 </del> <ins> startupProbeは、サービスの開始に時間がかかるコンテナを持つPodに役立ちます。livenessProbeの間隔を長く設定するのではなく、コンテナの起動時に別のProbeを構成して、livenessProbeの間隔よりも長い時間を許可できます。 </ins> コンテナの起動時間が、`initialDelaySeconds + failureThreshold x periodSeconds`よりも長い場合は、livenessProbeと同じエンドポイントをチェックするためにstartupProbeを指定します。`periodSeconds`のデフォルトは30秒です。次に、`failureThreshold`をlivenessProbeのデフォルト値を変更せずにコンテナが起動できるように、十分に高い値を設定します。これによりデッドロックを防ぐことができます。 ## Podの終了 {#pod-termination}

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:
<ins> --- title: Limit Range content_type: concept weight: 10 --- <!-- overview --> デフォルトでは、コンテナは、Kubernetesクラスター上の[計算リソース](/docs/concepts/configuration/manage-resources-containers/)の消費を制限されずに実行されます。リソースクォータを利用すれば、クラスター管理者はリソースの消費と作成を{{< glossary_tooltip text="名前空間" term_id="namespace" >}}ベースで制限することができます。名前空間内では、Podやコンテナは名前空間のリソースクォータで定義された範囲内でできるだけ多くのCPUとメモリーを消費できてしまうため、1つのPodまたはコンテナが利用可能なすべてのリソースを専有してしまう恐れがあります。LimitRangeを利用すれば、このような名前空間内での(Podやコンテナへの)リソースの割り当てを制限するポリシーを定めることができます。 <!-- body --> *LimitRange*を利用すると、次のような制約を課せるようになります。 - 名前空間内のPodまたはコンテナごとに、計算リソースの使用量の最小値と最大値を強制する。 - 名前空間内のPersistentVolumeClaimごとに、ストレージリクエストの最小値と最大値を強制する。 - 名前空間内で、リソースのrequestとlimitの割合を強制する。 - 名前空間内の計算リソースのデフォルトのrequest/limitの値を設定して、実行時にコンテナに自動的に注入する。 ## LimitRangeを有効にする Kubernetes 1.10以降では、LimitRangeのサポートはデフォルトで有効になりました。 LimitRangeが特定の名前空間内で強制されるのは、その名前空間内にLimitRangeオブジェクトが存在する場合です。 LimitRangeオブジェクトの名前は、有効な[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)でなければなりません。 ### Limit Rangeの概要 - 管理者は、1つの名前空間に1つのLimitRangeを作成します。 - ユーザーは、Pod、コンテナ、PersistentVolumeClaimのようなリソースを名前空間内に作成します。 - `LimitRanger`アドミッションコントローラーは、計算リソース要求が設定されていないすべてのPodとコンテナに対して、デフォルト値と制限値を強制します。そして、リソースの使用量を追跡し、名前空間内に存在するすべてのLimitRangeで定義された最小値、最大値、割合を外れないことを保証します。 - LimitRangeの制約を破るようなリソース(Pod、コンテナ、PersistentVolumeClaim)の作成や更新を行うと、APIサーバーへのリクエストがHTTPステータスコード`403 FORBIDDEN`で失敗し、破られた制約を説明するメッセージが返されます。 - 名前空間内でLimitRangeが`cpu`や`memory`などの計算リソースに対して有効になっている場合、ユーザーはrequestsやlimitsに値を指定しなければなりません。指定しなかった場合、システムはPodの作成を拒否する可能性があります。 - LimitRangeの検証は、Podのアドミッションステージでのみ発生し、実行中のPodでは発生しません。 以下は、LimitRangeを使用して作成できるポリシーの例です。 - 8GiBのRAMと16コアのCPUの容量がある2ノードのクラスター上で、名前空間内のPodに対して、CPUには100mのrequestと最大500mのlimitの制約を課し、メモリーには200Miのrequestと600Miのlimitの制約を課す。 - Spec内のrequestsにcpuやmemoryを指定せずに起動したコンテナに対して、CPUにはデフォルトで150mのlimitとrequestを、メモリーにはデフォルトで300Miのrequestをそれぞれ定義する。 名前空間のlimitの合計が、Podやコンテナのlimitの合計よりも小さくなる場合、リソースの競合が起こる可能性があります。その場合、コンテナやPodは作成されません。 LimitRangeに対する競合や変更は、すでに作成済みのリソースに対しては影響しません。 ## {{% heading "whatsnext" %}} より詳しい情報は、[LimitRangerの設計ドキュメント](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md)を参照してください。 制限の使用例については、以下のページを読んでください。 - [名前空間ごとにCPUの最小値と最大値の制約を設定する方法](/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/)。 - [名前空間ごとにメモリーの最小値と最大値の制約を設定する方法](/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace/)。 - [名前空間ごとにCPUのRequestとLimitのデフォルト値を設定する方法](/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/)。 - [名前空間ごとにメモリーのRequestとLimitのデフォルト値を設定する方法](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)。 - [名前空間ごとにストレージ消費量の最小値と最大値を設定する方法](/docs/tasks/administer-cluster/limit-storage-consumption/#limitrange-to-limit-requests-for-storage)。 - [名前空間ごとのクォータを設定する詳細な例](/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/)。 </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
Change:
resources. The scheduler then ranks each valid Node and binds the Pod to a suitable Node. Multiple different schedulers may be used within a cluster; kube-scheduler is the reference implementation. <del> See [scheduling](https://kubernetes.io/docs/concepts/scheduling-eviction/) </del> <ins> See [scheduling](/docs/concepts/scheduling-eviction/) </ins> for more information about scheduling and the kube-scheduler component. ```

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
Selector:     tier=frontend Labels:       app=guestbook tier=frontend <del> Annotations:  kubectl.kubernetes.io/last-applied-configuration: {"apiVersion":"apps/v1","kind":"ReplicaSet","metadata":{"annotations":{},"labels":{"app":"guestbook","tier":"frontend"},"name":"frontend",... </del> <ins> Annotations:  <none> </ins> Replicas:     3 current / 3 desired Pods Status:  3 Running / 0 Waiting / 0 Succeeded / 0 Failed Pod Template: Labels:  tier=frontend Containers: php-redis: <del> Image:        gcr.io/google_samples/gb-frontend:v3 </del> <ins> Image:        us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5 </ins> Port:         <none> Host Port:    <none> Environment:  <none>

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