jiebi/CodeConvo huggingface dataset:
Change:
<ins> --- title: रेप्लिकासेट (ReplicaSet) id: replica-set date: 2018-04-12 full_link: /docs/concepts/workloads/controllers/replicaset/ short_description: > रेप्लिकासेट यह सुनिश्चित करता है कि किसी एक अवसर पर निर्दिष्ट संख्या में पॉड प्रतिकृतियां चल रही हैं। aka: tags: - fundamental - core-object - workload --- एक रेप्लिकासेट (का उद्देश्य) किसी भी समय चल रहे रेप्लिका पॉड्स का एक समूह बनाए रखना है। <!--more--> वर्कलोड ऑब्जेक्ट्स, जैसे {{< glossary_tooltip text="डिप्लॉयमेंट" term_id="deployment" >}}, रेप्लिकासेट्स के विनिर्देश के आधार पर आपके क्लस्टर पर कॉन्फ़िगर की गई संख्या में {{< glossary_tooltip term_id="pod" text="पॉड्स" >}} चल रहे है ये सुनिश्चित करते हैं। </ins>

Discussion:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called content/hi/docs/reference/glossary/replica- Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign Thank you
Change:
<section class="call-to-action"> <div class="main-section"> <div class="call-to-action" id="cta-certification"> <del> <div class="logo-certification cta-image cta-image-before" id="logo-cka"> </del> <ins> <div class="cta-text"> <h2>Build your cloud native career</h2> <p>Kubernetes is at the core of the cloud native movement. Training and certifications from the Linux Foundation and our training partners lets you invest in your career, learn Kubernetes, and make your cloud native projects successful.</p> </div> <div class="logo-certification cta-image" id="logo-cka"> </ins> <img src="/images/training/kubernetes-cka-white.svg"/> </div> <del> <div class="logo-certification cta-image cta-image-after" id="logo-ckad"> </del> <ins> <div class="logo-certification cta-image" id="logo-ckad"> </ins> <img src="/images/training/kubernetes-ckad-white.svg"/> </div> <del> <div class="cta-text"> <h2>Build your cloud native career</h2> <p>Kubernetes is at the core of the cloud native movement. Training and certifications from the Linux Foundation and our training partners lets you invest in your career, learn Kubernetes, and make your cloud native projects successful.</p> </del> <ins> <div class="logo-certification cta-image" id="logo-cks"> <img src="/images/training/kubernetes-cks-white.svg"/> </ins> </div> </div> </div>

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 Update to mention the new Kubernetes Security Specialist Certification Why is this needed There is a Kubernetes Security Specialist Certification, coming in November 2020. Comments /kind feature /language en
/priority important-soon
let's collaborate to put everything in place to make this into a Good First Issue.
Design-wise, it's much easier to place 2 certification logos than 3. do you have any thoughts on how to adjust things design-wise to incorporate the 3rd certification?
/sig security
/triage accepted
/cc
Change:
This projected volume consists of three sources: <del> 1. A ServiceAccountToken acquired from kube-apiserver via TokenRequest API. It will expire after 1 hour by default or when the pod is deleted. It is bound to the pod and has kube-apiserver as the audience. 1. A ConfigMap containing a CA bundle used for verifying connections to the kube-apiserver. This feature depends on the `RootCAConfigMap` feature gate, which publishes a "kube-root-ca.crt" ConfigMap to every namespace. `RootCAConfigMap` feature gate is graduated to GA in 1.21 and default to true. (This flag will be removed from --feature-gate arg in 1.22) 1. A DownwardAPI that references the namespace of the pod. </del> <ins> 1. A `serviceAccountToken` acquired from kube-apiserver via TokenRequest API. It will expire after 1 hour by default or when the pod is deleted. It is bound to the pod and it has its audience set to match the audience of the `kube-apiserver`. 1. A `configMap` containing a CA bundle used for verifying connections to the kube-apiserver. 1. A `downwardAPI` that references the namespace of the pod. </ins> See more details about [projected volumes](/docs/tasks/configure-pod-container/configure-projected-volume-storage/).

Discussion:
says about : Since 1.22 is released, the text shall not say what is planned to happen in the 1.22 versions, as if those were in the future.
/triage accepted /kind bug /assign
/language en
Change:
<td colspan="2">--address string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0 </td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the Kubelet to serve on (set to <code>0.0.0.0</code> or <code>::</code> for listening in gll interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's <code>--config</code> flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)</td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the Kubelet to serve on (set to <code>0.0.0.0</code> or <code>::</code> for listening in all interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's <code>--config</code> flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)</td> </ins> </tr> <tr>

Discussion:
says: typo gll → all
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
Change:
systemctl daemon-reload systemctl restart docker ``` <del> {{< /tab >}} {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% /tab %}} {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # (도커 CE 설치)

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: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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
Hey folks, I'm happy to help you with this /assign
Change:
1. In a terminal window, clone your fork and update the [Docsy Hugo theme](https://github.com/google/docsy#readme): ```shell <del> git clone git@github.com/<github_username>/website </del> <ins> git clone git@github.com:<github_username>/website </ins> cd website git submodule update --init --recursive --depth 1 ```

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: It failed when running the command in the doc It works after replacing the first with in Proposed Solution: Replace the first with in 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
I will open a PR to fix it.
/retitle Incorrect git clone URL in "Opening a pull request" page /language en
Change:
kubectl logs myapp-pod -c init-mydb      # Inspect the second init container ``` <del> At this point, those init containers will be waiting to discover Services named </del> <ins> At this point, those init containers will be waiting to discover {{< glossary_tooltip text="Services" term_id="service" >}} named </ins> `mydb` and `myservice`. Here's a configuration you can use to make those Services appear:

Discussion:
This is a Bug Report Problem: section of page does not cover all required reference points which are mentioned throughout page. Proposed Solution: Add references of below topics under what's next section of page. learn about service, volume. kubelet, kubectl overview. Garbage Collection that Kubernetes uses to clean up cluster resources. Types of probes. Liveness, Readiness and Startup Probes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /language en /assign
/remove-kind bug /triage accepted I'm not sure how much we need to tell people about Services and Volumes; maybe we should instead signpost readers to learn more about Pods in general - perhaps links to specific fragments of relevant Pod pages? Same for garbage collection really.
Thanks for reply. In that case i will add one link in general to know more about pods and service under What's next section. For garbage collection its already available under what's next section. So i will not add reference link inside page.
Oops! it was my mistake, there is no reference link provided for under what's next section. will add this too.
Hi , Below, i prepared the preview changes what i am planning to do as per my understanding based your comment above. I would like to confirm is these changes you were expecting to do for this issue. ! Please suggest.
Hi Could you please confirm on above comment.
Hi Could you please take a look on Hi Please confirm if these changes sounds good to you. So that i can go ahead and work on it, Thanks.
When adding links, please use links that have words like “volumes”; readers don't need to see the URL. If you send in a pull request we can offer feedback on it directly. Ideally we can accept it as is!
Thanks for your response, i will soon open a PR for it.
Fixed it here .
Change:
- `KubeletTracing`: Add support for distributed tracing in the kubelet. When enabled, kubelet CRI interface and authenticated http servers are instrumented to generate OpenTelemetry trace spans. <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> - `LegacyServiceAccountTokenNoAutoGeneration`: Stop auto-generation of Secret-based [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens). - `LocalStorageCapacityIsolation`: Enable the consumption of

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:
FOO_SERVICE_PORT=<порт, на котором запущен сервис> ``` <del> Сервисы получают выделенные IP-адреса и доступны для контейнера через DNS, если включен [аддон DNS](https://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/). </del> <ins> Сервисы получают выделенные IP-адреса и доступны для контейнера через DNS, если включен [аддон DNS](https://releases.k8s.io/v{{< skew currentPatchVersion >}}/cluster/addons/dns/). </ins> ## {{% heading "whatsnext" %}}

Discussion:
Problem: Based on , I have created this issue/task to help update the [ru] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 33: Например, для установки версии {{< param "fullversion" }} на Linux введите: 36: {{< param "fullversion" }}/bin/linux/amd64/kubectl 110: Например, для установки версии {{< param "fullversion" }} на macOS введите: 113: {{< param "fullversion" }}/bin/darwin/amd64/kubectl 175: 1. Загрузите последний релиз {{< param "fullversion" }} по этой ссылке. 180: {{< param "fullversion" }} In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/concepts/containers/container- 44: DNS, если включен . /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/setup/learning- 222: чтобы запустить Minikube из-под версии {{< param "fullversion" }}, вам нужно выполнить следующую команду: 225: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 36: Например, команда загрузки версии {{< param "fullversion" }} для Linux будет выглядеть следующим образом 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: Например, команда загрузки версии {{< param "fullversion" }} для macOS будет выглядеть следующим образом 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 183: 1.

Загрузите последнюю версию {{< param "fullversion" }} по этой ссылкеe
Change:
title: Kubernetesのコンポーネント content_type: concept description: > <del> Kubernetesクラスターはコントロールプレーンやノードと呼ばれるマシン群といったコンポーネントからなります。 weight: 20 </del> <ins> Kubernetesクラスターはコントロールプレーンのコンポーネントとノードと呼ばれるマシン群で構成されています。 weight: 30 </ins> card: name: concepts weight: 20

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:
Patch your Deployment: ```shell <del> kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-no-retainkeys.yaml </del> <ins> kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-no-retainkeys.yaml </ins> ``` In the output, you can see that it is not possible to set `type` as `Recreate` when a value is defined for `spec.strategy.rollingUpdate`:

Discussion:
example commands are missing Resulting in: I will prepare a patch for this.
/triage accepted /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /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
Change:
You can project keys to specific paths and specific permissions on a per-file basis. The [Secrets](/docs/concepts/configuration/secret#using-secrets-as-files-from-a-pod) user guide explains the syntax. <del> ## Real World Example: Configuring Redis using a ConfigMap You can follow the steps below to configure a Redis cache using data stored in a ConfigMap. 1. Create a ConfigMap from the `docs/user-guide/configmap/redis/redis-config` file ```shell kubectl create configmap example-redis-config --from-file=docs/user-guide/configmap/redis/redis-config kubectl get configmap example-redis-config -o yaml ``` ```yaml apiVersion: v1 data: redis-config: | maxmemory 2mb maxmemory-policy allkeys-lru kind: ConfigMap metadata: creationTimestamp: 2016-03-30T18:14:41Z name: example-redis-config namespace: default resourceVersion: "24686" selfLink: /api/v1/namespaces/default/configmaps/example-redis-config uid: 460a2b6e-f6a3-11e5-8ae5-42010af00002 ``` 1. Create a pod specification that uses the config data stored in the ConfigMap: ```yaml apiVersion: v1 kind: Pod metadata: name: redis spec: containers: - name: redis image: kubernetes/redis:v1 env: - name: MASTER value: "true" ports: - containerPort: 6379 resources: limits: cpu: "0.1" volumeMounts: - mountPath: /redis-master-data name: data - mountPath: /redis-master name: config volumes: - name: data emptyDir: {} - name: config configMap: name: example-redis-config items: - key: redis-config path: redis.conf ``` 1. Create the pod. ```shell kubectl create -f docs/user-guide/configmap/redis/redis-pod.yaml ``` In the example, the config volume is mounted at `/redis-master`. It uses `path` to add the `redis-config` key to a file named `redis.conf`. The file path for the redis config, therefore, is `/redis-master/redis.conf`. This is where the image will look for the config file for the redis master. 1. Use `kubectl exec` to enter the pod and run the `redis-cli` tool to verify that the configuration was correctly applied: ```shell kubectl exec -it redis redis-cli 127.0.0.1:6379> CONFIG GET maxmemory 1) "maxmemory" 2) "2097152" 127.0.0.1:6379> CONFIG GET maxmemory-policy 1) "maxmemory-policy" 2) "allkeys-lru" ``` </del> {% endcapture %} {% capture discussion %}

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [x ] Feature Request Problem: As discussed in , the 'Real World Example' section of should probably be a separate tutorial. Proposed Solution: Create a new tutorial from the existing content (probably needs additional information). Remove the section from the task doc and replace with a 'What's Next' pointer to new tutorial doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
done
Change:
literal values. For example, the following instructions create a Kustomization file for the username `admin` and the password `1f2d1e2e67df`. <ins> {{< note >}} The `stringData` field for a Secret does not work well with server-side apply. {{< /note >}} </ins> ### Create the Kustomization file {{< tabs name="Secret data" >}}

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 Update the docs for server-side apply to mention that for a does not work well with - Update the docs for Secrets to mention that for a does not work well with Why is this needed etc Comments /language en /kind feature /triage accepted /priority backlog
See for more detail:
/assign I would raise a PR for fixing this issue.
This is only partially resolved by ...
Hi, , What do you mean "partially resolved"? I checked the list and only found 2 references, which have been fixed by Or anything else I missed?
I don't think we have address all cases. Am I missing anything?
Thanks . I am afraid that you are right. I will open another PR for fixing the other 2 links with hints.
Change:
Container Vulnerability Scanning and OS Dependency Security | As part of an image build step, you should scan your containers for known vulnerabilities. Image Signing and Enforcement | Sign container images to maintain a system of trust for the content of your containers. Disallow privileged users | When constructing containers, consult your documentation for how to create users inside of the containers that have the least level of operating system privilege necessary in order to carry out the goal of the container. <ins> Use container runtime with stronger isolation | Select [container runtime classes](/docs/concepts/containers/runtime-class/) that provider stronger isolation </ins> --> ## 容器

Discussion:
! Chinese page link can not open
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
/kind bug
Change:
## Running the website locally using Hugo <del> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L10) file. </del> <ins> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </ins> To build and test the site locally, run:

Discussion:
Under the the is pointing toward the wrong line in the file.
/assign
/retitle Incorrect line reference in within
/triage accepted