jiebi/CodeConvo huggingface dataset:
Change:
<ins> --- title: Gateway API id: gateway-api date: 2023-10-19 full_link: /docs/concepts/services-networking/gateway/ short_description: > An API for modeling service networking in Kubernetes. aka: tags: - networking - architecture - extension --- A family of API kinds for modeling service networking in Kubernetes. <!--more--> Gateway API provides a family of extensible, role-oriented, protocol-aware API kinds for modeling service networking in Kubernetes. </ins>

Discussion:
This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new "Gateway API" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the "Ingress" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the "Service" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign
checkout the gateway API in the section and look out for the bugs
/triage accepted /priority important-longterm
How about adding a short link eg that redirects (302) to https://gateway- ?
I'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.
Also see
Change:
resources: * [Installation](https://github.com/sigstore/cosign#installation) <del> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config) </del> <ins> * [Configuration Options](https://github.com/sigstore/cosign/blob/main/USAGE.md#detailed-usage) </ins>

Discussion:
The and link in the section are broken.
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 don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -
Change:
<ins> --- title: Replica id: replica date: 2023-06-11 full_link: short_description: > Replicas are copies of pods, ensuring availability, scalability, and fault tolerance by maintaining identical instances. aka: tags: - fundamental - workload --- A copy or duplicate of a {{< glossary_tooltip text="Pod" term_id="pod" >}} or a set of pods. Replicas ensure high availability, scalability, and fault tolerance by maintaining multiple identical instances of a pod. <!--more--> Replicas are commonly used in Kubernetes to achieve the desired application state and reliability. They enable workload scaling and distribution across multiple nodes in a cluster. By defining the number of replicas in a Deployment or ReplicaSet, Kubernetes ensures that the specified number of instances are running, automatically adjusting the count as needed. Replica management allows for efficient load balancing, rolling updates, and self-healing capabilities in a Kubernetes cluster. </ins>

Discussion:
Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign
Change:
... ``` <del> contains a single `from` element allowing connections from Pods with the label `role=client` in namespaces with the label `user=alice`. But *this* policy: </del> <ins> This policy contains a single `from` element allowing connections from Pods with the label `role=client` in namespaces with the label `user=alice`. But the following policy is different: </ins> ```yaml ...

Discussion:
I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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
/retitle Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign
Change:
컨테이너는 CPU 1개를 요구하는 컨테이너의 절반만큼 CPU를 보장한다. `0.1` 이라는 표현은 "백 밀리cpu"로 읽을 수 있는 `100m` 표현과 동일하다. 어떤 사람들은 "백 밀리코어"라고 말하는데, 같은 것을 의미하는 것으로 이해된다. <del> `0.1` 과 같이 소수점이 있는 요청은 API에 의해 `100m` 로 변환되며, `1m` 도 허용되지 않게 정밀하다. 이러한 이유로, `100m` 형식이 선호될 수 있다. </del> <ins> `0.1` 과 같이 소수점이 있는 요청은 API에 의해 `100m` 으로 변환되며, `1m` 보다 더 정밀한 단위는 허용되지 않는다. 이러한 이유로, `100m` 과 같은 형식이 선호될 수 있다. </ins> CPU는 항상 절대 수량으로 요청되며, 상대적 수량은 아니다. 0.1은 단일 코어, 이중 코어 또는 48코어 시스템에서 동일한 양의 CPU이다.

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: ] ] Proposed Solution: Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko /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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: A request with a decimal point, like , is converted to by the API, and precision finer than is not allowed. For this reason, the form might be preferred. API , . , . API , . , . - <!--Kubernetes Version:--/good-first-issue </details
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:
* For IPv4 endpoints, the DNS system creates A records. * For IPv6 endpoints, the DNS system creates AAAA records. <ins> When you define a headless Service without a selector, the `port` must match the `targetPort`. </ins> ## Discovering services For clients running inside your cluster, Kubernetes supports two primary modes of

Discussion:
Need to mention that for headless services without selector, the Port need to be the same as the TargetPort.
hey, can i get some more context related to this? I would like to work on this issue
you can see some information about this here: do we really need port for a headless service? | | | | | | do we really need port for a headless service? It might be a question based on curiosity which couldn't find help on google.Consider this part of the yaml fo... | | | Headless service targetPort not resolving containerPort name · Issue · kubernetes/kubernetes | | | | | | Headless service targetPort not resolving containerPort name · Issue ... It seems that my headless service definition does not correctly resolve the containerPort name. I receive this e... | | | On Friday, March 10, 2023 at 10:17:59 PM MST, Khush Patibandha hey, can i get some more context related to this? I would like to work on this issue — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID:
/sig network /kind bug /triage accepted /retitle Service concept unclear on vs consistency for headless Services
Fixed on
See for the PR we should review here.
Change:
<ins> FROM node:6.14.2 EXPOSE 8080 COPY server.js . CMD [ "node", "server.js" ] </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: is a missing page; however, is part of the for a localization. Proposed Solution: Localize “Hello Minikube” into Spanish Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language es /kind bug
/assign
Change:
FOO_SERVICE_PORT=<サービスが実行されているポート> ``` <del> サービスは専用のIPアドレスを持ち、[DNSアドオン](http://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/)が有効の場合、DNSを介してコンテナで利用可能です。 </del> <ins> サービスは専用のIPアドレスを持ち、[DNSアドオン](http://releases.k8s.io/v{{< skew currentPatchVersion >}}/cluster/addons/dns/)が有効の場合、DNSを介してコンテナで利用可能です。 </ins>

Discussion:
Problem: Based on , I have created this issue/task to help update the [ja] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ja" /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/containers/container- 46: IPDNS /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- 146: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- 283: )Service /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- 220: {{< param "fullversion" }}: 223: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- 34: Linux{{< param "fullversion" }}: 37: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: macOS{{< param "fullversion" }}: 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 181: {{< 181: "fullversion" }}){{< param "fullversion" }} 186: curl -LO {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- 107: Kubernetes{{< param "fullversion" }} 111: releases/latest/download/kube- kubectl apply -f - 150: .PrepareNode.

ps1 -KubernetesVersion {{% param "fullversion" %}} /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- 35: # {{% param "fullversion" %}} 36: -Lo C:k {{% param "fullversion" %}} 70: -Lo C:k {{% param "fullversion" %}} 86: {{< param "fullversion" }}: 89: releases/latest/download/kube- kubectl apply -f - /sig docs /sig localization /language ja cc:
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: Page to Update: /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services-networking/connect-applications- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/concepts/services- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/setup/learning- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/tools/install- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/adding-windows- /home/rdlugyhe/kubernetes/k8s-website/content/ja/docs/tasks/administer-cluster/kubeadm/upgrading-windows- /sig localization /language ja cc: 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
cc:
/triage accepted /area localization /priority backlog
Change:
Once you have a running Kubernetes cluster, you can deploy your containerized applications on top of it. To do so, you create a Kubernetes <b>Deployment</b> configuration. The Deployment instructs Kubernetes how to create and update instances of your application. Once you've created a Deployment, the Kubernetes <del> master schedules mentioned application instances onto individual Nodes in the cluster. </del> <ins> master schedules the application instances included in that Deployment to run on individual Nodes in the cluster. </ins> </p> <p>Once the application instances are created, a Kubernetes Deployment Controller continuously monitors those instances. If the Node hosting an instance goes down or is deleted, the Deployment controller replaces the instance with an instance on another Node in the cluster. <b>This provides a self-healing mechanism to address machine failure or maintenance.</b></p>

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: There's either a typo in the of Module 2 of the tutorial, or the sentence is very awkwardly worded. The sentence: Once you've created a Deployment, the Kubernetes master schedules mentioned application instances onto individual Nodes in the cluster. doesn't appear to make any sense. Is the Kubernetes master scheduling the "mentioned application instances"? What application instances were mentioned? What does "scheduling" in this context mean? Proposed Solution: If this sentence is written as intended, it could use clarification. However it seems like there might be one or more typos, where words have been accidentally substituted. Those substitutions should be corrected if that's the case. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I think the sentence is true. It looks like there is room to clarify and improve the wording. explains scheduling in a Kubernetes context. <hr /Does this wording work better ?
I think that's an improvement and I believe I understand the sentence as intended now. I think my confusion largely stemmed from the word "mentioned." My understanding now is that "mentioned application instances" in this context means "the application instances mentioned in the Deployment you've created," right? So maybe: I think "scheduling" might be another point of confusion, just because it's only been mentioned in the tutorial once before: . It might not be necessary to give an expanded definition of scheduling here, but I do think the phrasing used in that previous mention of scheduling is more accessible: "schedules ... to run on the cluster's nodes" rather than "schedules ... onto individual Nodes". "Scheduling something" is a familiar phrase, but "scheduling something onto something" is a little less clear at first. So then maybe: ?
- would you also be interesting in proposing that fix as a pull request?
Done!
Change:
### Approve Certificate Request <del> Use kubeadmin to create a CSR and approve it. </del> <ins> Use kubectl to create a CSR and approve it. </ins> Get the list of CSRs ```

Discussion:
/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly 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:
#### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range} <del> {{< feature-state for_k8s_version="v1.25" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> Kubernetes divides the `ClusterIP` range into two bands, based on the size of the configured `service-cluster-ip-range` by using the following formula

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:
### Language specific Zoom meetings If the localization project needs a separate meeting time, contact a SIG Docs Co-Chair or Tech <del> Lead to create a new reoccurring Zoom meeting and calendar invite. This is only needed when the </del> <ins> Lead to create a new reoccurring Zoom meeting and calendar invite. This is only needed when </ins> the team is large enough to sustain and require a separate meeting. Per CNCF policy, the localization teams must upload their meetings to the SIG Docs YouTube

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. --This extra "the" should be removed for better readability. ! Why is this needed For the improvement of the docs this extra "the" should be removed. file link :-
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
: Please check the comments against PR . Thank you for suggesting this amendment, however, we'd request that when you suggest such trivial edits you check the entire document for any other mistakes that might need rectification.
Change:
<div class="row"> <div class="col-md-8"> <del> <h3>Objectives</h3> </del> <ins> <h3>उद्देश्य</h3> </ins> <ul> <li>जानें कुबेरनेट्स क्लस्टर क्या है।</li> <li>जानें मिनिक्यूब क्या है।</li>

Discussion:
This is a Bug Report Objective should be replace by उद्देश्य in content/hi/docs/tutorials/kubernetes-basics/create-cluster/cluster- <!--Required Information--Problem: Objective is english word in hindi content Proposed Solution: Replace with उद्देश्य 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
/kind documentation
/assign
Change:
<div class="col-md-8"> <h3>Kubernetesクラスター</h3> <p> <del> <b>Kubernetesは、単一のユニットとして機能するように接続された、可用性の高いコンピュータのクラスターをまとめあげます。</b>Kubernetesの抽象化により、コンテナ化されたアプリケーションを個々のマシンに特に結び付けることなくクラスターにデプロイできます。この新しいデプロイモデルを利用するには、アプリケーションを個々のホストから切り離す方法でアプリケーションをパッケージ化(つまり、コンテナ化)する必要があります。コンテナ化されたアプリケーションは、アプリケーションがホストに深く統合されたパッケージとして特定のマシンに直接インストールされていた従来のデプロイモデルよりも柔軟で、より迅速に利用可能です。<b>Kubernetesはより効率的な方法で、クラスター全体のアプリケーションコンテナの配布とスケジューリングを自動化します。</b>Kubernetesはオープンソースのプラットフォームであり、プロダクションレディです。 </del> <ins> <b>Kubernetesは、単一のユニットとして機能するように接続された、可用性の高いコンピューターのクラスターをまとめあげます。</b>Kubernetesの抽象化により、コンテナ化されたアプリケーションを個々のマシンに特に結び付けることなくクラスターにデプロイできます。この新しいデプロイモデルを利用するには、アプリケーションを個々のホストから切り離す方法でアプリケーションをパッケージ化(つまり、コンテナ化)する必要があります。コンテナ化されたアプリケーションは、アプリケーションがホストに深く統合されたパッケージとして特定のマシンに直接インストールされていた従来のデプロイモデルよりも柔軟で、より迅速に利用可能です。<b>Kubernetesはより効率的な方法で、クラスター全体のアプリケーションコンテナの配布とスケジューリングを自動化します。</b>Kubernetesはオープンソースのプラットフォームであり、プロダクションレディです。 </ins> </p> <p>Kubernetesクラスターは以下の2種類のリソースで構成されています: <ul>

Discussion:
This is a Feature Request What would you like to be fix the notation variations of the term "computer" valid: invalid: | Why is this needed In Japanese documents, There are notation variations. The Japanese localization of k/website has rules, so we want to follow them. Comments FYI: Japanese Localization document: command /language ja /area localization /help /good-first-issue
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
PTAL before woking
PR
/remove-help
Change:
``` {{< tabs name="tab-cri-cri-o-installation" >}} <del> {{< tab name="Debian" >}} </del> <ins> {{% tab name="Debian" %}} </ins> ```shell # Debian 개발 배포본(Unstable/Sid)

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