jiebi/CodeConvo huggingface dataset:
Change:
The  group in OWNERSALIASES is a historical artifact with no permissions associated with it. Remove the team from OWNERS_ALIASES. I'm also proposing to update the description of from "Website admins" to "Website chairs and tech leads" and add and to the group. For more information, see We need to update the to replace with I propose continuing to limit repo admin access to current chairs. /assign

Discussion:
- ianychoi - seokho-son - ysyukr <del> sig-docs-maintainers: # Website maintainers </del> <ins> sig-docs-leads: # Website chairs and tech leads </ins> - jimangel - kbarnard10 <del> - pwittrock - steveperry-53 </del> <ins> - kbhawkey - onlydole - sftim </ins> - zacharysarah <del> - zparnold </del> sig-docs-zh-owners: # Admins for Chinese content - chenopis - chenrui333

[build] # This default build command adds the robots noindex directive to the site headers. # It is turned off for only for the production site by using [context.master] below <del> # DO NOT REMOVE THIS (contact @chenopis or @sig-docs-maintainers) </del> <ins> # DO NOT REMOVE THIS (contact @kubernetes/sig-docs-leads) </ins> publish = "public" functions = "functions" command = "make non-production-build"

[context.master] # This context is triggered by the `master` branch and allows search indexing <del> # DO NOT REMOVE THIS (contact @chenopis or @sig-docs-maintainers) </del> <ins> # DO NOT REMOVE THIS (contact @kubernetes/sig-docs-leads) </ins> publish = "public" command = "make production-build"
Change:
hellothere is a possible mistake at "Joining your nodes" section ! ! have you wrongly written "port" to "ip" ?
hi, yes this seems wrong. do you wish to send a PR to fix it? /sig cluster-lifecycle /help
sorry…i just find this mistake during learning, but i don't know how to fix it...(i am a novice to github and k8s…)
/assign
/remove-help
- I would like to help with such doc issues for sig/cluster-lifecycle.
thanks i can ping on new tickets. you can also watch the sig/cluster-lifecycle label in this repo.

Discussion:
``` {{< note >}} <del> To specify an IPv6 tuple for `<control-plane-host>:<control-plane-ip>`, IPv6 address must be enclosed in square brackets, for example: `[fd00::101]:2073`. </del> <ins> To specify an IPv6 tuple for `<control-plane-host>:<control-plane-port>`, IPv6 address must be enclosed in square brackets, for example: `[fd00::101]:2073`. </ins> {{< /note >}} The output should look something like:
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: '' . . . Proposed Solution: . . - . : - . Minikube : /ko/docs/setup/learning-environment/minikube/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ko /assign

Discussion:
쿠버네티스 클러스터가 필요하고, kubectl 커맨드-라인 툴이 클러스터와 <del> 통신할 수 있도록 설정되어 있어야 합니다. </del> <ins> 통신할 수 있도록 설정되어 있어야 한다. </ins> 만약, 아직 클러스터를 가지고 있지 않다면, <del> [Minikube](/docs/setup/learning-environment/minikube/)를 사용해서 만들거나, 다음의 쿠버네티스 플레이그라운드 중 하나를 사용할 수 있습니다: </del> <ins> [Minikube](/ko/docs/setup/learning-environment/minikube/)를 사용해서 생성하거나, 다음의 쿠버네티스 플레이그라운드 중 하나를 사용할 수 있다. </ins> * [Katacoda](https://www.katacoda.com/courses/kubernetes/playground) * [Play with Kubernetes](http://labs.play-with-k8s.com/)
Change:
This is a Bug Report Problem: The reference documentation for kubectl v1.18 does not match the implementation regarding command and its options and . Proposed Solution: Update the reference docs. Pages to Update: , the sections for options replicas and restart are incorrect. The option is depreciated and always creates a pod regardless of the , the following line: The option is depreciated.
/assign
Thanks for contributing

Discussion:
`port-forward`    | `kubectl port-forward POD [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]` | Forward one or more local ports to a pod. `proxy`        | `kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix] [flags]` | Run a proxy to the Kubernetes API server. `replace`        | `kubectl replace -f FILENAME` | Replace a resource from a file or stdin. <del> `run`        | </code>kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=server&#124;client&#124;none] [--overrides=inline-json] [flags]</code> | Run a specified image on the cluster. </del> <ins> `run`        | <code>kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server&#124;client&#124;none] [--overrides=inline-json] [flags]</code> | Run a specified image on the cluster. </ins> `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. `version`        | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
Change:
This is a Feature Request The task page, refers to the feature state as reaching beta in , however, the text in the task page refers to the version as . What would you like to be Confirm when the feature reached beta and adjust the text on the page. Why is this needed The content is not consistent. Comments Let me know if you need help resolving this issue.
/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 : /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
/assign

Discussion:
--- {{% capture overview %}} <del> {{< feature-state state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.10" state="beta" >}} </ins> A subset of the Kubelet's configuration parameters may be set via an on-disk config file, as a substitute for command-line flags.
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: describes the API List Chunking feature. However, this is a beta feature. Proposed Solution: Warn readers that this feature is not yet stable, using a Hugo shortcode. You can look up when the feature went beta from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 /sig api-machinery
/assign

Discussion:
`Bookmark` events can be requested by `allowWatchBookmarks=true` option in watch requests, but clients shouldn't assume bookmarks are returned at any specific interval, nor may they assume the server will send any `bookmark` event. ## Retrieving large results sets in chunks <ins> {{< feature-state for_k8s_version="v1.9" state="beta" >}} </ins> On large clusters, retrieving the collection of some resource types may result in very large responses that can impact the server and client. For instance, a cluster may have tens of thousands of pods, each of which is 1-2kb of encoded JSON. Retrieving all pods across all namespaces may result in a very large response (10-20MB) and consume a large amount of server resources. Starting in Kubernetes 1.9 the server supports the ability to break a single large collection request into many smaller chunks while preserving the consistency of the total request. Each chunk can be returned sequentially which reduces both the total size of the request and allows user-oriented clients to display results incrementally to improve responsiveness.
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: Documentation - description is not fully inline with current version. Current text: "Non-resource paths include: /api, /apis, /metrics, /resetMetrics, /logs, /debug, /healthz, /swagger-ui/, /swaggerapi/, /ui, and /version." The following non-resource don't seem to exist anymore: '/resetMetrics', '/swagger-ui' ( swagger 1.2 was deprecated and functionality seems it was already removed), '/swaggerapi'. The non-resource path '/ui' would need more checking, but it seems is part only of some tests. Proposed Solution: Description should be updated accordingly. For example, the text could be updated as: "Non-resource paths include: /api, /apis, /metrics, /logs, /debug, /healthz, /livez, /openapi/v2, /readyz and /version." Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--{ "gitVersion": "v1.18.2", "gitCommit": "" } <!--Additional Information:--
/assign
/priority important-longterm /language en
/kind bug

Discussion:
} ``` <del> Non-resource paths include: `/api`, `/apis`, `/metrics`, `/resetMetrics`, `/logs`, `/debug`, `/healthz`, `/swagger-ui/`, `/swaggerapi/`, `/ui`, and </del> <ins> Non-resource paths include: `/api`, `/apis`, `/metrics`, `/logs`, `/debug`, `/healthz`, `/livez`, `/openapi/v2`, `/readyz`, and </ins> `/version.` Clients require access to `/api`, `/api/*`, `/apis`, `/apis/*`, and `/version` to discover what resources and versions are present on the server. Access to other non-resource paths can be disallowed without restricting access

For further documentation refer to the authorization.v1beta1 API objects and [webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go).
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: does not mention that PodDisruptionBudget is beta. Proposed Solution: Add a shortcode to Page to Update: There may well be other pages that describe PodDisruptionBudget without mentioning its feature state. <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 <!--Additional Information:--/help /kind bug /priority backlog
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: does not mention that PodDisruptionBudget is beta. Add a shortcode to There may well be other pages that describe PodDisruptionBudget without mentioning its feature state. Kubernetes Version: v1.18 /help /kind bug /priority backlog 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 don't see on this page -
Looks like it is since .
/assign

Discussion:
## How Disruption Budgets Work <ins> {{< feature-state for_k8s_version="v1.5" state="beta" >}} </ins> An Application Owner can create a `PodDisruptionBudget` object (PDB) for each application. A PDB limits the number of pods of a replicated application that are down simultaneously from voluntary disruptions.  For example, a quorum-based application would

{{% capture overview %}} <ins> {{< feature-state for_k8s_version="v1.5" state="beta" >}} </ins> This page shows how to limit the number of concurrent disruptions that your application experiences, allowing for higher availability while permitting the cluster administrator to manage the clusters
Change:
Problem: The page is missing the Cleaning up topic Proposed Solution: Add the commands that delete the created services and deployments Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign

Discussion:
{{% /capture %}} <ins> {{% capture cleanup %}} To delete the Services, enter this command: kubectl delete services frontend hello To delete the Deployments, the ReplicaSets and the Pods that are running the backend and frontend applications, enter this command: kubectl delete deployment frontend hello {{% /capture %}} </ins> {{% capture whatsnext %}}
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: After creating and scaling deployment using command kubectl create deployment cattle -- kubectl scale deployment cattle --replicas=5 When we execute below command to list pods with options -l kubectl get pods -l run=cattle O/P is No resources found in production namespace. Proposed Solution: kubectl get pods -l app=cattle Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
can you / have you confirmed that this is a bug? If so, it's be good to record this issue as /kind bug
Yes, this is a bug. When was changed to , the label should have changed from to . This needs to be updated on a couple of other pages as well. /kind bug
/priority backlog

Discussion:
``` ```shell <del> kubectl get pods -l run=snowflake </del> <ins> kubectl get pods -l app=snowflake </ins> ``` ``` NAME                         READY     STATUS    RESTARTS   AGE

``` ```shell <del> kubectl get pods -l run=cattle </del> <ins> kubectl get pods -l app=cattle </ins> ``` ``` NAME                      READY     STATUS    RESTARTS   AGE

To demonstrate this, let's spin up a simple Deployment and Pods in the `development` namespace. ```shell <del> kubectl create deployment snowflake --image=k8s.gcr.io/serve_hostname  -n=development </del> <ins> kubectl create deployment snowflake --image=k8s.gcr.io/serve_hostname -n=development </ins> kubectl scale deployment snowflake --replicas=2 -n=development ``` We have just created a deployment whose replica size is 2 that is running the pod called `snowflake` with a basic container that just serves the hostname. <del> Note that `kubectl run` creates deployments only on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/reference/generated/kubectl/kubectl-commands/#run) for more details. </del> ```shell kubectl get deployment -n=development

snowflake    2/2     2            2           2m ``` ```shell <del> kubectl get pods -l run=snowflake -n=development </del> <ins> kubectl get pods -l app=snowflake -n=development </ins> ``` ``` NAME                         READY     STATUS    RESTARTS   AGE

Production likes to run cattle, so let's create some cattle pods. ```shell <del> kubectl run cattle --image=k8s.gcr.io/serve_hostname --replicas=5 -n=production </del> <ins> kubectl create deployment cattle --image=k8s.gcr.io/serve_hostname -n=production kubectl scale deployment cattle --replicas=5 -n=production </ins> kubectl get deployment -n=production ```

``` ```shell <del> kubectl get pods -l run=cattle -n=production </del> <ins> kubectl get pods -l app=cattle -n=production </ins> ``` ``` NAME                      READY     STATUS    RESTARTS   AGE
Change:
HTML breaks on this page: Related to Hugo version upgrade in
After investigating, it appears that the table is breaking partly because the caption shortcode was . The originating PR was by That said, even refactoring the table for whitespace doesn't fix the error; only removing the shortcode does. I'll open a PR for others to experiment. UPDATE: Works fine.

Discussion:
an illustrative collection of numbers of elephants. See https://play.golang.org/p/Gi0PLgVHiUg , which computes this table. <del> {{< table caption="Example Shuffle Sharding Configurations" >}} |HandSize|     Queues|	1 elephant|		4 elephants|		16 elephants| |--------|-----------|------------|----------------|--------------------| |      12|         32|	4.428838398950118e-09|	0.11431348830099144|	0.9935089607656024| |      10|         32|	1.550093439632541e-08|	0.0626479840223545|	0.9753101519027554| |      10|         64|	6.601827268370426e-12|	0.00045571320990370776|	0.49999929150089345| |       9|         64|	3.6310049976037345e-11|	0.00045501212304112273|	0.4282314876454858| |       8|         64|	2.25929199850899e-10|	0.0004886697053040446|	0.35935114681123076| |       8|        128|	6.994461389026097e-13|	3.4055790161620863e-06|	0.02746173137155063| |       7|        128|	1.0579122850901972e-11|	6.960839379258192e-06|	0.02406157386340147| |       7|        256|	7.597695465552631e-14|	6.728547142019406e-08|	0.0006709661542533682| |       6|        256|	2.7134626662687968e-12|	2.9516464018476436e-07|	0.0008895654642000348| |       6|        512|	4.116062922897309e-14|	4.982983350480894e-09|	2.26025764343413e-05| |       6|       1024|	6.337324016514285e-16|	8.09060164312957e-11|	4.517408062903668e-07| </del> <ins> {{< table caption = "Example Shuffle Sharding Configurations" >}} HandSize | Queues | 1 elephant | 4 elephants | 16 elephants |----------|-----------|------------|----------------|--------------------| | 12 | 32 | 4.428838398950118e-09 | 0.11431348830099144 | 0.9935089607656024 | | 10 | 32 | 1.550093439632541e-08 | 0.0626479840223545 | 0.9753101519027554 | | 10 | 64 | 6.601827268370426e-12 | 0.00045571320990370776 | 0.49999929150089345 | | 9 | 64 | 3.6310049976037345e-11 | 0.00045501212304112273 | 0.4282314876454858 | | 8 | 64 | 2.25929199850899e-10 | 0.0004886697053040446 | 0.35935114681123076 | | 8 | 128 | 6.994461389026097e-13 | 3.4055790161620863e-06 | 0.02746173137155063 | | 7 | 128 | 1.0579122850901972e-11 | 6.960839379258192e-06 | 0.02406157386340147 | | 7 | 256 | 7.597695465552631e-14 | 6.728547142019406e-08 | 0.0006709661542533682 | | 6 | 256 | 2.7134626662687968e-12 | 2.9516464018476436e-07 | 0.0008895654642000348 | | 6 | 512 | 4.116062922897309e-14 | 4.982983350480894e-09 | 2.26025764343413e-05 | | 6 | 1024 | 6.337324016514285e-16 | 8.09060164312957e-11 | 4.517408062903668e-07 | {{< /table >}} </ins> ### FlowSchema
Change:
I would like to have the "Container Environment" page to be translated into Italian page /language it /priority important-soon
/assign /lifecycle active

Discussion:
<ins> --- title: "Containers" weight: 40 --- </ins>

<ins> --- title: Container Environment content_type: concept weight: 20 --- <!-- overview --> Questa pagina descrive le risorse disponibili nei Container eseguiti in Kubernetes. <!-- body --> ## Container environment Quando si esegue un Container in Kubernetes, le seguenti risorse sono rese disponibili: * Un filesystem, composto dal file system dell'[image](/docs/concepts/containers/images/) e da uno o più [volumes](/docs/concepts/storage/volumes/). * Una serie di informazioni sul Container stesso. * Una serie di informazioni sugli oggetti nel cluster. ### Informazioni sul Container L' *hostname* di un Container è il nome del Pod all'interno del quale è eseguito il Container. È consultabile tramite il comando `hostname` o tramite la funzione [`gethostname`](http://man7.org/linux/man-pages/man2/gethostname.2.html) disponibile in libc. Il nome del Pod e il namespace possono essere resi disponibili come environment variables attraverso l'uso delle [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). Gli utenti possono aggiungere altre environment variables nella definizione del Pod; anche queste saranno disponibili nel Container come tutte le altre environment variables definite staticamente nella Docker image. ### Informazioni sul cluster Al momento della creazione del Container è generata una serie di environment variables con la lista di servizi in esecuzione nel cluster. Queste environment variables rispettano la sintassi dei Docker links. Per un servizio chiamato *foo* che è in esecuzione in un Container di nome *bar*, le seguenti variabili sono generate: ```shell FOO_SERVICE_HOST=<host su cui il servizio è attivo> FOO_SERVICE_PORT=<porta su cui il servizio è pubblicato> ``` I servizi hanno un indirizzo IP dedicato e sono disponibili nei Container anche via DNS se il [DNS addon](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/) è installato nel cluster. ## {{% heading "whatsnext" %}} * Approfondisci [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/). * Esegui un tutorial su come [definire degli handlers per i Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). </ins>
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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --There are several CNI plugins that need to be translated into Korean to be to . English --- --- Calico Cilium Flannel Kube-router Romana Weave-net Weaveworks 'Weave Net' . 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

Discussion:
Boot | 부트 | Build | 빌드 | Cache | 캐시 | <ins> Calico | 캘리코(Calico) | </ins> canary | 카나리(canary) | 릴리스 방식에 관련한 용어인 경우에 한함 cascading | 캐스케이딩(cascading) | character set | 캐릭터 셋 | Charts | 차트 | checkpoint | 체크포인트 | <ins> Cilium | 실리움(Cilium) | </ins> CLI | CLI | Cluster | 클러스터 | Command Line Tool | 커맨드라인 툴 |

Failed | Failed | 파드의 상태에 한함 Federation | 페더레이션 | field | 필드 | <del> Flannel | Flannel | </del> <ins> Flannel | 플란넬(Flannel) | </ins> form | 형식 | Google Compute Engine | Google Compute Engine | hash | 해시 |

kube-proxy | kube-proxy | Kubelet | Kubelet | Kubernetes | 쿠버네티스 | <ins> Kube-router | Kube-router | </ins> label | 레이블 | lifecycle | 라이프사이클 | Linux | 리눅스 |

rollback | 롤백 | rolling update | 롤링 업데이트 | rollout | 롤아웃 | <ins> Romana | 로마나(Romana) | </ins> Running | Running | 파드의 상태에 한함 runtime | 런타임 | Scale | 스케일 |

Volume | 볼륨 | Waiting | Waiting | 파드의 상태에 한함 Walkthrough | 연습 | <ins> Weave-net | 위브넷(Weave Net) | Weaveworks 사의 솔루션 공식 명칭은 'Weave Net'이므로 한영병기 시 공식 명칭 사용 </ins> Windows | 윈도우 | Worker | 워커 | 노드의 형태에 한함 Workload | 워크로드 |
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 <!-- 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

Discussion:
distros | 배포판 | Docker | 도커 | Dockerfile | Dockerfile | <ins> Docker Swarm | Docker Swarm | </ins> Downward API | 다운워드(Downward) API | draining | 드레이닝(draining) | egress | 이그레스, 송신(egress) |