jiebi/CodeConvo huggingface dataset:
Change:
Problem: Output from the example on this page is incorrect. Proposed Solution: Fix example to show the correct output. Page to Update: Additional Information: There has been some confusion about how the works in Kubernetes. The output from this example is incorrect and it implies that the API server returns at the top of the output. In reality, the API server doesn't implement . It is kubectl that adds to the end of the output as a means of rendering it. Here is the output that returned when I ran the commands on this page:
Thanks for the reporting the bug and clear explanation! I will fix the doc. /triage accepted /assign
Thanks for taking that on, . For anyone interested in a discussion of , I'm working on some larger writing to describe that and related list types (PodList, ServiceList, etc.). See .
Thanks for writting the larger topic for the List. I close this issue since the larger topic is tracked in another issue. /close
Closing this issue. <detailsIn response to : Thanks for writting the larger topic for the List. I close this issue since the larger topic is tracked in another issue. /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
Thanks for taking care of this issue so quickly! I was happy to see that it had published when I looked at it today.

Discussion:
```yaml apiVersion: v1 <del> kind: List </del> items: - apiVersion: stable.example.com/v1 kind: CronTab metadata: <del> creationTimestamp: 2017-05-31T12:56:35Z </del> <ins> annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"stable.example.com/v1","kind":"CronTab","metadata":{"annotations":{},"name":"my-new-cron-object","namespace":"default"},"spec":{"cronSpec":"* * * * */5","image":"my-awesome-cron-image"}} creationTimestamp: "2021-06-20T07:35:27Z" </ins> generation: 1 name: my-new-cron-object namespace: default <del> resourceVersion: "285" uid: 9423255b-4600-11e7-af6a-28d2447dc82b </del> <ins> resourceVersion: "1326" uid: 9aab1d66-628e-41bb-a422-57b8b3b1f5a9 </ins> spec: cronSpec: '* * * * */5' image: my-awesome-cron-image <ins> kind: List </ins> metadata: resourceVersion: "" <ins> selfLink: "" </ins> ``` ## Delete a CustomResourceDefinition
Change:
In the section of There is no file with the specified URL, and the output of running this command is:
In PR the is deleted, which is used in the 'Creating MongoDB deployment and service' page. /kind bug
/triage accepted /retitle Example missing from Use Port Forwarding to Access Applications in a Cluster
/assign will add these yaml's
Fix it here

Discussion:
1. Create a Deployment that runs MongoDB: ```shell <del> kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-deployment.yaml </ins> ``` The output of a successful command verifies that the deployment was created:

2. Create a Service to expose MongoDB on the network: ```shell <del> kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-service.yaml </ins> ``` The output of a successful command verifies that the Service was created:

<ins> apiVersion: apps/v1 kind: Deployment metadata: name: mongo labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: selector: matchLabels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend replicas: 1 template: metadata: labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: containers: - name: mongo image: mongo:4.2 args: - --bind_ip - 0.0.0.0 resources: requests: cpu: 100m memory: 100Mi ports: - containerPort: 27017 </ins>

<ins> apiVersion: v1 kind: Service metadata: name: mongo labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: ports: - port: 27017 targetPort: 27017 selector: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend </ins>
Change:
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.

Discussion:
{{< 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.
Change:
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 Update to have an extra link in it's What's Next section, pointing at Why is this needed The is very relevant to people reading about the operator pattern. Comments /language en /kind feature
/good-first-issue /triage accepted
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 /triage accepted 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 I can work on this.
Fixed it here

Discussion:
## {{% heading "whatsnext" %}} <ins> * Read the {{< glossary_tooltip text="CNCF" term_id="cncf" >}} [Operator White Paper](https://github.com/cncf/tag-app-delivery/blob/eece8f7307f2970f46f100f51932db106db46968/operator-wg/whitepaper/Operator-WhitePaper_v1-0.md). </ins> * Learn more about [Custom Resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) * Find ready-made operators on [OperatorHub.io](https://operatorhub.io/) to suit your use case * [Publish](https://operatorhub.io/) your operator for other people to use
Change:
Nope, when you press Ctrl+C after running the dashboard stops working.
Thanks for the first issue here! By saying "when you press Ctrl+C after running minikube dashboard the dashboard stops working", do you mean the web browser cannot access the dashboard page after Ctrl+C? This is the expected behavior. After the proxy is stopped, the current web browser session stops working. But the dashboard server is still running in the background, you can open another proxy connection to access it again. I can try to improve the doc if the original sentence confuses new learners.
Hello, From a user perspective the dashboard is unusable after Ctrl+C and if you start it again it’s on a different port so it looks very mich like it’s stopped. The real question is why starting the dashboard should block the CLI like this. I’d say the behaviour is unnecessarily confusing for beginners and the documentation compounds this.
Let me improve the doc to clarify this. /triage accepted /kind feature
/assign

Discussion:
4. Katacoda environment only: Type `30000`, and then click **Display Port**. {{< note >}} <del> The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. </del> <ins> The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. </ins> If you are running in an environment as root, see [Open Dashboard with URL](#open-dashboard-with-url). <del> To stop the proxy, run `Ctrl+C` to exit the process. The dashboard remains running. </del> <ins> By default, the dashboard is only accessible from within the internal Kubernetes virtual network. The `dashboard` command creates a temporary proxy to make the dashboard accessible from outside the Kubernetes virtual network. To stop the proxy, run `Ctrl+C` to exit the process. After the command exits, the dashboard remains running in Kubernetes cluster. You can run the `dashboard` command again to create another proxy to access the dashboard. </ins> {{< /note >}} ## Open Dashboard with URL
Change:
This is a Bug Report Problem: There is incorrectly translated content in docs/concepts/storage/volumes/#hostpath . in English: in Korean: Proposed Solution: Page to Update:
/kind bug /language ko
/triage accepted

Discussion:
| | 빈 문자열 (기본값)은 이전 버전과의 호환성을 위한 것으로, hostPath 볼륨은 마운트 하기 전에 아무런 검사도 수행되지 않는다. | | `DirectoryOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0755로 설정한 빈 디렉터리를 생성한다. | | `Directory` | 주어진 경로에 디렉터리가 있어야 함 | <del> | `FileOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0644로 설정한 빈 디렉터리를 생성한다. | </del> <ins> | `FileOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0644로 설정한 빈 파일을 생성한다. | </ins> | `File` | 주어진 경로에 파일이 있어야 함 | | `Socket` | 주어진 경로에 UNIX 소캣이 있어야 함 | | `CharDevice` | 주어진 경로에 문자 디바이스가 있어야 함 |
Change:
Typo in frensh Statefulset documentation: Garanties de déploiment et de mise à l'échelle -Garanties de déploiement et de mise à l'échelle
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
/kind bug /language fr
/assign

Discussion:
il ajoute une étiquette, `statefulset.kubernetes.io/pod-name`, renseignée avec le nom du Pod. Cette étiquette vous permet d'attacher un Service à un Pod spécifique du StatefulSet. <del> ## Garanties de déploiment et de mise à l'échelle </del> <ins> ## Garanties de déploiement et de mise à l'échelle </ins> * Pour un StatefulSet avec N réplicas, lorsque les Pods sont déployés, ils sont créés de manière séquentielle, dans l'ordre {0..N-1}. * Lorsque les Pods sont supprimés, ils sont terminés dans l'ordre inverse, {N-1..0}.
Change:
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 this page, there is a "hook" link. However, #hook-details doesn't exist in /docs/concepts/containers/container-lifecycle-hooks/. Proposed Solution: The link would 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 /sig node /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /sig node /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
as terminating (a graceful shutdown duration has been set), the kubelet begins the local Pod shutdown process. 1. If one of the Pod's containers has defined a `preStop` <del> [hook](/docs/concepts/containers/container-lifecycle-hooks/#hook-details), the kubelet </del> <ins> [hook](/docs/concepts/containers/container-lifecycle-hooks), the kubelet </ins> runs that hook inside of the container. If the `preStop` hook is still running after the grace period expires, the kubelet requests a small, one-off grace period extension of 2 seconds.
Change:
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 Mention the within , or link to it. Why is this needed Readers might have an interest in knowing how security fixes are planned and communicated. Comments /sig release /sig security /language en /kind feature
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 I can work on this.
Hi Please suggest which option from the following I will go with In this, we will have to make a page for embargo policy(security-embargo-) as we do not mention the link directly. 1) Copy the whole content from the to security-embargo- which seems redudant as it already mention in kubernete/security. 2) Mention the below text and then the link to for more details like:
I can clarify: this issue is about explaining that some information about upcoming releases is subject to embago, and that there is a defined policy about how those embargos are set. I don't see a need to mention how to join the mailing list for distributors within If someone is maintaining a Kubernetes distribution, I hope they're able to follow hyperlinks well enough to work that out. We have readers who might not think to look there. That's why we should refer to it (a hyperlink could be OK).
Thanks for suggestion. will create a pr for it soon.
fixed it here:

Discussion:
The responsibilities of each role are described below. - [Contact](#contact) <ins> - [Security Embargo Policy](#security-embargo-policy) </ins> - [Handbooks](#handbooks) - [Release Managers](#release-managers) - [Becoming a Release Manager](#becoming-a-release-manager)

| [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | N/A | Private | Private discussion for privileged Release Managers | Release Managers, SIG Release leadership | | [security-release-team@kubernetes.io](mailto:security-release-team@kubernetes.io) | [#security-release-team](https://kubernetes.slack.com/archives/G0162T1RYHG) (channel) / @security-rel-team (user group) | Private | Security release coordination with the Product Security Committee | [security-discuss-private@kubernetes.io](mailto:security-discuss-private@kubernetes.io), [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | <ins> ### Security Embargo Policy Some information about releases is subject to embargo and we have defined policy about how those embargos are set. Please refer [Security Embargo Policy](https://github.com/kubernetes/security/blob/master/private-distributors-list.md#embargo-policy) here for more information. </ins> ## Handbooks **NOTE: The Patch Release Team and Branch Manager handbooks will be de-duplicated at a later date.**
Change:
suggests: Do changes, then The output is equivalent to the previous run of . I do not see, how this output can confirm, that the Deployment was updated.
Welcome and thanks for contributing your first issue here! This sentence does seem confusing to me. I will improve it. /triage accepted /kind bug /assign
/sig apps
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:

Discussion:
apply multiple fixes in between pausing and resuming without triggering unnecessary rollouts. * For example, with a Deployment that was created: Get the Deployment details: ```shell kubectl get deploy

REVISION  CHANGE-CAUSE 1   <none> ``` <del> * Get the rollout status to ensure that the Deployment is updated successfully: </del> <ins> * Get the rollout status to verify that the existing ReplicaSet has not changed: </ins> ```shell kubectl get rs ```
Change:
This is a Bug Report <!--Required Information--Problem: There are both a raw untranslated sentence and its translated sentence. Proposed Solution: remove this raw sentence Page to Update:
/assign
/triage accepted

Discussion:
cat ./kubectl-whoami ``` 次の例では、下記の内容を含んだ`kubectl-whoami`が既に作成済であることを前提としています。 <del> The next few examples assume that you already made `kubectl-whoami` have the following contents: </del> ```shell #!/bin/bash
Change:
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 - , number is wrong in numbered list. ! Proposed Solution: Fix indent in Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind cleanup /language ko /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In - , number is wrong in numbered list. Fix indent in - <!--Kubernetes Version:--/language ko /good-first-issue </details
/assign
GitHub didn't allow me to assign the following users: yuswift. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
/triage accepted

Discussion:
1. `kubernetes/website` 리포지터리 내 [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/master/OWNERS) 파일의 섹션에 여러분의 GitHub 사용자 이름을 추가하는 풀 리퀘스트를 연다. <del> {{< note >}} 자신을 추가할 위치가 확실하지 않으면, `sig-docs-ko-reviews` 에 추가한다. {{< /note >}} 1. PR을 하나 이상의 SIG-Docs 승인자(`sig-docs-{language}-owners` 에 </del> <ins> {{< note >}} 자신을 추가할 위치가 확실하지 않으면, `sig-docs-ko-reviews` 에 추가한다. {{< /note >}} 2. PR을 하나 이상의 SIG-Docs 승인자(`sig-docs-{language}-owners` 에 </ins> 나열된 사용자 이름)에게 지정한다. 승인되면, SIG Docs 리더가 적당한 GitHub 팀에 여러분을 추가한다. 일단 추가되면,
Change:
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: Pod / Service names can not start with an alphanumeric character in kubernetes, but should be possible according to RFC1123 Proposed Solution: Change documentation in sections and to: or change kubernetes name check to use the specification in RFC1123. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 19.11 <!--Additional Information:--
Kubernetes does not strictly follow the RFC.
this might be true, but the documentation says otherwise. eg.
According to the validation logic, starting with alphanumeric characters should be okay. Can you paste the error message you have got?
I tried locally, and getting this error !
Just double checked the validation logic for core v1 Service. Its name must be a RFC1035 label rather than a RFC1123 label. This is something we need to fix in the docs. Related code:
/triage accepted /kind bug /assign

Discussion:
In cases when objects represent a physical entity, like a Node representing a physical host, when the host is re-created under the same name without deleting and re-creating the Node, Kubernetes treats the new host as the old one, which may lead to inconsistencies. {{< /note >}} <del> Below are three types of commonly used name constraints for resources. </del> <ins> Below are four types of commonly used name constraints for resources. </ins> ### DNS Subdomain Names

- start with an alphanumeric character - end with an alphanumeric character <del> ### DNS Label Names </del> <ins> ### RFC 1123 Label Names {#dns-label-names} </ins> Some resource types require their names to follow the DNS label standard as defined in [RFC 1123](https://tools.ietf.org/html/rfc1123).

- start with an alphanumeric character - end with an alphanumeric character <ins> ### RFC 1035 Label Names Some resource types require their names to follow the DNS label standard as defined in [RFC 1035](https://tools.ietf.org/html/rfc1035). This means the name must: - contain at most 63 characters - contain only lowercase alphanumeric characters or '-' - start with an alphabetic character - end with an alphanumeric character </ins> ### Path Segment Names Some resource types require their names to be able to be safely encoded as a

REST objects, you can `POST` a Service definition to the API server to create a new instance. The name of a Service object must be a valid <del> [DNS label name](/docs/concepts/overview/working-with-objects/names#dns-label-names). </del> <ins> [RFC 1035 label name](/docs/concepts/overview/working-with-objects/names#rfc-1035-label-names). </ins> For example, suppose you have a set of Pods where each listens on TCP port 9376 and contains a label `app=MyApp`: