jiebi/CodeConvo huggingface dataset:
Change:
kubectl get pod liveness-exec ``` <del> The output shows that `RESTARTS` has been incremented: </del> <ins> The output shows that `RESTARTS` has been incremented. Note that the `RESTARTS` counter increments as soon as a failed container comes back to the running state: </ins> ``` NAME            READY     STATUS    RESTARTS   AGE

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 documentation on readiness probes is unclear. It describes how to configure readiness for a single container, but when it comes to the restart behavior, it's not exactly clear, if just the container or the complete pod is restarted: the documentation says: but then command is used to show that the restart counter of the pod has been increased. It is not clear in the documentation, if this restart counter relates to all containers in the pod (meaning that all containers in that pod have been restarted due to failed readiness checks of a single container in that pod) or just a single container in the pod. In the example it does not matter because the pod consists of just a single container. Proposed Solution: Please clarify if a single failing container causes a restart of the whole pod or just of the affected container, and how it relates to the RESTARTS field of the output of the command. Page to Update:
/remove-kind bug This is a request to improve docs; the existing docs are unclear, not wrong. /language en /sig node /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]:
/remove-lifecycle stale
I would like to work on it.
/assign
Change:
metadata: # ... spec: <ins> serviceAccountName: bob-the-bot </ins> containers: - name: nginx image: nginx:1.7.9 <del> serviceAccountName: bob-the-bot </del> ``` Service account bearer tokens are perfectly valid to use outside the cluster and

Discussion:
This is a... [ ] Feature Request [X] Bug Report Problem: Incorrect example at "Service Account Tokens". The documentation states: But in the example the serviceAccountName field has been set in the container field. Proposed Solution: Replace: With: Page to Update:
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. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/lifecycle frozen /remove-lifecycle stale
Change:
name: system:kube-scheduler apiGroup: rbac.authorization.k8s.io --- <ins> apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: my-scheduler-as-volume-scheduler subjects: - kind: ServiceAccount name: my-scheduler namespace: kube-system roleRef: kind: ClusterRole name: system:volume-scheduler apiGroup: rbac.authorization.k8s.io --- </ins> apiVersion: apps/v1 kind: Deployment metadata:

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 steps in tutorial. At the end of it the annotation-second-scheduler POD got into the pending state. Client Version: v1.17.0 Server Version: v1.17.0 Errors visible in my-scheduler POD: Proposed Solution: Remove lock-object-namespace and lock-object-name from There is no lock-object-namespace namespace, hence my-scheduler won't not work properly. In addition to that, add the following lines to clusterrole system:kube-scheduler: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
It looks to me as if ought to tell the reader to add a new namespace to hold lock objects. Does that sound right? /sig scheduling
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
/remove-lifecycle stale
/assign
could you confirm if you were trying to set up leader election or not?
Change:
|    node-1 *drained*  |       node-2        |       node-3       | *no node*          | |:--------------------:|:-------------------:|:------------------:|:------------------:| <del> |                      | pod-b *available*   | pod-c *available*  | pod-e *pending*    | </del> <ins> |                      | pod-b *terminating* | pod-c *available*  | pod-e *pending*    | </ins> |                      | pod-d *available*   | pod-y              |                    | At this point, the cluster administrator needs to

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--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The last table after the paragraph shows that pod-b available, which I think that it's wrong, because previously it says "It will succeed at evicting pod-b" Proposed Solution: pod-b terminating Page to Update:
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
/remove-lifecycle stale
/priority backlog
/kind bug
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
/remove-lifecycle stale
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign
Change:
distros | 배포판 | Docker | 도커 | Dockerfile | Dockerfile | <ins> Docker Swarm | Docker Swarm | </ins> Downward API | 다운워드(Downward) API | draining | 드레이닝(draining) | egress | 이그레스, 송신(egress) |

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. --There are several Vendor's solution names that need to be maintained in the English when localizing documents. So, I suggest this word to be . English --- --- Docker Swarm Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
/language ko
Change:
kubectl version --client --output=yaml ``` <del> 1. After installing the plugin, clean up the installation files: ```powershell del kubectl.exe kubectl.exe.sha256 ``` </del> {{< note >}} [Docker Desktop for Windows](https://docs.docker.com/docker-for-windows/#kubernetes)

Discussion:
I was doing the step-by-step installation for v1.26.3 and found this as the final step for installing on Windows: installing the plugin, clean up the installation files: del Please correct me if I am wrong, but isn't the kube controller that I just installed? It isn't an installer, it's the product. Your instruction should not be to delete it. If I delete then I won't have kubectl installed anymore. Make sense?
/kind bug /language en /triage accepted For Windows, we don't provide our own installable package and the instructions don't explain putting the kubectl binary anywhere special. Until that changes, let's not advise readers to delete .
do we have to comment down or delete the 5th instruction there ?
/assign
Change:
{{< note >}} While any plugin can access the list of "waiting" Pods and approve them <del> (see [`FrameworkHandle`](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md#frameworkhandle)), we expect only the permit </del> <ins> (see [`FrameworkHandle`](https://git.k8s.io/enhancements/keps/sig-scheduling/624-scheduling-framework#frameworkhandle)), we expect only the permit </ins> plugins to approve binding of reserved Pods that are in "waiting" state. Once a Pod is approved, it is sent to the [PreBind](#pre-bind) phase. {{< /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: "FrameworkHandle" link is broken. Proposed Solution: The link should be ( ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /triage accepted
/assign
Change:
{{< feature-state for_k8s_version="v1.5" state="alpha" >}} <del> You can replicate Kubernetes control plane nodes in `kube-up` or `kube-down` scripts for Google Compute Engine. </del> <ins> You can replicate Kubernetes control plane nodes in `kube-up` or `kube-down` scripts for Google Compute Engine. However this scripts are not suitable for any sort of production use, it's widely used in the project's CI. </ins> This document describes how to use kube-up/down scripts to manage a highly available (HA) control plane and how HA control planes are implemented for use with GCE.

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In , and scripts are mentioned. But according to 's , And the in (where the and scripts exist) says that Proposed Solution: ~Update to not mention and scripts.~ Delete and redirect it to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/kind cleanup /triage accepted
/sig cluster-lifecycle (ish)
/reopen The page still mentions those scripts.
Reopened this issue. <detailsIn response to : /reopen 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 think it would probably be best to instead drop all reference to them, we have if we need to document details to upstream contributors, previously we did not and sort of did double-duty IMHO
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]:
Let's delete and redirect it to /lifecycle frozen do you agree with that approach? If so, please update the issue description to highlight it as a plan.
→ Yes! → Done!
/assign
Thanks all.
Change:
</TABLE> </DIV> </DIV> <del> <SCRIPT src="/js/jquery-2.2.0.min.js"></SCRIPT> </del> <ins> <SCRIPT src="/js/jquery-3.2.1.min.js"></SCRIPT> </ins> <SCRIPT src="jquery.scrollTo.min.js"></SCRIPT> <del> <SCRIPT src="/js/bootstrap.min.js"></SCRIPT> </del> <ins> <SCRIPT src="/js/bootstrap-3.3.7.min.js"></SCRIPT> </ins> <SCRIPT src="navData.js"></SCRIPT> <SCRIPT src="scroll.js"></SCRIPT> </BODY>

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--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [ ] Bug Report Problem: api doc reference not working properly due to jquery- and not found. 404 (Not Found) 404 (Not Found) Proposed Solution: put back the missing JS file Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--11 12 13 <!--Additional Information:--
12 works. 1.11 and 1.13 doesn't work.
Change:
Lease | 리스(Lease) | API 오브젝트인 경우 lifecycle | 라이프사이클 | LimitRange | 리밋레인지(LimitRange) | API 오브젝트인 경우 <ins> limit | 한도(limit) | 리소스의 개수나 용량을 한정하기 위한 수치로 사용된 경우 선택적으로 사용 (API 오브젝트의 속성으로 limit을 사용한 경우는 가능한 영문 유지) </ins> Linux | 리눅스 | load | 부하 | LocalSubjectAccessReview | 로컬서브젝트액세스리뷰(LocalSubjectAccessReview) | API 오브젝트인 경우

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: / . '' '' . English | -- | -- Default Limit | Default Request | max limit/request ratio | / Resource Limit | Proposed Solution: / '' '' , . LimitRange API yaml English -- -- Default Limit Default Request max limit/request ratio Resource Limit limit ResourceQuota, LimitRange request ResourceQuota, LimitRange Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
. before : LimitRange after : ResourceQuota, LimitRange LimitRange ResourceQuota .
Change:
To build and test the site locally, run: ```bash <ins> # install dependencies npm ci </ins> make serve ```

Discussion:
This is a Bug Report As discussed in the SIG-Docs meeting, the current steps for building doc website in README is incomplete in the following point of views. It requires yarn on top of npm, but is missing and package- is there. did not work for me but I need further investigation on it. The build step is going to be equal in containerized and local in , but yarn installation or npm ci is currently missing in . <!--Required Information--Proposed Solution: and remove yarn from the dependency the npm command inside of the container Page to Update: N/A
Here's my cat picture after the sig-docs meeting lol !
AIUI, the live website build (within Netlify) relies on , and does not use Yarn.
/area web-development
Could you have a quick look if npm ci in local works just fine?
Yes, I believe so.
worked in my local environment
/kind bug /priority important-longterm
/sig contributor-experience I suppose
Change:
sudo chown root: /usr/local/bin/kubectl ``` <ins> {{< note >}} Make sure `/usr/local/bin` is in your PATH environment variable. {{< /note >}} </ins> 1. Test to ensure the version you installed is up-to-date: ```bash

Discussion:
Hello, I installed Kubernetes using this method "Install kubectl binary with curl on MacOS". In step 5, I get the error "kubectl: command not found". MacOS version: 10.12.6 Could you please give a solution? Regards, Myat
Can you send me the reference document?
/kind support
reference document:
You can run . Check if is in the PATH. !
Let's mention that must be in your . This was a support request, but it's also a hint about how to improve the docs /remove-kind support /language en
/assign
Let me improve it.
/sig node
/remove-sig node
/sig cli
/triage accepted
Change:
``` `periodSeconds` indicates the length of time in the past for which the policy must hold true. <ins> The maximum value that you can set for `periodSeconds` is 1800 (half an hour). </ins> The first policy _(Pods)_ allows at most 4 replicas to be scaled down in one minute. The second policy _(Percent)_ allows at most 10% of the current replicas to be scaled down in one minute.

Discussion:
Facing error HorizontalPodAutoscaler.autoscaling "test" is invalid: spec.behavior.scaleDown.policies[0].periodSeconds: Invalid value: 3600: must be less than or equal to 1800 It is a limitation, I'd like to avoid scaling down a maximum of 1 pod every 1 hour not half an hour Add a scale down policy for a periodSeconds of 1 hour If the issue not resolved, better to modify the documentation to clearly mention that this is a limitation and the maximum value of must be less than or equal half an hour <details</details<detailsAWS EKS </details<details</details<details</details<details</details<details</details
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
For Reference This is a well-thought-out limit set in this PR:
However, mentioning this in yaml or in a note in the Default behaviour section doesn't sound bad. You can raise the issue in for contribution related help please go through t
Let's move this to k/website /transfer website
/sig autoscaling /kind feature /remove-kind bug
/assign
/triage accepted /priority backlog
Change:
{{< feature-state for_k8s_version="v1.16" state="beta" >}} <del> As of Kubernetes v1.16, RuntimeClass includes support for heterogeneous clusters through its `scheduling` fields. Through the use of these fields, you can ensure that pods running with this RuntimeClass are scheduled to nodes that support it. To use the scheduling support, you must have the [RuntimeClass admission controller](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass) enabled (the default, as of 1.16). </del> <ins> By specifying the `scheduling` field for a RuntimeClass, you can set constraints to ensure that Pods running with this RuntimeClass are scheduled to nodes that support it. If `scheduling` is not set, this RuntimeClass is assumed to be supported by all nodes. </ins> To ensure pods land on nodes supporting a specific RuntimeClass, that set of nodes should have a common label which is then selected by the `runtimeclass.scheduling.nodeSelector` field. The

Discussion:
RuntimeClass feature gate is GA in 1.20. According to , a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.
triage/accepted
/language en
/triage accepted
/assign
Change:
[thirdparty_message_vendor] other = """Items on this page refer to vendors external to Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. To add a vendor, product or project to this list, read the <a href="/docs/contribute/style/content-guide/#third-party-content">content guide</a> before submitting a change. <a href="#third-party-content-disclaimer">More information.</a>""" <ins> [translated_by] other = "Translated By" </ins> [ui_search_placeholder] other = "Search this site"

Discussion:
This is a Feature Request What would you like to be In , the "author" metadata was to the front matter. Currently, some l10n teams are also setting "translator" metadata. This is one of the initiatives to promote the localization of blog posts. FYI: I would like to add "translator" metadata to the blog's front matter, just like the author metadata. Why is this needed To promote the localization of blog articles. This would be a significant motivation for those involved in localization. Comments
/area web-development /area blog /area localization
/assign
This is a great idea. It will be very motivating for localization contributors.
Thank you for your interest in this issue, mengjiao-liu ! I've opened a pull request to resolve it - . please have a look :)
Would be nice to add this feature. /priority backlog /triage accepted
Change:
<ins> --- title: 使用 Kind 安装 Kubernetes weight: 40 content_type: concept --- <!-- overview --> <!-- Kind is a tool for running local Kubernetes clusters using Docker container "nodes". --> Kind 是一个使用 Docker 容器“节点”运行本地 Kubernetes 集群的工具。 <!-- body --> <!-- ## Installation See [Installing Kind](https://kind.sigs.k8s.io/docs/user/quick-start/). --> ## 安装  {#installation} 参见[安装 Kind ](https://kind.sigs.k8s.io/docs/user/quick-start/)。 </ins>

Discussion:
This is a Bug Report Problem: is missing in Chinese version. Proposed Solution: Add content/zh/docs/setup/learning- Page to Update: content/zh/docs/setup/learning- content/zh/docs/setup/learning-
/language zh /assign
Change:
The `expiration` field controls the expiry of the token. Expired tokens are rejected when used for authentication and ignored during ConfigMap signing. <del> The expiry value is encoded as an absolute UTC time using RFC3339. Enable the </del> <ins> The expiry value is encoded as an absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339). Enable the </ins> `tokencleaner` controller to automatically delete expired tokens. ## Token Management with kubeadm

Discussion:
This is a Feature Request What would you like to be Add the following hyperlink to under the in reference docs. Why is this needed Adding the hyperlink will help the readers to know about RFC3339. Proposed Solution: Where to add this link: In above code instead of it should be Comments /sig docs /language en
/sig auth /triage accepted /good-first-issue Please save this for a new contributor to the Kubernetes documentation. This is a great opportunity for new contributor to make their first contribution to the k8s project.
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 : /sig auth /triage accepted /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