jiebi/CodeConvo huggingface dataset:
Change:
* Wait for a {{< glossary_tooltip text="Service" term_id="service">}} to be created, using a shell one-line command like: ```shell <del> for i in {1..100}; do sleep 1; if dig myservice; then exit 0; fi; done; exit 1 </del> <ins> for i in {1..100}; do sleep 1; if nslookup myservice; then exit 0; fi; done; exit 1 </ins> ``` * Register this Pod with a remote server from the downward API with a command like:

Discussion:
This example... has an issue. dig always returns true "0" regardless of whether the name resolves, so if the intent is that 'dig myservice' should be replaced with the dns name of the services this will always loop to 100 and end. perhaps this should be: will filter NXDOMAIN (failing DNS)
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
Ref Link : /sig docs /language en
I agree with you about this modification of command. the script will exit successfully when it detects a failed DNS resolution (NXDOMAIN)
/kind support
/remove-kind support
Agree that the always returns true "0" regardless of whether the service exists. But the scenario is . The still does not work, because If the does not exist, the command returns 0, and the script exits 0. We can not wait for the service. To wait for the service to be created, we can replace with since "nslookup returns with an exit status of 1 if any query failed, and 0 otherwise."
Thanks abel8! nslookup is better with its exit behavior. And the example reads cleaner without the extra pipe and complexity. Nice! Thanks!
you had raised the PR to fix the issue so you can assign this issue to yourself. /assign
Change:
Different kinds of object can also have different `.status`; again, the API reference pages detail the structure of that `.status` field, and its content for each different type of object. <ins> {{< note >}} See [Configuration Best Practices](/docs/concepts/configuration/overview/) for additional information on writing YAML configuration files. {{< /note >}} </ins> ## Server side field validation Starting with Kubernetes v1.25, the API server offers server side

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 describes a bug in Kubernetes where YAML 1.2 documents are not parsed (Kubernetes does not have good support for YAML 1.1), but then also Kubernetes does incorrectly parse completely valid YAML 1.1 the way that the specification defines. Why is this needed The bug makes it hard for some people, using conformant libraries, to make YAML documents that Kubernetes accepts. We should document the bug so that readers are aware of the shortcomings here. Comments /wg api-expression /language en /priority backlog
/triage accepted
i can help you because I'm new to it so if i can tag along i will be able to learn a lot
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
would you add this as a warning note in ?
/assign
Change:
description: "一般的なタスク、そのタスクを短い手順でどのように実行するかを見てみます。" button: "タスクを見る" button_path: "/docs/tasks" <del> - name: training title: "トレーニング" description: "Kubernetesの資格を取得して、クラウドネイティブプロジェクトを成功させます！" button: "トレーニングを見る" button_path: "/training" </del> - name: reference title: "リファレンス情報を調べる" description: "用語、コマンドラインの構文、APIリソースタイプ、そして構築ツールのドキュメントを見て回ります。"

Discussion:
This is a Feature Request Update Why is this needed Many people view this page. Updating the links on this page is useful for many people. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/assign /language ja /area localization
/triage accepted
Change:
<generator>Hugo -- gohugo.io</generator> <language>en-US</language> <copyright>{{ .Site.Params.Copyright_k8s }}</copyright> <ins> <!-- Render last build date only if CVE feed is available, accommodating for offline builds. --> {{- if ne $feed nil -}} </ins> <lastBuildDate>{{ time.Format "Mon, 02 Jan 2006 15:04:05 -0700" $feed._kubernetes_io.updated_at | safeHTML }}</lastBuildDate> <ins> {{- end -}} </ins> {{ with .OutputFormats.Get "RSS" -}} {{ printf "<atom:link href=%q rel="self" type=%q />" .Permalink .MediaType | safeHTML }} {{ end -}}

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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign
Change:
{{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}. --> Kubernetes 通过将容器放入在节点（Node）上运行的 Pod 中来执行你的工作负载。 <del> 节点可以是一个虚拟机或者物理机器，取决于所在的集群配置。每个节点由 {{< glossary_tooltip text="控制面" term_id="control-plane" >}} 负责管理， 并包含运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所需的服务。 </del> <ins> 节点可以是一个虚拟机或者物理机器，取决于所在的集群配置。 每个节点包含运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所需的服务， 这些 Pods 由 {{< glossary_tooltip text="控制面" term_id="control-plane" >}} 负责管理。 </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: ! 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:
{{% code_sample file="application/web/web.yaml" %}} You will need to use at least two terminal windows. In the first terminal, use <del> [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to watch the creation </del> <ins> [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to {{< glossary_tooltip text="watch" term_id="watch" >}} the creation </ins> of the StatefulSet's Pods. ```shell

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 to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.
Change:
[deprecation_warning] other = " のドキュメントは積極的にメンテナンスされていません。現在表示されているバージョンはスナップショットです。最新のドキュメントはこちらです: " <ins> [dockershim_message] other = """dockershimは1.24のリリースをもってKubernetesプロジェクトから削除されました。詳しくは、<a href="/ja/dockershim">dockershimの削除に関するFAQ</a>をご覧ください。""" </ins> [docs_label_browse] other = "ドキュメントの参照"

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. --Add japanese translations of the contents listed below: {{% dockershim-removal %}} block Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref.
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 ja
Change:
## コンフィギュレーションを上書きします <del> `Node Problem Detector`の Dockerイメージをビルドする際に、[default configuration(https://github.com/kubernetes/node-problem-detector/tree/v0.1/config)が埋め込まれます。 </del> <ins> `Node Problem Detector`の Dockerイメージをビルドする際に、[default configuration](https://github.com/kubernetes/node-problem-detector/tree/v0.1/config)が埋め込まれます。 </ins> [`ConfigMap`](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/) を使用することで設定を上書きすることができます。

Discussion:
as of now : [default configuration(https://..... expected : [default configuration](https://... <img width="800" alt="Screen Shot 2022-06-24 at 18 40 25" src="https://user-"
/triage accepted /language ja
/assign
Change:
<p>We hit a different Pod with every request. This demonstrates that the load-balancing is working.</p> --> <p>我们每个请求都命中了不同的 Pod，这证明负载均衡正在工作。</p> <del> {{< note >}} </del> <!-- <del> <p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> </del> <ins> <p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> </ins> <p>In a separate terminal window, execute:<br> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> <ins> <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <code><b>curl 127.0.0.1:51082</b></code></p> </ins> --> <ins> {{< note >}} </ins> <p>如果你使用 Docker Desktop 作为容器驱动程序运行 minikube，则需要 minikube 隧道。 这是因为 Docker Desktop 内的容器与主机隔离。<br> <p>在单独的终端窗口中，执行：<br> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> <del> <!-- <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <code><b>curl 127.0.0.1:51082</b></code></p> --> </del> <p>输出看起来像这样： <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>然后使用给定的 URL 访问应用程序：

Discussion:
Chinese document display in raw html format. <img width="868" alt="image" src=""
/language zh
/kind bug
Related page: /retitle [zh] Displays Raw Html data in tutorials page
/sig docs /triage accepted /priority backlog
As per original site, this part should look something like this - !
/assign
Change:
<!-- Following are the manual steps to follow in case you run into problems running make (on windows for example): --> <del> 以下是您在运行make时遇到问题时要遵循的手动步骤（例如，在Windows上）： </del> <ins> 以下是你在运行 make 时遇到问题时要遵循的手动步骤（例如，在 Windows 上）： </ins> ```shell # Create a public private key pair

Discussion:
Nginx https 404
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 It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
Requires the CPUManager feature gate to be enabled. Dynamic Kubelet Config (beta): This field should not be updated without a full node reboot. It is safest to keep this value the same as the local config. <del> Default: "none"</td> </del> <ins> Default: "None"</td> </ins> </tr>

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. Page to Update:
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 take up this ticket.
Change:
slug: are-you-ready-for-dockershim-removal --- <ins> {{< note >}} This poll will close on January 7, 2022. {{</ note >}} </ins> **Author:** Sergey Kanzhelev, Google. With reviews from Davanum Srinivas, Elana Hashman, Noah Kantrowitz, Rey Lejano. Last year we announced that Dockershim is being deprecated: [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/).

Discussion:
Pre the first alpha cut of 1.24, a blog post should be drafted expressing the project's understanding that many users have not migrated off of dockershim, and migration can be painful but its needed for a variety of reasons and we are committed to documenting and making it as easy as possible. /assign (For visibility) /assign sig-arch / sig-node (please loop in / assign others) /assign (for myself to keep track of) /sig node architecture /priority important-soon /area blog
:100: /triage accepted
hoping can cover for me! also cc
/assign
I started the draft, which is super rough and doesnt' have all the outline yet:
IMO the draft is in a good enough place to be converted to a PR.
Change:
다음은 쿠버네티스가 애플리케이션의 파드를 어떻게 관리하는지를 알 수 있게 해주는 두 가지 개념이다. <del> * [가비지(Garbage) 수집](/ko/docs/concepts/workloads/controllers/garbage-collection/)은 _소유하는 리소스_ 가 </del> <ins> * [가비지(Garbage) 수집](/ko/docs/concepts/architecture/garbage-collection/)은 _소유하는 리소스_ 가 </ins> 제거된 후 클러스터에서 오브젝트를 정리한다. * [_time-to-live after finished_ 컨트롤러](/ko/docs/concepts/workloads/controllers/ttlafterfinished/)는 잡이 완료된 이후에 정의된 시간이 경과되면 잡을 제거한다.

Discussion:
This is a Feature Request Translate in Korean What would you like to be Translate in Korean Why is this needed This file is not translated yet. Comments Page to translate : /language ko /assign Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
Resolved by page: /close
Closing this issue. <detailsIn response to : Resolved by 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:
<ins> --- title: लिमिटरेंज (LimitRange) id: limitrange date: 2019-04-15 full_link:  /docs/concepts/policy/limit-range/ short_description: > नेमस्पेस में प्रति कंटेनर या पॉड में संसाधन खपत को सीमित करने के लिए प्रतिबंध प्रदान करता है। aka: tags: - core-object - fundamental - architecture related: - pod - container --- नेमस्पेस में प्रति {{< glossary_tooltip text="कंटेनर" term_id="container" >}} या {{< glossary_tooltip text="पॉड" term_id="pod" >}} में संसाधन खपत को सीमित करने के लिए प्रतिबंध प्रदान करता है। <!--more--> लिमिटरेंज, टाइप (type) द्वारा बनाई जा सकने वाले ऑब्जेक्ट्स और साथ ही नेमस्पेस में अलग-अलग {{< glossary_tooltip text="कंटेनर" term_id="container" >}} या {{< glossary_tooltip text="पॉड" term_id="pod" >}} द्वारा अनुरोध/उपभोग किए जा सकने वाले कंप्यूट संसाधनों की मात्रा को सीमित करता है। </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 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
Ahan! A great approach to helping new contributors. Sorry I missed that point. /unassign
Hello Team, This is my first issue on kubernetes/website. I would like to work on it /assign
Keep working on this issue. Feel free to raise a PR
Change:
The next step is to define a context for the kubectl client to work in each namespace. The value of "cluster" and "user" fields are copied from the current context. ```shell <del> $ kubectl config set-context dev --namespace=development --cluster=lithe-cocoa-92103_kubernetes --user=lithe-cocoa-92103_kubernetes $ kubectl config set-context prod --namespace=production --cluster=lithe-cocoa-92103_kubernetes --user=lithe-cocoa-92103_kubernetes </del> <ins> $ kubectl config set-context dev --namespace=development  --cluster=lithe-cocoa-92103_kubernetes  --user=lithe-cocoa-92103_kubernetes $ kubectl config set-context prod --namespace=production  --cluster=lithe-cocoa-92103_kubernetes  --user=lithe-cocoa-92103_kubernetes </ins> ``` <del> The above commands provided two request contexts you can alternate against depending on what namespace you wish to work against. </del> <ins> By default, the above commands adds two contexts that are saved into file `.kube/config`. You can now view the contexts and alternate against the two new request contexts depending on which namespace you wish to work against. To view the new contexts: ```shell $ kubectl config view apiVersion: v1 clusters: - cluster: certificate-authority-data: REDACTED server: https://130.211.122.180 name: lithe-cocoa-92103_kubernetes contexts: - context: cluster: lithe-cocoa-92103_kubernetes user: lithe-cocoa-92103_kubernetes name: lithe-cocoa-92103_kubernetes - context: cluster: lithe-cocoa-92103_kubernetes namespace: development user: lithe-cocoa-92103_kubernetes name: dev - context: cluster: lithe-cocoa-92103_kubernetes namespace: production user: lithe-cocoa-92103_kubernetes name: prod current-context: lithe-cocoa-92103_kubernetes kind: Config preferences: {} users: - name: lithe-cocoa-92103_kubernetes user: client-certificate-data: REDACTED client-key-data: REDACTED token: 65rZW78y8HbwXXtSXuUw9DbP4FLjHi4b - name: lithe-cocoa-92103_kubernetes-basic-auth user: password: h5M0FtUUIflBSdI7 username: admin </ins> Let's switch to operate in the development namespace.

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: Add the steps to get back out of the kubectl context after running the commands Proposed Solution: point out that the .kube folder has a config file that holds the info 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. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
### Internal traffic policy <del> {{< feature-state for_k8s_version="v1.22" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> You can set the `.spec.internalTrafficPolicy` field to control how traffic from internal sources is routed. Valid values are `Cluster` and `Local`. Set the field to

Discussion:
This is a Bug Report Problem: The FEATURE STATE of the following features is mentioned wrongly(outdated) under the docs: : The corresponding feature gate is and mentioned Feature State is : The corresponding feature gate is and mentioned Feature State is Proposed Solution: According to the docs, for Feature State should be and for Feature State should be Page to Update:
/language en /sig docs /sig network
/assign
Fixed it here:
/retitle Feature gates and incorrectly marked as beta
/triage accepted
Change:
$ kubectl cluster-info Kubernetes master is running at https://108.59.85.141 KubeDNS is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kube-dns/proxy <del> KubeUI is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kube-ui/proxy </del> <ins> kubernetes-dashboard is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy </ins> Grafana is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy Heapster is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-heapster/proxy InfluxDB is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy

Discussion:
Connect with Proxies references kube ui. It should use the kube dashboard instead.
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. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Change:
<ins> apiVersion: v1 kind: Service metadata: name: my-service labels: app: MyApp spec: ipFamilies: - IPv6 selector: app: MyApp ports: - protocol: TCP port: 80 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: sa-token-test spec: containers: - name: container-test image: busybox:1.28 volumeMounts: - name: token-vol mountPath: "/service-account" readOnly: true serviceAccountName: default volumes: - name: token-vol projected: sources: - serviceAccountToken: audience: api expirationSeconds: 3600 path: token </ins>

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /kind feature /language es /sig docs
Hi Rodolfo, I will take it!
/assign
algún avance al respecto?
disculpa. Lo terminaré hoy, gracias por recordarmenlo Victor.