jiebi/CodeConvo huggingface dataset:
Change:
## Trusting TLS in a cluster <del> Trusting the [custom CA](#a-note-to-cluster-administrators) from an application running as a pod usually requires </del> <ins> Trusting the [custom CA](#configuring-your-cluster-to-provide-signing) from an application running as a pod usually requires </ins> some extra application configuration. You will need to add the CA certificate bundle to the list of CA certificates that the TLS client or server trusts. For example, you would do this with a golang TLS config by parsing the certificate

Discussion:
This is a Bug Report Problem: Following below hyperlinks are not working under task: and The reason for it is it both redirects to but the is changed to in this PR: Proposed Solution: Changed to for both dedicated CA and custom CA. Page to Update:
Also, the hyperlinks for both dedicated CA and custom CA were in this PR:
/assign /sig auth
Fixed it here:
/language en /triage accepted Thanks for spotting this
you're welcome!
Change:
Kubernetes assigns this Service an IP address (sometimes called the "cluster IP"), which is used by the Service proxies <del> (see [Virtual IPs and service proxies](#virtual-ips-and-service-proxies) below). </del> <ins> (see [Virtual IP addressing mechanism](#virtual-ip-addressing-mechanism) below). </ins> The controller for the Service selector continuously scans for Pods that match its selector, and then POSTs any updates to an Endpoint object

Discussion:
This is a Bug Report Problem: The Link for under is wrong. It doesn't redirect anywhere. It is redirected to the following link: instead of that, it should redirect to . contains the context of . Proposed Solution: Virtual IPs and service proxies should redirect to instead of Page to Update:
/assign /sig network /sig docs
Fixed it here:
/triage accepted
Change:
clear: both; } <del> .body-content > h3, .body-content > h4, .body-content > h5, .body-content > h6, .body-content > p, .body-content > ul > li, .body-content > ul > li { width: 52%; } .body-content table { </del> <ins> .body-content > * { </ins> width: 52%; }

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: Stylesheet does not limit width of <olfor larger screens. The config details in overflow its container. (I use mozilla firefox if it's required) Proposed Solution: Find a way to add, "width:52%;" attribute for <oltags in Stylesheet under " screen and (min-width: 992px)" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind bug /language en I'll try to make a PR to fix this if its fine.
I'm not sure that fixing just for elements is the right approach. Maybe fix it for or, if there need to be exceptions, ?
/priority important-longterm
I see. I suggested changing just <oltag previously since the generated stylesheet had mentioned for lot of them individually.
I built website locally and navigated to "http://localhost:1313/docs/reference/generated/kubectl/kubectl-commands#config". It says error 404. When i manually add .html to the url then i can view the page. Is this normal?
Change:
You will need to have the following tools installed: <del> - `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/)) </del> <ins> - `cosign` ([install guide](https://docs.sigstore.dev/cosign/system_config/installation/)) </ins> - `curl` (often provided by your operating system) - `jq` ([download jq](https://jqlang.github.io/jq/download/))

Discussion:
in this page the link about Verify Signed Kubernetes Artifacts for install cosign changed --- !
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
It is a documentation issue, Docs issues are implemented in . Please open in this repo.
/transfer website
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig doc 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
/kind bug /kind documentation
Change:
## डेप्लॉयमेंट बनाएँ <del> कुबेरनेट्स [*पॉड*](/hi/docs/concepts/workloads/pods/) एक या अधिक कंटेनरों का एक समूह है, </del> <ins> कुबेरनेट्स [*पॉड*](/docs/concepts/workloads/pods/) एक या अधिक कंटेनरों का एक समूह है, </ins> जो प्रशासन और नेटवर्किंग के उद्देश्यों के लिए एक साथ बंधे होते हैं। इस ट्यूटोरियल के पॉड में केवल एक कंटेनर है। कुबेरनेट्स <del> [*डेप्लॉयमेंट*](/hi/docs/concepts/workloads/controllers/deployment/) आपके पॉड के स्वास्थ्य की </del> <ins> [*डेप्लॉयमेंट*](/docs/concepts/workloads/controllers/deployment/) आपके पॉड के स्वास्थ्य की </ins> जाँच करता है और यदि पॉड बंद हो जाता है तो पॉड के कंटेनर को पुनः आरंभ करता है। पॉड्स के निर्माण और स्केलिंग को प्रबंधित करने के लिए डेप्लॉयमेंट अनुशंसित तरीका है।

Discussion:
Problem: There are broken link in page. Proposed Solution: --Page to Update:
/triage accepted
/assign
Is the issue still open, anyone working?
Yes, I'm working on it!!
/area localization
I think has already raised a PR!
PR working on this issue
Change:
* Fetch the `cluster-info` file from the API Server: ```shell <del> kubectl -n kube-public get cm cluster-info -o yaml | grep "kubeconfig:" -A11 | grep "apiVersion" -A10 | sed "s/    //" | tee cluster-info.yaml </del> <ins> kubectl -n kube-public get cm cluster-info -o jsonpath='{.data.kubeconfig}' | tee cluster-info.yaml </ins> ``` The output is similar to this:

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. --The current documentation for suggests the use of a combination of with / to extract the contents of the field from the ConfigMap. However, has the option that allows us to extract such field without the need of parsing it through /. 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. --Update the command to use instead. Why is this needed It provides data extraction with less steps and less risk of error if the content format changes in the future. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --N/A /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:
### MutatingAdmissionWebhook {#mutatingadmissionwebhook} <del> {{< feature-state for_k8s_version="v1.13" state="beta" >}} </del> This admission controller calls any mutating webhooks which match the request. Matching webhooks are called in serial; each one may modify the object if it desires.

Discussion:
This is a Bug Report It's not a bug, just an outdated doc thing. Problem: The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to in . But the docs still show that they are in beta state at and . Proposed Solution: the description from the two plug-ins. the descriptions of the two plug-ins if they need an update too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it. /assign
/triage accepted
Change:
the `spec.renewTime` field for the Lease. The Kubernetes control plane uses the time stamp of this field to determine the availability of this `Node`. <del> See [Node Lease objects](/docs/concepts/architecture/nodes/#heartbeats) for more details. </del> <ins> See [Node Lease objects](/docs/concepts/architecture/nodes/#node-heartbeats) for more details. </ins> ## Leader election

Discussion:
This is a Bug Report The link provided for [Node Lease objects] is wrong <!--Required Information--Problem: The provided link is navigating to top of the page not to corresponding sub section. Proposed Solution: URL link should be 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:
You can acquire all these from the [nginx https example](https://github.com/kubernetes/examples/tree/{{< param "githubbranch" >}}/staging/https-nginx/). This requires having go and make tools installed. If you don't want to install those, then follow the manual steps later. In short: --> <del> ## Service 安全 </del> <ins> ## 保护 Service {#securing-the-service} </ins> <del> 到现在为止，我们只在集群内部访问了 Nginx server。在将 Service 暴露到 Internet 之前，我们希望确保通信信道是安全的。对于这可能需要： </del> <ins> 到现在为止，我们只在集群内部访问了 Nginx 服务器。在将 Service 暴露到因特网之前，我们希望确保通信信道是安全的。 为实现这一目的，可能需要： </ins> <del> * https 自签名证书（除非已经有了一个识别身份的证书） * 使用证书配置的 Nginx server </del> <ins> * 用于 HTTPS 的自签名证书（除非已经有了一个识别身份的证书） * 使用证书配置的 Nginx 服务器 </ins> * 使证书可以访问 Pod 的 [Secret](/zh/docs/concepts/configuration/secret/) <del> 可以从 [Nginx https 示例](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/examples/https-nginx/) 获取所有上述内容，简明示例如下： </del> <ins> 你可以从 [Nginx https 示例](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/staging/https-nginx/) 获取所有上述内容。你需要安装 go 和 make 工具。如果你不想安装这些软件，可以按照 后文所述的手动执行步骤执行操作。简要过程如下： </ins> ```shell make keys KEY=/tmp/nginx.key CERT=/tmp/nginx.crt

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:
``` NAME             READY   STATUS    RESTARTS   AGE <del> frontend-b2zdv   1/1     Running   0          6m36s frontend-vcmts   1/1     Running   0          6m36s frontend-wtsmm   1/1     Running   0          6m36s </del> <ins> frontend-gbgfx   1/1     Running   0          10m frontend-rwz57   1/1     Running   0          10m frontend-wkl7w   1/1     Running   0          10m </ins> ``` You can also verify that the owner reference of these pods is set to the frontend ReplicaSet. To do this, get the yaml of one of the Pods running: ```shell <del> kubectl get pods frontend-b2zdv -o yaml </del> <ins> kubectl get pods frontend-gbgfx -o yaml </ins> ``` The output will look similar to this, with the frontend ReplicaSet's info set in the metadata's ownerReferences field:

Discussion:
Hi Currently we obsrved that following image is not availble
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 /sig docs
can you please provide the page link of the issue?
HI Kubernetes/Website PFA link
/retitle Container image is not available for /kind bug
This looks similar to issue we already have I think it is a duplicate. /triage duplicate
Thanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned
Closing this issue, marking it as "Not Planned". <detailsIn response to : Thanks for raising this! 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:
port: 20250 serializeImagePulls: false evictionHard: <del> memory.available:  "200Mi" </del> <ins> memory.available:  "100Mi" nodefs.available:  "10%" nodefs.inodesFree: "5%" imagefs.available: "15%" </ins> ``` <del> In the example, the kubelet is configured to serve on IP address 192.168.0.8 and port 20250, pull images in parallel, and evict Pods when available memory drops below 200Mi. Since only one of the four evictionHard thresholds is configured, other evictionHard thresholds are reset to 0 from their built-in defaults. All other kubelet configuration values are left at their built-in defaults, unless overridden by flags. Command line flags which target the same value as a config file will override that value. </del> <ins> In this example, the kubelet is configured with the following settings: 1. `address`: The kubelet will serve on IP address `192.168.0.8`. 2. `port`: The kubelet will serve on port `20250`. 3. `serializeImagePulls`: Image pulls will be done in parallel. 4. `evictionHard`: The kubelet will evict Pods under one of the following conditions: - When the node's available memory drops below 100MiB. - When the node's main filesystem's available space is less than 10%. - When the image filesystem's available space is less than 15%. - When more than 95% of the node's main filesystem's inodes are in use. </ins> {{< note >}} In the example, by changing the default value of only one parameter for

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: As we know that, in eviction hard thresholds, when we change the default value of any one of the four parameters (memory.available, nodefs.available, imagefs.available, nodefs.inodesFree), then the value of other parameters will be set to 0. Although this is an expected behaviour but I think it's not a good motivation for user to change only the one parameter as given in this . As setting other parameters to 0 is not a good scenario. Proposed Solution: Is there any good case by setting the other parameters to 0 or we should change the example to motivate users to change all parameters 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 en
/retitle Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes
/remove-kind bug /kind feature
/assign
Change:
## 設定 <ins> * [例: Javaのマイクロサービスの設定](/docs/tutorials/configuration/configure-java-microservice/) </ins> * [ConfigMapを用いたRedisの設定](/ja/docs/tutorials/configuration/configure-redis-using-configmap/) ## ステートレスアプリケーション

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. --Update Japanese translation of Why is this needed It seems be outdated a bit Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
I0710 14:43:38.274797    3655 portforward.go:225] Forwarding from [::1]:7000 -> 6379 ``` <ins> {{< note >}} `kubectl port-forward` does not return. To continue with the exercises, you will need to open another terminal. {{< /note >}} </ins> 2.  Start the Redis command line interface: ```shell

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--On the page: Under the section: Forward a local port to a port on the Pod This page suggests using kubectl port-forward to forward ports to your pod. However, kubectl port-forward does not return, it is not daemonized by default. The page does not note this fact Proposed Solution: Either: modify the page to indicate that kubectl port-forward will not return, and that the user needs to open another terminal window to continue with the exercises; OR modify the kubectl port-forward commands to include a & (ampersand) at the end of the line, so that the job will run in the background and return to the terminal prompt. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/assign
Maybe adding a flag to is a better way to solve this problem, such as ?
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
/remove-lifecycle stale
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
/remove-lifecycle stale
Change:
<ins> --- title: コミュニティ layout: basic cid: community css: /css/community.css --- <div class="community_main"> <h1>Kubernetesコミュニティ行動規範</h1> Kubernetesは、<a href="https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/jp.md">CNCF行動規範</a>に従います。 以下のCNCFの行動規範のテキストは、<a href="https://github.com/cncf/foundation/blob/214585e24aab747fb85c2ea44fbf4a2442e30de6/code-of-conduct-languages/jp.md">commit 214585e</a>から複製したものです。この掲示が古くなっていることに気がついた場合には、<a href="https://github.com/kubernetes/website/issues/new">issueを作成</a>してください。 イベント、ミーティング、Slack、その他のコミュニケーション手段において行動規範の違反を見つけた場合には、<a href="https://git.k8s.io/community/committee-code-of-conduct">Kubernetes Code of Conduct Committee(行動規範委員会)</a>に連絡してください。連絡はメールアドレス<a href="mailto:conduct@kubernetes.io">conduct@kubernetes.io</a>から行えます。連絡者の匿名性は守られます。 <div class="cncf_coc_container"> {{< include "static/cncf-code-of-conduct.md" >}} </div> </div> </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
Change:
so we have to tell curl to ignore the CName mismatch. By creating a Service we linked the CName used in the certificate with the actual DNS name used by pods during Service lookup. Let's test this from a pod (the same secret is being reused for simplicity, the pod only needs nginx.crt to access the Service): --> <del> 注意最后一步我们是如何提供 `-k` 参数执行 curl命令的，这是因为在证书生成时， 我们不知道任何关于运行 Nginx 的 Pod 的信息，所以不得不在执行 curl 命令时忽略 CName 不匹配的情况。 通过创建 Service，我们连接了在证书中的 CName 与在 Service 查询时被 Pod使用的实际 DNS 名字。 </del> <ins> 注意最后一步我们是如何提供 `-k` 参数执行 curl 命令的，这是因为在证书生成时， 我们不知道任何关于运行 nginx 的 Pod 的信息，所以不得不在执行 curl 命令时忽略 CName 不匹配的情况。 通过创建 Service，我们连接了在证书中的 CName 与在 Service 查询时被 Pod 使用的实际 DNS 名字。 </ins> 让我们从一个 Pod 来测试（为了简化使用同一个秘钥，Pod 仅需要使用 nginx.crt 去访问 Service）： {{< codenew file="service/networking/curlpod.yaml" >}}

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:
そのRuntimeClassリソースは現時点で2つの重要なフィールドを持ちます。それはRuntimeClassの名前(`metadata.name`)とハンドラー(`handler`)です。そのオブジェクトの定義は下記のようになります。 ```yaml <del> apiVersion: node.k8s.io/v1beta1  # RuntimeClassはnode.k8s.ioというAPIグループで定義されます。 </del> <ins> # RuntimeClassはnode.k8s.ioというAPIグループで定義されます。 apiVersion: node.k8s.io/v1 </ins> kind: RuntimeClass metadata: <del> name: myclass  # RuntimeClass名 </del> <ins> # RuntimeClass名 </ins> # RuntimeClassはネームスペースなしのリソースです。 <del> handler: myconfiguration  # 対応するCRI設定 </del> <ins> name: myclass # 対応するCRI設定 handler: myconfiguration </ins> ``` RuntimeClassオブジェクトの名前は[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)に従う必要があります。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
[community_youtube_name] other = "YouTube" <ins> [cve_id] other = "CVE ID" [cve_issue_url] other = "CVE 깃헙 이슈 URL" [cve_json_external_url] other = "외부 URL" [cve_json_id] other = "id" [cve_json_summary] other = "요약" [cve_json_url] other = "url" [cve_summary] other = "이슈 요약" [cve_table] other = "공식 쿠버네티스 CVE 목록" [cve_url] other = "CVE URL" </ins> [deprecation_title] other = "해당 문서의 쿠버네티스 버전:"

Discussion:
What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language ko
/triage accepted Thanks !
/assign