jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report Problem: The link for under in is incorrect. It is redirecting to instead of that it should redirect to Proposed Solution: Create a ConfigMap should redirect to instead of .
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
Page related to the issue:
/language en /sig docs
I would like to work on this issue if triage gets accepted.
The issue is fixed

Discussion:
{{< note >}} <del> * You must create a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) </del> <ins> * You must [create a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/#create-a-configmap) </ins> before you can use it. * A ConfigMap is always mounted as `readOnly`.
Change:
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

Discussion:
<ins> --- title: CIDR id: cidr date: 2019-11-12 full_link: short_description: > CIDRは、IPアドレスの範囲を記述するための表記法であり、さまざまなネットワークを構成するために使用されています。 aka: tags: - networking --- CIDR(Classless Inter-Domain Routing)はIPアドレスの範囲を記述するための表記法であり、さまざまなネットワークを構成するために使用されています。 <!--more--> Kubernetesでは、各{{< glossary_tooltip text="Node" term_id="node" >}}に対して、CIDRで記述されている開始アドレスとサブネットマスクを通してIPアドレスの範囲が割り当てられます。これにより、Nodeは各{{< glossary_tooltip text="Pod" term_id="pod" >}}に一意のIPアドレスを割り当てることができます。CIDRはもともとIPv4の概念でしたが、IPv6もサポートされるように拡張されています。 </ins>
Change:
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.

Discussion:
<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>
Change:
In the paragraph under a working control plane node in the cluster that has execute kubeadm kubeconfig user --org system:nodes --client-name system:node:NODE must be set to the name of the existing failed node in the cluster. Modify the resulted manually to adjust the cluster name and server endpoint, or pass kubeconfig user --config (it accepts InitConfiguration). If your cluster does not have the you must sign the embedded certificates in the externally. I do not know where or what the "InitConfiguration" is, nor does the command run without specifying a --config. Could someone add a little more information or example to this?
Page reported in issue: /language en
/retitle Lack of clarity on usage of within the "Troubleshooting kubeadm" page
/sig cluster-lifecycle
all kubeadm commands have reference pages
About InitConfiguration is explained
if you go to that page there is a guide on how to generate kubeconfig files. but the text under should probably mention /help /triage accepted replace: with:
This request has been marked as needing help from a contributor. 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 : all kubeadm commands have reference pages /triage accepted (it accepts InitConfiguration (see ) </details
/assign
Please review the PR.
I just wanted to say thank you very much. I really appreciate that link going into the paragraph so I can follow it to the reference.

Discussion:
`kubeadm kubeconfig user --org system:nodes --client-name system:node:$NODE > kubelet.conf`. `$NODE` must be set to the name of the existing failed node in the cluster. Modify the resulted `kubelet.conf` manually to adjust the cluster name and server endpoint, <del> or pass `kubeconfig user --config` (it accepts `InitConfiguration`). If your cluster does not have </del> <ins> or pass `kubeconfig user --config` (see [Generating kubeconfig files for additional users](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#kubeconfig-additional-users)). If your cluster does not have </ins> the `ca.key` you must sign the embedded certificates in the `kubelet.conf` externally. 1. Copy this resulted `kubelet.conf` to `/etc/kubernetes/kubelet.conf` on the failed node. 1. Restart the kubelet (`systemctl restart kubelet`) on the failed node and wait for
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: documents the audit annotation ; however, it is missing from (which is the formal document we use to record registrations). Proposed Solution: Update to mention the ValidatingAdmissionPolicy audit annotation. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig api-machinery /language en /priority backlog /triage accepted /help
This request has been marked as needing help from a contributor. 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: documents the audit annotation ; however, it is missing from (which is the formal document we use to record registrations). Update to mention the ValidatingAdmissionPolicy audit annotation. <!--Kubernetes Version:--/sig api-machinery /language en /priority backlog /triage accepted /help </details
hey ,please review my change , I am trying to solve this
/assign
Fix merged as part of /close
Closing this issue. <detailsIn response to : Fix merged as part of 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:
- [`pod-security.kubernetes.io/audit-violations`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-audit-violations) - [`pod-security.kubernetes.io/enforce-policy`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-enforce-policy) - [`pod-security.kubernetes.io/exempt`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-exempt) <ins> - [`validation.policy.admission.k8s.io/validation_failure`](/docs/reference/labels-annotations-taints/audit-annotations/#validation-policy-admission-k8s-io-validation-failure) </ins> See more details on [Audit Annotations](/docs/reference/labels-annotations-taints/audit-annotations/). ## kubeadm
Change:
This is a Bug Report <!--Required Information--Problem: Documentation layout issue in page under IngressClass scope Namespaced section, see following screenshot: <img width="912" alt="image" src=""Proposed Solution: I would like to create a PR to fix it, the solution is to remove and outside of template Page to Update: Documentation layout issue in Ingress.

Discussion:
{{ if not $is_valid }} {{ errorf "%q is not a valid feature-state, use one of %q" $state $valid_states }} {{ else }} <del> <div class="my-2 feature-state-notice feature-{{ $state }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]</code> </div> </del> <ins> <div class="my-2 feature-state-notice feature-{{ $state }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]</code> </div> </ins> {{ end }} {{- else -}}

{{- with $currentStage -}} <!-- Display feature state information  --> <del> <div class="my-2 feature-state-notice feature-{{ .stage }}" title="{{ printf "%s %s" (T "feature_state_feature_gate_tooltip") $feature_gate_name }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]</code> </div> </del> <ins> <div class="my-2 feature-state-notice feature-{{ .stage }}" title="{{ printf "%s %s" (T "feature_state_feature_gate_tooltip") $feature_gate_name }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]</code> </div> </ins> {{- $featureGateFound = true -}} {{- end -}}
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 In , briefly mention that you can set environment variables for containers in Pods, and link to our pages about that. No need to add an explanation; this is about helping people discover the feature. Why is this needed This is about helping people discover the feature. Comments /sig node /language en
Relevant to
Potential improvement, worth doing. /priority backlog /triage accepted
I would like to assist in resolving this issue. Thanks! /assign
PRs are welcome!

Discussion:
object to make actual Pods. The `PodTemplate` is part of the desired state of whatever workload resource you used to run your app. <ins> When you create a Pod, you can include [environment variables](/docs/tasks/inject-data-application/define-environment-variable-container/) in the Pod template for the containers that run in the Pod. </ins> The sample below is a manifest for a simple Job with a `template` that starts one container. The container in that Pod prints a message then pauses.
Change:
This is a Bug Report Problem: In the of the page, there is a section of that has an issue with the hyperlinking of the text. The is not hyperlinked properly. Proposed Solution: We should link the with the appropriate link, i.e., Page to Update:
/language en
I would to like to work on this issue, if the triage gets accepted.
/retitle Broken link in the description of on "Feature Gates" page
Fixes are welcomed. /triage accepted /priority backlog
I have raised PR to fix this problem.
Could you please review and merge the PR whenever free.

Discussion:
defaultValue: false fromVersion: "1.29" --- <del> Enables images to be pulled based on the [runtime class] (/docs/concepts/containers/runtime-class/) of the pods that reference them. </del> <ins> Enables images to be pulled based on the [runtime class](/docs/concepts/containers/runtime-class/) of the pods that reference them. </ins>
Change:
Note that this issue is for Japanese Speaker 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
/assign
/unassign Shubhdeep02 PTAL , thank you
/triage accepted
/assign
Hi thank you for interesting in SIG-docs Japanese Localization project!! Localization requires native or equivalent Japanese language proficiency. It looks you live in Pune, India. Please confirm this before working on this issue. I believe the issues labeled with or (or those you created) are areas where you can contribute more effectively. issues labeled with : issues labeled with : Thank you
/unassign PTAL
Hello, -san, this issue looks good as my first contribution. /assign

Discussion:
<ins> --- title: コンテナランタイムインターフェース(CRI) id: cri date: 2019-03-07 full_link: /docs/concepts/overview/components/#container-runtime short_description: > コンテナランタイムがkubeletと統合するためのAPIです aka: tags: - fundamental --- コンテナランタイムインターフェース(CRI)は、ノード上の{{< glossary_tooltip text="kubelet" term_id="kubelet" >}}と統合するためのコンテナランタイム用APIです。 <!--more--> 詳細については、[CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)のAPIと仕様をご覧ください。 </ins>
Change:
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
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted </details
/assign
Raised PR in
Hi Thank you for interesting in SIG-docs ja subproject !! This is a Japanese localization Project, but It looks that you live in India and you are fluent Hindi / English. So, Participating in Hindi projects is helpful for k/website :) you can search issues from this query result thank you
I checked , but it looks that this translation is made by google translation (or any other auto-translation tools). We cannot accept the pr like this. Thank you
/unassign Shubhdeep02
I sincerely apologize for the problems occurred due to me , and thanks for your support.
Thank you for understanding Your motivation is really excellent for the kubernetes community, so I believe that you will be able to make valuable contributions!! Please don't hesitate to contact us if there's anything you need support with. Thank you :)
/triage accepted
/assign
PRPR

Discussion:
<ins> --- title: containerd id: containerd date: 2019-05-14 full_link: https://containerd.io/docs/ short_description: > シンプルさ、堅牢性、移植性を重視したコンテナランタイムです。 aka: tags: - tool --- シンプルさ、堅牢性、移植性を重視したコンテナランタイムです。 <!--more--> containerdはLinuxやWindows上でデーモンとして実行される{{< glossary_tooltip text="コンテナ" term_id="container" >}}ランタイムです。containerdはコンテナイメージの取得や保存、コンテナの実行、ネットワークアクセスの提供などを行います。 </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: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Proposed Solution: Add more links into (look at the left nav to see which ones they are) Page to Update: /language en /priority backlog /good-first-issue /triage accepted :information_source: have you already worked on an issue? Please save this for a contributor who has not.
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: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Add more links into (look at the left nav to see which ones they are) /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
I want to work on this. /assign
Pr to fix this issue

Discussion:
* the kubelet's [checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) * a list of [Articles on dockershim Removal and on Using CRI-compatible Runtimes](/docs/reference/node/topics-on-dockershim-and-cri-compatible-runtimes/) <ins> * [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions) * [Node Labels Populated By The Kubelet](/docs/reference/node/node-labels) </ins> * [Node `.status` information](/docs/reference/node/node-status/) You can also read node reference details from elsewhere in the

* [Node Metrics Data](/docs/reference/instrumentation/node-metrics). <del> * [CRI Pod & Container Metrics](/docs/reference/instrumentation/cri-pod-container-metrics). </del>  No newline at end of file <ins> * [CRI Pod & Container Metrics](/docs/reference/instrumentation/cri-pod-container-metrics). </ins>