jiebi/CodeConvo huggingface dataset:
Change:
- lifecycle - livenessProbe - readinessProbe <del> - securityContext </del> - startupProbe - definition: io.k8s.api.core.v1.ReplicationControllerSpec

Discussion:
This is a Bug Report <!--Required Information--Problem: Setting for ephemeral containers is allowed as of Kubernetes 1.22, but it's still showing up as a "not allowed" field here: Proposed Solution: This page looks to be autogenerated based on the API definition, but I'm not sure how it's detecting not allowed fields. If it's automatic we'll correct the metadata or if it's curated then just reclassify the field in docs. Page to Update:
/assign
The fix is likely to happen within
is autogenerated. I don't think received field updates for v1.22
Track the update of the documentation as an issue in this repository. /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]:
Looks like this is still happening, and also is showing up under the alpha heading even though its description says (correctly) that it's beta. This dropped off my radar, but I'll take a look at it in the next few days. /remove-lifecycle stale
/priority critical-urgent
/remove-priority critical-urgent /priority important-soon /sig security you're welcome to make a case for raising it back to critical. What would be the motivation there?
Hi I don't wish to make that case. I was just trying to assign a priority according to guidance and . The documentation is wrong for a core feature, which seems like a "fix it now" rather than "fix it in the next release" priority. The priority isn't important to me, though. Happy for it to be whatever you think is best.
This repo uses continuous deployment (we don't wait for a release for fixes). Anyway, yes, it looks important.
Change:
[弃用](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi)。 更多关于 CSI 制备器的详情，请参阅 [Kubernetes vSphere CSI 驱动](https://vsphere-csi-driver.sigs.k8s.io/) <del> 和 [vSphereVolume CSI 迁移](/zh-cn/docs/concepts/storage/volumes/#csi-migration-5)。 </del> <ins> 和 [vSphereVolume CSI 迁移](/zh-cn/docs/concepts/storage/volumes/#vsphere-csi-migration)。 </ins> <!-- #### CSI Provisioner {#vsphere-provisioner-csi}

Discussion:
stay In the page, the link at the text "vSphereVolume CSI " should be -csi-migration
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/language zh
Are you still working on it?
I submitted PR to solve this issue and put you as the co-author.
Change:
### Allow Volume Expansion <del> {{< feature-state for_k8s_version="v1.11" state="beta" >}} </del> PersistentVolumes can be configured to be expandable. This feature when set to `true`, allows the users to resize the volume by editing the corresponding PVC object.

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:
`--large-cluster-size-threshold` nodes - default 50), then evictions are stopped. - Otherwise, the eviction rate is reduced to `--secondary-node-eviction-rate` (default 0.01) per second. The reason these policies are implemented per availability zone is because one availability zone might become partitioned from the master while the others remain connected. If your cluster does not span multiple cloud provider availability zones,

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: As-is: is rendered like this: ! Proposed Solution: Add a separating blank line. To-be: Page to Update: /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:
<del> # i18n strings for the Vietnamese (main) site. </del> <ins> # Chuỗi i18n cho trang chủ tiếng Việt. [auto_generated_edit_notice] other = "(trang tự động tạo)" [auto_generated_pageinfo] other = """<p>Trang này được tạo tự động.</p><p>Nếu bạn có ý định báo cáo một vấn đề với trang này, hãy đề cập rằng trang này được tạo tự động trong mô tả vấn đề của bạn. Sửa lỗi có thể cần phải xảy ra ở một nơi khác trong dự án Kubernetes.</p>""" </ins> [caution] other = "Chú ý:" [cleanup_heading] <del> other = "Cleaning up" </del> <ins> other = "Dọn dẹp" </ins> [community_events_calendar] other = "Lịch sự kiện"

Discussion:
Đề nghị thay thế "lạc thú" bằng "lỗi thời" !
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
Please raise the issue in english putting the language code before the issue in [] example [vi] Issue title here It will be good practice to write the description and title of the issue in English only.
Thank you! BTW i'd commited about this change, waiting for review.
Fixed in
Change:
title: "bash auto-completion on Linux" description: "Some optional configuration for bash auto-completion on Linux." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- ### Introduction

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 source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Proposed Solution: Edit every file within : Page to Update: and its contents /area web-development /help /priority backlog /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 source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Edit every file within : Page to Update: and its contents /help /priority backlog /good-first-issue </details
/retitle Include files for install are rendered and served /triage accepted
/assign
/unassign
Thanks !
Change:
These controllers include: <del> * Node Controller * Responsible for noticing & responding when nodes go down. * Replication Controller * Responsible for maintaining the correct number of pods for every replication controller object in the system. * Endpoints Controller * Populates the Endpoints object (i.e., join Services & Pods). * Service Account & Token Controllers * Create default accounts and API access tokens for new namespaces. </del> <ins> * Node Controller: Responsible for noticing & responding when nodes go down. * Replication Controller: Responsible for maintaining the correct number of pods for every replication controller object in the system. * Endpoints Controller: Populates the Endpoints object (i.e., join Services & Pods). * Service Account & Token Controllers: Create default accounts and API access tokens for new namespaces. </ins> * ... and others. ### kube-scheduler

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: There is an extra . ! Proposed Solution: remove and regenerate document. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
[options_heading] other = "Options" <ins> [outdated_blog__message] other = "The Kubernetes project considers this article to be outdated because it is more than one year old. Check that the information in the page has not become incorrect since its publication." [outdated_blog__title] other = "Outdated article" </ins> [post_create_issue] other = "Create an issue"

Discussion:
ref: , but this is also just a general feature! Blog posts by their nature go stale over time. This becomes particularly problematic when we decide to deprecate functionality in the project, as those blog posts are forever a part of the docs and forever searchable via Google. Update the blog post's templates (probably , but you may need to copy over from the Docsy theme) to include a warning for blog posts over 1 year old: Some notes: Use standard docsy warning block styles Make sure strings are in localization files so the localization teams know where to look /triage accepted /priority important-soon /area website
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : ref: , but this is also just a general feature! Some notes: Make sure strings are in localization files so the localization teams know where to look /triage accepted /priority important-soon /area website 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
/area web-development
Sorry y'all, I hadn't seen this issue before I created . It turns out that there's a clean solution that doesn't involve changes to the blog template. Anyhow, this has been /cc
/close Thanks
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

From : The comment was made in the context of the Dockershim-removal effort. I'm opening this PR following discussions with The warning, which would appear only on posts that are = 1 year old, might read something like this: Comments are welcome. /cc
I'm glad to work on this, though it might not happen until January.
Good idea /area web-development I suggest borrowing the styling from .
/triage accepted
/assign I don't know if the command above will work. If it doesn't or can you assign this to me? I've started working on this now.
Thanks (and the looks to have worked )
/triage duplicate
Change:
指向该域名服务器，而不是 `/etc/resolv.conf`。 ``` <del> proxy .  172.16.0.1 </del> <ins> forward .  172.16.0.1 </ins> ``` <!--

Discussion:
Please replace the code from to please kindly check the mistake in below link
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 zh
/good-first-issue
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 : /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
Change:
To mitigate the above situation, a  user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) <del> is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint, the </del> <ins> is enabled on {{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}}, and a Node is marked out-of-service with this taint, the </ins> pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node.

Discussion:
This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :
/sig docs / language en /assign
If triage is accepted, i would be happy to contribute on it. PTAL.
/language en Fixed here .
/triage accepted
Change:
{{ $textArg := .Get "text" }} {{ $page := site.GetPage "page" (printf "%s/%s" $base $pageArg) }} {{ $metadata := $page.Params.api_metadata }} <del> <a href="{{ $page.URL }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a> </del>  No newline at end of file <ins> <a href="{{ $page.RelPermalink }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a> </ins>  No newline at end of file

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: I followed the section "Running the website locally using Hugo" in README of this repo, but I met an error. With Ubuntu 18.04 desktop amd64 the latest commit of this repo () Docsy whose version is the same as of (docsy @ ) npm version: 6.14.15 node version: v14.18.1 go version go1.17.3 linux/amd64 hugo v0.96.0-+extended linux/amd64 BuildDate=2022-03-26T09:15:58Z VendorInfo=mage Docker Client/Server: 20.10.11 [How to reproduce] Proposed Solution:
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
The version of Hugo that we support is as declared in : 0.87.0 Try using Hugo 0.87.0 Pull requests to adopt a newer Hugo version are welcome.
Following comment, I confirmed that this error does not occur with Hugo 0.87.0. After doing some testing, it seems that the field is accessible with Hugo 0.87.0, but not with Hugo 0.96.0 (and maybe with some other versions too). (I tried to find Hugo changelog that says field of is deprecated in what Hugo version, but I could not find.) Suggested solution: Instead of field, if we use , I checked locally that it seems working.

[] How I checked: In page (http://localhost:1313/docs/concepts/workloads/controllers/cron-jobs/#what-s-next), the link goes to http://localhost:1313/docs/reference/kubernetes-api/workload-resources/cron-job-v1/ , for these cases: (As-is) , with Hugo 0.87.0 (To-be) , with Hugo 0.87.0 (To-be) , with Hugo 0.96.0 /area web-development
/assign
Change:
* spec: Invalid value: map[string]interface {}{"maxReplicas":10, "minReplicas":0, "replicas":20}: failed rule: self.replicas <= self.maxReplicas ``` <ins> {{< note >}} You can quickly test CEL expressions in [CEL Playground](https://playcel.undistro.io). {{< /note >}} </ins> Validation rules are compiled when CRDs are created/updated. The request of CRDs create/update will fail if compilation of validation rules fail. Compilation process includes type checking as well.

Discussion:
Hello there, I would like to suggest adding a link to the CEL Playground in the Kubernetes documentation. CEL (Common Expression Language) is used in Kubernetes APIs, such as the , and the CEL Playground can help users easily test expressions. The playground also includes a set of examples and the . I believe the link would be useful on the following pages: The CEL Playground is available at and the source code can be found at I also invite you to test and contribute to the project. Thank you.
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/sig docs
/transfer website The repo is not quite the right place to track this.
/language en /kind feature
If we add a link, I would add it to: (and I wouldn't add it to the reference page ; instead, we can have link to the three pages I listed above)
/wg api-expression
@ Hey which particular points on these links would you want the CEL playground. I will be glad for more clarification on this?
IMHO, a mention similar to the mention of on the would help: but saying that users can quickly test CEL expressions in the playground.
Hi I've opened a PR () with some suggestions for adding the CEL Playground link. Please take a look and let me know your thoughts. Inviting to share their thoughts as well.
I'm supportive of this. It's a wonderful tool and the community will benefit from being more aware of it.
/triage accepted
Change:
--- 本ウェブサイトには、現行版とその直前4バージョンのKubernetesドキュメントがあります。 <ins> Kubernetesバージョンのドキュメントの入手性は、そのリリースが現在サポートされているかどうかで分かれます。 どのKubernetesバージョンが公式にどのくらいの期間サポートされるかについて知るには、[サポート期間](/releases/patch-releases/#support-period)を参照してください。 </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. --Update translation /ja/docs/home/supported-doc-versions to current English version Tue May 31 06:54:51 2022 +0600 Why is this needed fix outdated doc 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:
Details of the metric data that Kubernetes components export. --- <del> ## Metrics (v1.29) </del> <ins> ## Metrics (v1.28) </ins> <del> <!-- (auto-generated 2023 Sep 06) --> <!-- (auto-generated v1.29) --> </del> <ins> <!-- (auto-generated 2023 Jul 20) --> <!-- (auto-generated v1.28) --> </ins> This page details the metrics that different Kubernetes components export. You can query the metrics endpoint for these components using an HTTP scrape, and fetch the current metrics data in Prometheus format.

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: says that it is for Kubernetes v1.29, which has yet to be released. Proposed Solution: Revise to cover v1.28 metrics Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: We should fix this before the v1.29 release. /priority important-soon /sig instrumentation /language en /triage accepted
Upon some investigation, I can see the generation of 1.29 metrics on one of my old PRs; Please refer If reverting to an older version of this file helps, Let's do that. I'll make amendments for the formatting once again Alternatively, We can try some experimenting with git history and make a PR which generates 1.28 metrics, With the formatting in place. That should work too (I'd prefer doing this)
I can take this.
/assign
Given the timeline, please mention in the PR and also request a review specifically from me. Whoever gets to it first can pick up the review work.
any advice for about how to approach this?
Sure, Here's my advice These metrics are generated over at Part of the work here includes figuring out where the generation went from 1.28 to 1.29 If you're able to do that, We can revert to the point where 1.28 metrics were generated Given the timeline of docs 1.29 release, If that's not possible in this timeframe, We should revert would you like to add anything else?
Thanks, I will see that, btw can i know what's the timeline?
I believe the release is on 5th December
I found that due to commit which was made by bot on 6-9-23, changed the version from 1.28 to 1.29. If we revert this than the issue will be resolved. //
That's the code we adopted in can we revert this PR for the docs at the time of 1.29 release while keeping the generator at k8s/k8s, the same? After the release we can sync back from k8s/k8s
Yeah, this can work too
I think that's reasonable.

I believe now is a good time to revert that PR (only reverting the markdown changes would be fine)
Sure
you mean reverting completely this PR -
Yes that's correct