jiebi/CodeConvo huggingface dataset:
Change:
<ins> --- title: CLA (Contributor License Agreement) id: cla date: 2018-04-12 full_link: https://github.com/kubernetes/community/blob/master/CLA.md short_description: > コントリビューターが行った貢献について、オープンソースプロジェクトが利用することを許諾する同意契約。 aka: tags: - community --- {{< glossary_tooltip text="コントリビューター" term_id="contributor" >}}が行った貢献について、オープンソースプロジェクトが利用することを許諾する同意契約。 <!--more--> CLAは、提供された成果物や知的財産(IP)に関する法的紛争の解決に役立ちます。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document:
/area localization /language ja /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 : /area localization /language ja /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
/triage accepted
/assign This is my first contribution to this project. Please let me know if you have any feedback or suggestions.
Change:
following matches only Pods with labels matching `app=nginx`. ```shell <del> kubectl get pods --all-namespaces -o=jsonpath="{..image}" -l app=nginx </del> <ins> kubectl get pods --all-namespaces -o=jsonpath="{.items[*].spec.containers[*].image}" -l app=nginx </ins> ``` ## List Container images filtering by Pod namespace

Discussion:
Hi, I've tested this example : It returns image names double, because "{..image}" recursively search in the output of JSON, So at the first, it will find the "image" word in "" and at the second time, it will find the "image" word in "". It means you will see the image name two times for each pod at least. Please change your example. Best Regards, Alireza Bahmani.
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
Hi What's the URL of the page where you've seen a problem?
here are the links to the: kubernetes docs website page ~ markdown file(s) where it require changes ~
The issue is, the following command produces 2 times (the count of image in a single pod). As mentioned, it is because the command count both the occurrence from the & sections from a single pod json manifest. Ideally it should be:
Following could be one of the fix for it:
/assign
There are other references . These would return duplicate images as well, right? I've updated those as well for now.
Hi yes, I feel those also need to be fixed. Let's wait for to provide their review. :)
Change:
``` Non-PEM content may appear before or after the CERTIFICATE PEM blocks and is unvalidated, <del> to allow for explanatory text as described in section 5.2 of RFC7468. </del> <ins> to allow for explanatory text as described in [section 5.2 of RFC7468](https://www.rfc-editor.org/rfc/rfc7468#section-5.2). </ins> When encoded in JSON or YAML, this field is base-64 encoded. A CertificateSigningRequest containing the example certificate above would look like this:

Discussion:
This is a Feature Request What would you like to be Add hyperlink to RFC7468 under API-based signers section in . Why is this needed This Change will make easier for the users to easily know about RFC7468 Timestamp as a quick reference. Comments kind/feature
/assign
Fixed it here
It is always a good practice to work on those issues which have the tag .
/language en /priority backlog /triage accepted Thanks for the suggestion
Thanks for your suggestion, i will take care from next time.
Change:
In Kubernetes v{{< skew currentVersion >}}, the value of `.spec.os.name` does not affect how the {{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}} <del> picks a Pod to run a node. In any cluster where there is more than one operating system for </del> <ins> picks a node for the Pod to run on. In any cluster where there is more than one operating system for </ins> running nodes, you should set the [kubernetes.io/os](/docs/reference/labels-annotations-taints/#kubernetes-io-os) label correctly on each node, and define pods with a `nodeSelector` based on the operating system

Discussion:
Hello! in the Pod OS section of this page, it says: ... **Editing for clarity: Forgive me if I'm misunderstanding, but kube-scheduler should pick a node for the Pod to run on, and not the other way around? The way the above sentence is worded sounds like kube-scheduler picks Pods to run nodes.
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
these two statements donot contradict as first one say that selecton of node by kube-scheduler is not based on . kube-scheduler pick a node of run based on various other creterias but not consider frield
I think you might correct the text might need some correction.
Let me see if I can help with this. /assign
Change:
The response to a successful request is a hello message: ```shell <del> Hello Kubernetes! </del> <ins> Hello, world! Version: 2.0.0 Hostname: hello-world-2895499144-2e5uh </ins> ``` ## {{% heading "cleanup" %}}

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: While following the Kubernetes tutorial on exposing an external IP address at , using the command results in an error. The error message indicates a failure to pull the Docker image due to deprecated image format: This issue prevents the tutorial from being completed as described. Proposed Solution: Update the tutorial page to use a newer version of the Docker image that complies with the current Docker Image specifications (OCI Format or Docker Image manifest v2, schema 2). Alternatively, provide a note or warning about this issue with guidance on how to proceed or troubleshoot this specific deprecation issue. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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 image going to be deprecated. so the example has to be updated !
So, what can be the alternate image to use?
This issue might be fixed similar to , I'm happy to draft a PR if no one was working on it already.
Change:
### DNS <del> While the other addons are not strictly required, all Kubernetes clusters should have [cluster DNS](/docs/concepts/services-networking/dns-pod-service/), as many examples rely on it. </del> <ins> While the other addons are not strictly required, all Kubernetes clusters should have [cluster DNS](/docs/concepts/services-networking/dns-pod-service/), as many examples rely on it. </ins> <del> Cluster DNS is a DNS server, in addition to the other DNS server(s) in your environment, which serves DNS records for Kubernetes services. </del> <ins> Cluster DNS is a DNS server, in addition to the other DNS server(s) in your environment, which serves DNS records for Kubernetes services. </ins> Containers started by Kubernetes automatically include this DNS server in their DNS searches. ### Web UI (Dashboard) <del> [Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications running in the cluster, as well as the cluster itself. </del> <ins> [Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications running in the cluster, as well as the cluster itself. </ins> ### Container Resource Monitoring <del> [Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/) records generic time-series metrics </del> <ins> [Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/) records generic time-series metrics </ins> about containers in a central database, and provides a UI for browsing that data. ### Cluster-level Logging

Discussion:
Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign
Change:
"name-virtual-host-ingress":               {&networking.Ingress{}}, "name-virtual-host-ingress-no-third-host": {&networking.Ingress{}}, "namespaced-params":                       {&networking.IngressClass{}}, <ins> "networkpolicy":                           {&networking.NetworkPolicy{}}, </ins> "network-policy-allow-all-egress":         {&networking.NetworkPolicy{}}, "network-policy-allow-all-ingress":        {&networking.NetworkPolicy{}}, "network-policy-default-deny-egress":      {&networking.NetworkPolicy{}},

Discussion:
While working through the Killer Shell scenario for NetworkPolicies to prep for my CKA, I used the example but it failed validation. When I looked at their solution it had one tiny difference, they had a - in front of "ports:" and you guys didn't. Based on the reference docs it appears ports does expect an array which would mean that you are missing the hyphen. docs: solution from
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 indentation of list items may be the source of confusion. Once you indent all list items under a given key, the parent element of the 'ports' attribute becomes more evident. The example on the website is correct. I'm not sure about the solution from If you put as the first key of a list item object, if will carry the bar for that list item, if is not the the first key, you will indent it rather than adding another before it. Anyway, I'm fixing the example in hope things become clearer for readers.
Change:
title: "What's next?" description: "What's next after installing kubectl." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- * [Install Minikube](https://minikube.sigs.k8s.io/docs/start/)

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:
- **CPU requirement (cores)** and **Memory requirement (MiB)**: You can specify the minimum [resource limits](/docs/tasks/configure-pod-container/limit-range/) for the container. By default, Pods run with unbounded CPU and memory limits. <del> - **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/user-guide/containers/#containers-and-commands). You can use the command options and arguments to override the default. </del> <ins> - **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/tasks/inject-data-application/define-command-argument-container/). You can use the command options and arguments to override the default. </ins> - **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.

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 link navigates to . However, there is no ID . Proposed Solution: It would probably be fine to replace the link with . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign PR created:
/close
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
Change:
only when a Pod is created (either by the client, or mutated during admission). After creation, each schedulingGate can be removed in arbitrary order, but addition of a new scheduling gate is disallowed. <del> {{<mermaid>}} stateDiagram-v2 s1: pod created s2: pod scheduling gated s3: pod scheduling ready s4: pod running if: empty scheduling gates? [*] --> s1 s1 --> if s2 --> if: scheduling gate removed if --> s2: no if --> s3: yes s3 --> s4 s4 --> [*] {{< /mermaid >}} </del> <ins> {{< figure src="/docs/images/podSchedulingGates.svg" alt="pod-scheduling-gates-diagram" caption="Figure. Pod SchedulingGates" class="diagram-large" link="https://mermaid.live/edit#pako:eNplkktTwyAUhf8KgzuHWpukaYszutGlK3caFxQuCVMCGSDVTKf_XfKyPlhxz4HDB9wT5lYAptgHFuBRsdKxenFMClMYFIdfUdRYgbiD6ItJTEbR8wpEq5UpUfnDTf-5cbPoJjcbXdcaE61RVJIiqJvQ_Y30D-OCt-t3tFjcR5wZayiVnIGmkv4NiEfX9jijKTmmRH5jf0sRugOP0HyHUc1m6KGMFP27cM28fwSJDluPpNKaXqVJzmFNfHD2APRKSjnNFx9KhIpmzSfhVls3eHdTRrwG8QnxKfEZUUNeYTDBNbiaKRF_5dSfX-BQQQ0FpnEqQLJWhwIX5hyXsjbYl85wTINrgeC2EZd_xFQy7b_VJ6GCdd-itkxALE84dE3fAqXyIUZya6Qqe711OspVCI2ny2Vv35QqVO3-htt66ZWomAvVcZcv8yTfsiSFfJOydZoKvl_ttjLJVlJsblcJw-czwQ0zr9ZeqGDgeR77b2jD8xdtjtDn" >}} </ins> ## Usage example To mark a Pod not-ready for scheduling, you can create it with one or more scheduling gates like this:

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: has a diagram, but it doesn't use Kubernetes colors. Proposed Solution: Copy the colors from an example in and then apply those colors to the items in the diagram. Page to Update: /priority backlog
/triage accepted
/assign
Change:
_Pods_ are the smallest deployable units of computing that you can create and manage in Kubernetes. A _Pod_ (as in a pod of whales or pea pod) is a group of one or more <del> {{< glossary_tooltip text="containers" term_id="container" >}}, with shared storage/network resources, and a specification </del> <ins> [containers](/docs/concepts/containers/), with shared storage/network resources, and a specification </ins> for how to run the containers. A Pod's contents are always co-located and co-scheduled, and run in a shared context. A Pod models an application-specific "logical host": it contains one or more application

Discussion:
Clicking the "Containers" hyperlink leads to the "What is Kubernetes?" page. I'm not sure if this was intended. There is some explanation of containerized deployments (after a scroll) but I wonder if it makes more sense to direct them to the "Containers" term page. As a user learning in the docs, it was a bit confusing. Pods hyperlink re-direction shown below, from this <img width="901" alt="Screen Shot 2020-10-09 at 1 58 28 PM" src="https://user-"Leads to the below <img width="843" alt="Screen Shot 2020-10-09 at 1 58 54 PM" src="https://user-"Perhaps redirecting to the page defining containers in the concepts may be better, though I believe more definition could be there.
/triage accepted
/kind bug /language en /priority backlog /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 : /kind bug /language en /priority backlog /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
Hi I'd like to work on this
Awesome! I think you can assign it yourself by running the "assign" command. Context here: and example here:
/assign
Change:
deployment methods. - Configure user management by determining your [Authentication](/docs/reference/access-authn-authz/authentication/) and <del> [Authorization](docs/reference/access-authn-authz/authorization/) methods. </del> <ins> [Authorization](/docs/reference/access-authn-authz/authorization/) methods. </ins> - Prepare for application workloads by setting up <del> [resource limits](docs/tasks/administer-cluster/manage-resources/), </del> <ins> [resource limits](/docs/tasks/administer-cluster/manage-resources/), </ins> [DNS autoscaling](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/) and [service accounts](/docs/reference/access-authn-authz/service-accounts-admin/).

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
<!-- Kubernetes runs your workload by placing containers into Pods to run on _Nodes_. A node may be a virtual or physical machine, depending on the cluster. Each node <del> is managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}} and contains the services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} </del> <ins> contains the services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}}, managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. </ins> Typically you have several nodes in a cluster; in a learning or resource-limited environment, you might have just one.

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: ! URL #self-registration-of-nodes #manual-node-administration # # Proposed Solution: {#self-registration-of-nodes} {#manual-node-administration} Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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 /assign
Change:
rollback | 롤백 | rolling update | 롤링 업데이트 | rollout | 롤아웃 | <ins> Romana | 로마나(Romana) | </ins> Running | Running | 파드의 상태에 한함 runtime | 런타임 | Scale | 스케일 |

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 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