jiebi/CodeConvo huggingface dataset:
Change:
This page shows how to create a Kubernetes Service object that exposes an external IP address. ## {{% heading "prerequisites" %}} * Install [kubectl](/docs/tasks/tools/install-kubectl/). * Use a cloud provider like Google Kubernetes Engine or Amazon Web Services to

Discussion:
This is a Bug Report There are some commands in the tutorial that are missing code formatting. This is a request to update those commands and remove any extra lines in the page. <!--Required Information--Problem: The tutorial has commands that are not formatted as code. For example, kubectl get deployments hello-world Add code formatting: Proposed Solution: Identify the commands that are missing code formatting. Add the code formatting to the commands. Clean up any extra lines in the page. Page to Update: This is a good issue for a first time contributor. If you need more information, feel free to ask in this issue. It is a good idea to build your changes locally.
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted /language en Thanks - another good spot
Is this PR currently being worked on?
it seems already formatted, right?
I don't see any issues with the page as well, and it looks like it was last modified July 27, 2020 at 4:18. Are we missing something?
Let me look. I'd like a first time contributor to work on this issue.
The page renders correctly, however, it would be helpful to clean up the formatting of the page such as extra lines and spaces. Also, the page should use code blocks around any commands (instead of indentation). Let me know if you need more information. Thanks!
i'm a first timer in kubernetes. But i saw nothing wrong in formatting code nor indentation. Only i think there is missing some instruction in creating apps. Should be better to follow Just my 2cent. wdyt?
/assign
Change:
host mounts, or containers that are privileged or using specific non-namespaced capabilities (e.g. `MKNODE`, `SYS_MODULE` etc.). This should only be enabled if user namespace remapping is enabled in the Docker daemon. <ins> - `ExternalPolicyForExternalIP`: Fix a bug where ExternalTrafficPolicy is not applied to Service ExternalIPs. </ins> - `GCERegionalPersistentDisk`: Enable the regional PD feature on GCE. - `GenericEphemeralVolume`: Enables ephemeral, inline volumes that support all features of normal volumes (can be provided by third-party storage vendors, storage capacity tracking,

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 feature gate is not listed in Proposed Solution: Add to the feature gate list Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.21 Additional Information: Prompted by /language en /kind bug /sig network
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
we'd like this feature documented, even if it has already graduated
Change:
- [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com` - [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume` <del> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#csi-migration-5). </del> <ins> In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration). </ins> --> vSphere 存储类有两种制备器

Discussion:
stay In the page, the link at the text "vSphereVolume CSI " should be -csi-migration
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/language zh
Are you still working on it?
I submitted PR to solve this issue and put you as the co-author.
Change:
- `APIResponseCompression`: Compress the API responses for `LIST` or `GET` requests. - `APIServerIdentity`: Assign each API server an ID in a cluster. - `APIServerTracing`: Add support for distributed tracing in the API server. <del> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/traces-for-kubernetes-system-components) for more details. </del> <ins> See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details. </ins> - `Accelerators`: Provided an early form of plugin to enable Nvidia GPU support when using Docker Engine; no longer available. See [Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) for

Discussion:
This is a Bug Report In the file: find two hits: with broken links to 404. /language en
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 en
Below is the correct link for Traces for Kubernetes System Components:
/assign
Change:
<!--more--> <del> Um Ingress pode fornecer as capacidades de um proxy reverso para as aplicações. </del> <ins> Um Ingress pode fornecer balanceamento de carga, terminação SSL e hospedagem virtual baseada em nomes. </ins>

Discussion:
The translated Brazilian Portuguese glossary entry for ingress is slightly out-of-date with its English counterpart. Update the entry so it reflects the latest English version. /language pt /triage accepted /assign
Change:
container runtime's management service is restarted while waiting for processes to terminate, the cluster retries from the start including the full original grace period. <del> An example flow: </del> <ins> Pod termination flow, illustrated with an example: </ins> 1. You use the `kubectl` tool to manually delete a specific Pod, with the default grace period (30 seconds).

Discussion:
work not well. Not sure how to fix it. This issue has spreaded to the currently. <img width="550" alt="image" src=""
/triage accepted
/language en
For a likely fix, see
Change:
nodes` when run on the control-plane node. {{< note >}} <del> As the cluster nodes are usually initialized sequentially, the CoreDNS Pods are likely to all run on the first control-plane node. To provide higher availability, please rebalance the CoreDNS Pods </del> <ins> As the cluster nodes are usually initialized sequentially, the CoreDNS Pods are likely to all run on the first control-plane node. To provide higher availability, please rebalance the CoreDNS Pods </ins> with `kubectl -n kube-system rollout restart deployment coredns` after at least one new node is joined. {{< /note >}}

Discussion:
The command only has Cobra (CLI) documentation and there are no pointers on what fields are relevant in the configuration passed with --config to it: Add a minimal example + config for the command usage on this page: /sig cluster-lifecycle /kind feature xref
/triage accepted
/language en
Change:
nodeName: kube-01 ``` <del> 上記のPodはkube-01という名前のNodeで稼働します。 </del> <ins> 上記のPodは`kube-01`というNodeでのみ実行されます。 ## Podトポロジー分散制約 {#pod-topology-spread-constraints} </ins> <del> ## {{% heading "whatsnext" %}} </del> <ins> _トポロジー分散制約_ を使って、リージョン、ゾーン、Nodeなどの障害ドメイン間、または定義したその他のトポロジードメイン間で、クラスター全体にどのように{{< glossary_tooltip text="Pod" term_id="Pod" >}}を分散させるかを制御することができます。これにより、パフォーマンス、予想される可用性、または全体的な使用率を向上させることができます。 </ins> <del> [Taints](/ja/docs/concepts/scheduling-eviction/taint-and-toleration/)を使うことで、NodeはPodを追い出すことができます。 </del> <ins> 詳しい仕組みについては、[トポロジー分散制約](/docs/concepts/scheduling-eviction/topology-spread-constraints/)を参照してください。 </ins> <del> [Nodeアフィニティ](https://git.k8s.io/community/contributors/design-proposals/scheduling/nodeaffinity.md)と [Pod間アフィニティ/アンチアフィニティ](https://git.k8s.io/community/contributors/design-proposals/scheduling/podaffinity.md) のデザインドキュメントには、これらの機能の追加のバックグラウンドの情報が記載されています。 </del> <ins> ## {{% heading "whatsnext" %}} </ins> <del> 一度PodがNodeに割り当たると、kubeletはPodを起動してノード内のリソースを確保します。 [トポロジーマネージャー](/docs/tasks/administer-cluster/topology-manager/)はNodeレベルのリソース割り当てを決定する際に関与します。 </del> <ins> * [TaintとToleration](/ja/docs/concepts/scheduling-eviction/taint-and-toleration/)についてもっと読む。 * [Nodeアフィニティ](https://git.k8s.io/design-proposals-archive/scheduling/nodeaffinity.md)と[Pod間アフィニティ/アンチアフィニティ](https://git.k8s.io/design-proposals-archive/scheduling/podaffinity.md)のデザインドキュメントを読む。 * [トポロジーマネージャー](/ja/docs/tasks/administer-cluster/topology-manager/)がNodeレベルのリソース割り当ての決定にどのように関与しているかについて学ぶ。 * [nodeSelector](/ja/docs/tasks/configure-pod-container/assign-pods-nodes/)の使用方法について学ぶ。 * [アフィニティとアンチアフィニティ](/ja/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/)の使用方法について学ぶ。 </ins>

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
## Securing a cluster <del> * [Certificates](/docs/concepts/cluster-administration/certificates/) describes the steps to generate certificates using different tool chains. </del> <ins> * [Generate Certificates](/docs/tasks/administer-cluster/certificates/) describes the steps to generate certificates using different tool chains. </ins> * [Kubernetes Container Environment](/docs/concepts/containers/container-environment/) describes the environment for Kubelet managed containers on a Kubernetes node.

Discussion:
This is a clean up 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. --Why is this needed is a task page. A better home for it would be within Comments Be sure to add Netlify redirects (see ) from the old to the new page. /language en /kind cleanup
/assign
From (I agree)
/sig auth
/triage accepted
I left notes (PR ) about how to create a new task page from the page. Does this sound like a good approach?
Change:
<a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> <del> {{ T "version_menu" }} </del> <ins> {{ T "version_menu" }} </ins> </a> <del> <div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink"> </del> <ins> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> </ins> {{ range .Site.Params.versions }} <a class="dropdown-item" href="{{ .url }}">{{ .version }}</a> {{ end }} <del> </div> </del> <ins> </div> </ins>  No newline at end of file

Discussion:
Expected behavior: https://v1- (drop-downs work) Actual behavior: (drop-downs do not work) This may be a issue or a result of non-translated pages not showing up in autogenerated navs. I'm unsure.
/assign /priority important-soon /kind bug
Hello, calestehorgan I investigated this problem quickly and found that (this is the version and language box) seemed to remain when the mouse cursor has hovered. ! Adding the following style makes the problem disappeared: ! Maybe some style is missing or something blocks a style applied.
Thank you for the help!! I'll try it out.
I'm glad to help!
Change:
#### Install wins, kubelet, and kubeadm ```PowerShell <del> curl.exe -LO https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/PrepareNode.ps1 </del> <ins> curl.exe -LO https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/kubeadm/scripts/PrepareNode.ps1 </ins> .PrepareNode.ps1 -KubernetesVersion {{< param "fullversion" >}} ```

Discussion:
Please change the link at ("Adding Windows nodes" page): with the new one:
Welcome and thanks for the first issue here! I will look into this issue. /assign
/triage accepted /kind bug
Instead you can request a new release in the sig windows tools repo, by logging an issue there. Linking to the master branch there is not a good idea, IMO. /sig windows
Also what problems are you seeing?
The problem is that the link is dead. We need to replace it with the link in
GitHub didn't allow me to assign the following users: steven-my. 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 steven-my 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
Change:
When you are ready to scale up to more machines and higher availability, a [hosted solution](#hosted-solutions) is the easiest to create and maintain. [Turnkey cloud solutions](#turnkey-cloud-solutions) require only a few commands to create <del> and cover a wide range of cloud providers. </del> <ins> and cover a wide range of cloud providers. [On-Premises turnkey cloud solutions](#on-premises-turnkey-cloud-solutions) have the simplicity of the turnkey cloud solution combined with the security of your own private network. </ins> If you already have a way to configure hosting resources, use [kubeadm](/docs/setup/independent/create-cluster-kubeadm/) to easily bring up a cluster with a single command per machine.

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ X] Feature Request [ ] Bug Report Problem: Some Kubernetes platforms are best described as being an On-Prem Turnkey Solution. This category is not properly mentioned or described on the Picking the Right Solution page ( ) Proposed Solution: Add a new section called On-Prem Turn-key Cloud Solutions right below the existing Turn-key Cloud Solutions section that describes this category and list platforms that fit into this category. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
^
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 stale
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Change:
The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes you through the steps you follow to apply a seccomp profile to a Pod or to one of its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes, <del> based on setting `securityContext` within the Pod's `.spec`. </del>  No newline at end of file <ins> based on setting `securityContext` within the Pod's `.spec`. </ins>

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: Kubernetes an annotation, , that is not registered or documented. Proposed Solution: Register and document this annotation. Page to Update: Also consider whether to mention that annotation in Additional Information: /sig auth /language en
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
I would like to work on this.
/assign
Change:
margin-top: 25px; } <del> footer { float: left !important; } </del> p { font-weight: 300 !important; }

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: (Despite the PR has been merged, it seems that the error still exists. So opening an issue here. ) From the PR : [As-is] ! ! [To-be] ! ! Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--CC /area web-development
/triage accepted
Hello Thanks for reporting this issue. May i kindly know some more details to reproduce the issue. 1) Browser & Version ? 2) Resolution of your display ? I'm trying to reproduce it on wide viewport !
Hello Here is the info of my env: Windows 10 Enterprise 20H2 Google Chrome 97.0.4692.99 (64bit) Monitor resolution: 3840 1600 Chrome window size: [1868 1592] ! [1868 1592] [3767 1600] ! [3767 * 1600]
I can replicate this with Chromium and with Firefox.
/priority backlog
Thanks for the information. Please can you assign this issue to me.
try this Prow command: /assign ravikiranr26 (reply in a comment with that command on a line by itself)
/assign ravikiranr26
Change:
card: name: contribute weight: 50 <del> title: Translating the docs </del> <ins> title: Localizing the docs </ins> --- <!-- overview -->

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 /enhanced? I could have directly raised a PR for it, but i didn't found the file where its written, so raising it as issue. I think "Localizing" word could be better fit here than "Translating", and across K8s site "Localization" term is used everywhere so... Page: ! <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --<!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/language en /sig docs
/retitle Update link text terminology to 'Localizing' instead of 'Translating' on docs home page
/priority backlog /triage accepted
plz plz i want work this. /assign
Can you please let me know how to proceed with making the change? I'm relatvely new contributor. Any pointers will be help me. Thanks:)
The employs to render the Markdown file as a corresponding HTML page. (See and ) To address the issue with link text displayed on the page. Navigate to the markdown file  , go to , and change the attribute in the markdown front matter, to see if it resolves the problem. I hope this suggestion will be of assistance!
wow thanks for taking effort to explain this. Would have taken you less time to fix this yourself than explain me here(lol). Appreciate it, thanks a lot!
Submitted pull request please review when get time. thanks!
Change:
<!-- overview --> <del> Kubernetes reserves all labels and annotations in the kubernetes.io namespace. </del> <ins> Kubernetes reserves all labels and annotations in the kubernetes.io and k8s.io namespaces. </ins> This document serves both as a reference to the values and as a coordination point for assigning values.

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: "Well-Known Labels, Annotations and Taints" says Except it's actually AND (?) cc Proposed Solution: Add Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Filing an issue so I don't forget this. See discussion
/assign
I think and both hold the same meaning.
/triage accepted