jiebi/CodeConvo huggingface dataset:
Change:
Would be good to include the new fields in the output such as ,, and . These are related to dual stack deployments but since the same IPv4 address appear twice in a single stack output I think it is worth updating the sample outputs.
/retitle Stale output in Connecting Applications with Services URL of tutorial is ( it's definitely helpful if you include that detail) /language en /kind bug
/triage accepted
/sig network
/assign
I will update output with latest one

Discussion:
Annotations:         <none> Selector:            run=my-nginx Type:                ClusterIP <ins> IP Family Policy:    SingleStack IP Families:         IPv4 </ins> IP:                  10.0.162.149 <ins> IPs:                 10.0.162.149 </ins> Port:                <unset> 80/TCP <ins> TargetPort:          80/TCP </ins> Endpoints:           10.244.2.5:80,10.244.3.4:80 Session Affinity:    None Events:              <none>
Change:
This is a Bug Report Problem: Under concept page, content for volume type is missing. In it is mentioned like: ! Due to this, content() is missing from the page: ! Instead of that it should be like the below screenshot: ! Proposed Solution: Above missing content Content for should be there. Page to Update:
/assign
/sig docs
Fixed it here:
/triage accepted /retitle Formatting problem for volume details in Volumes concept /language en

Discussion:
<!-- maintenance note: OK to remove all mention of glusterfs once the v1.25 release of Kubernetes has gone out of support --> <del> - </del> Kubernetes {{< skew currentVersion >}} does not include a `glusterfs` volume type. The GlusterFS in-tree storage driver was deprecated in the Kubernetes v1.25 release
Change:
This is a Bug Report Problem: Glossary term id and title must be same as per the current design. But for Glossary , term id is documented wrongly as whereas title and file name is . Proposed Solution: Update term id from workloads to . Page to Update: <!--Additional Information:--
/language en /sig docs /assign
I don't think this is true. We prefer it if the term ID and the display text are similar though.
Hi ok, might be my understanding is wrong on it. But i was verifying the existing Glossary items, most of them are documented term id and title are same. Also if we use term id as in PR, build is getting fail and giving error as invalid term id "workloads". Test cases are accepting only if we mention term id as . is the related error, Thanks.
Looks like a bug, isn't it?
Hi Yes, but I'm not sure if the bug is in the documentation or in the test cases. First, we must determine the correct term id among these two (workload/workloads), and then only we can proceed.
I've gone through the other files in the and noticed a pattern that the id most often matches with the title itself. Hence for this, I believe workload should work fine. However, I'm not sure why a change in the id is leading to CI failure?
The glossary shortcode does care about the field? I don't think so. That is the reason why referencing the field rather than the file name sometimes failed.
Any updates onto it?
I looked up what is for: it's the fragment identifier on the glossary page.
The following is from the shortcode. is the variable used in the shortcode, then it is used to generate the file name of the glossary. The code never extract the in the glossary entry, right?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues 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 as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
If we look at this, here it is trying to match which doesn't exist. That's why the error is comming if i am not wrong. What do you suggest to be done?
/remove-lifecycle stale
SIG Docs: Can you please have a look into this as its waiting since many days.
Is there are fix proposal for this? /triage accepted
/assign
IMO we can change id to that will exactly match with existing filename which can fix the issue. I will propose a PR if OK.
PR raised

Discussion:
--- title: Workload <del> id: workloads </del> <ins> id: workload </ins> date: 2019-02-13 full_link: /docs/concepts/workloads/ short_description: >
Change:
Problem: The text on is not working, it should point to this Check the page for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text king link to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to this Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text king link to and not to this . /assign /language en 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
Hello , the doesnt direct to any page, I have checked the official king page, I believe adding would be appropriate. Please suggest if any changes, Thanks.
/triage accepted Mind propose a fix?

Discussion:
## kind <del> [`kind`](https://kind.sigs.k8s.io/docs/) lets you run Kubernetes on </del> <ins> [`kind`](https://kind.sigs.k8s.io/) lets you run Kubernetes on </ins> your local computer. This tool requires that you have [Docker](https://docs.docker.com/get-docker/) installed and configured.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Kubernetes an annotation, . For example, this annotation is set on ConfigMaps that are being used for legacy leader election (the modern / GA way to do this is using a Lease). That annotation is unregistered because it doesn't appear inside Proposed Solution: Register the annotation, by documenting it in Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig architecture /language en
/assign
/triage accepted

Discussion:
If the number of backend endpoints falls below 1000, the control plane removes this annotation. <ins> ### control-plane.alpha.kubernetes.io/leader (deprecated) {#control-plane-alpha-kubernetes-io-leader} Type: Annotation Example: `control-plane.alpha.kubernetes.io/leader={"holderIdentity":"controller-0","leaseDurationSeconds":15,"acquireTime":"2023-01-19T13:12:57Z","renewTime":"2023-01-19T13:13:54Z","leaderTransitions":1}` Used on: Endpoints The {{< glossary_tooltip text="control plane" term_id="control-plane" >}} previously set annotation on an [Endpoints](/docs/concepts/services-networking/service/#endpoints) object. This annotation provided the following detail: - Who is the current leader. - The time when the current leadership was acquired. - The duration of the lease (of the leadership) in seconds. - The time the current lease (the current leadership) should be renewed. - The number of leadership transitions that happened in the past. Kubernetes now uses [Leases](/docs/concepts/architecture/leases/) to manage leader assignment for the Kubernetes control plane. </ins> ### batch.kubernetes.io/job-tracking (deprecated) {#batch-kubernetes-io-job-tracking} Type: Annotation
Change:
This is a Bug Report Problem: The Hyperlink for under of and Containers gives Error. ! Proposed Solution: It should be redirected to Instead of 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
/sig docs /language en
/assign
Fixed it here:

Discussion:
and its [resource requirements](/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources) * Read about [project quotas](https://xfs.org/index.php/XFS_FAQ#Q:_Quota:_Do_quotas_work_on_XFS.3F) in XFS * Read more about the [kube-scheduler configuration reference (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/) <del> * Read more about [Quality of Service classes for Pods](/docs/concepts/workloads/pods/pod-quality/) </del> <ins> * Read more about [Quality of Service classes for Pods](/docs/concepts/workloads/pods/pod-qos/) </ins>
Change:
Problem: The text on is not working, I believe the right link should be https://gateway- Check the page for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text enhancement proposals link to https://gateway- and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, I believe the right link should be https://gateway- Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text enhancement proposals link to https://gateway- and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
/kind documentation

Discussion:
Management and Administration. This group will deliver [enhancement <del> proposals](https://gateway-api.sigs.k8s.io/v1beta1/contributing/gep/) consisting </del> <ins> proposals](https://gateway-api.sigs.k8s.io/geps/overview/) consisting </ins> of resources, additions, and modifications to the Gateway API specification for mesh and mesh-adjacent use-cases.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --The link to installation instructions for the Calico networking add-on leads to a Page Not Found page. ! <!--Required Information--Problem: Proposed Solution: A correct link to the installation instruction be for Calico in Networking and Network Policy section of Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Duplicated by

Discussion:
* [ACI](https://www.github.com/noironetworks/aci-containers) provides integrated container networking and network security with Cisco ACI. * [Antrea](https://antrea.io/) operates at Layer 3/4 to provide networking and security services for Kubernetes, leveraging Open vSwitch as the networking data plane. Antrea is a [CNCF project at the Sandbox level](https://www.cncf.io/projects/antrea/). <del> * [Calico](https://docs.projectcalico.org/latest/introduction/) is a networking and network policy provider. Calico supports a flexible set of networking options so you can choose the most efficient option for your situation, including non-overlay and overlay networks, with or without BGP. Calico uses the same engine to enforce network policy for hosts, pods, and (if using Istio & Envoy) applications at the service mesh layer. </del> <ins> * [Calico](https://www.tigera.io/project-calico/) is a networking and network policy provider. Calico supports a flexible set of networking options so you can choose the most efficient option for your situation, including non-overlay and overlay networks, with or without BGP. Calico uses the same engine to enforce network policy for hosts, pods, and (if using Istio & Envoy) applications at the service mesh layer. </ins> * [Canal](https://projectcalico.docs.tigera.io/getting-started/kubernetes/flannel/flannel) unites Flannel and Calico, providing networking and network policy. * [Cilium](https://github.com/cilium/cilium) is a networking, observability, and security solution with an eBPF-based data plane. Cilium provides a simple flat Layer 3 network with the ability to span multiple clusters in either a native routing or overlay/encapsulation mode, and can enforce network policies on L3-L7 using an identity-based security model that is decoupled from network addressing. Cilium can act as a replacement for kube-proxy; it also offers additional, opt-in observability and security features. Cilium is a [CNCF project at the Incubation level](https://www.cncf.io/projects/cilium/). * [CNI-Genie](https://github.com/cni-genie/CNI-Genie) enables Kubernetes to seamlessly connect to a choice of CNI plugins, such as Calico, Canal, Flannel, or Weave. CNI-Genie is a [CNCF project at the Sandbox level](https://www.cncf.io/projects/cni-genie/).
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: under the 'Use Calico for NetworkPolicy' is leading to an invalid URL resulting in page not found error. Proposed Solution: Updating of Quickstart link in the Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Hi , great find! Apart from fixing link you can also look for further improvement in overall doc so that one PR can cover more improvements. For eg. fixing Grammatical errors, adding more information in the sections etc.
This seems to be duplicate of /triage duplicate
looks to be reporting broken link on whereas this issue is reporting issue with link on different page
/remove-triage duplicate
Right. my bad. Please consider these points as well:

Discussion:
## Creating a local Calico cluster with kubeadm To get a local single-host Calico cluster in fifteen minutes using kubeadm, refer to the <del> [Calico Quickstart](https://docs.projectcalico.org/latest/getting-started/kubernetes/). </del> <ins> [Calico Quickstart](https://projectcalico.docs.tigera.io/getting-started/kubernetes/). </ins>
Change:
I guess this needs to be appended here After following instructions I am unable to authenticate to the cluster if is missing.
I think the author of that reference page expected that you would use the OpenSSL tool interactively, and that's why you can read: If your configuration for OpenSSL doesn't prompt you for a common name, the advice won't work as expected. We could change this page to use a different tool - not - that is perhaps easier to explain consistently. /sig auth /language en
Just by appending would make this reference a working copy/paste step-by-step guide.
Should we do this as the first step so the docs are correct? Then we could explore the option of a different tool as per WDYT?
/triage accepted
I won't comment on that - SIG Auth or SIG Security are the best people to explain and confirm what the right fix is here, from a technical perspective. If you know it does fix this then sure, feel free to open a PR.
I will open a PR for it. /assign
Fixed it here:
or anyone from you, could you please take a look at the PR: corresponding to this issue? Thanks

Discussion:
```shell openssl genrsa -out myuser.key 2048 <del> openssl req -new -key myuser.key -out myuser.csr </del> <ins> openssl req -new -key myuser.key -out myuser.csr -subj "/CN=myuser" </ins> ``` ### Create a CertificateSigningRequest {#create-certificatessigningrequest}
Change:
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.

Discussion:
* 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
Change:
The yaml has the definition of: externalIPs: 198.51.100.32 But the docs above say: "my-service" can be accessed by clients on "80.11.12.10:80" (externalIP:port) Should it not be: "my-service" can be accessed by clients on "198.51.100.32:80" (externalIP:port)
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 , can you please explain some more ? which document page are you referring to and how can we replicate or get this error/bug?
The title is not explanatory of the issue. I'd suggest changing title to explain in brief what issue you are facing/refering to.
I think he's talking about this page:
PR only modified the data in YAML but did not modify the above description. Is a change to this description missing?
/retitle The description of Service External IPs does not match the YAML example
You are right
Thank you, I will try to use a better title next time
That could be my bug. Sorry about that.
Open PR to fix this issue.

Discussion:
of the cluster administrator. In the Service spec, `externalIPs` can be specified along with any of the `ServiceTypes`. <del> In the example below, "`my-service`" can be accessed by clients on "`80.11.12.10:80`" (`externalIP:port`) </del> <ins> In the example below, "`my-service`" can be accessed by clients on "`198.51.100.32:80`" (`externalIP:port`) </ins> ```yaml apiVersion: v1
Change:
Numbers in the following list may be not up to date. Please run again before working on each of them.
/language zh /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language zh /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
/assign

Discussion:
<!-- ## Services <ins> * [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) </ins> * [Using Source IP](/docs/tutorials/services/source-ip/) --> ## 服务  {#services} <ins> * [使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/) </ins> * [使用源 IP](/zh-cn/docs/tutorials/services/source-ip/) <!--

<!-- ## Create a minikube cluster <del> 1. Click **Launch Terminal** </del> <ins> 1. Click **Launch Terminal**. </ins> --> ## 创建 Minikube 集群  {#create-a-minikube-cluster}

Deployment 是管理 Pod 创建和扩展的推荐方法。 <!-- <del> 1. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then click open a new terminal. </del> <ins> 1. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then **Open New Terminal**. </ins> --> <del> 1. 仅 Katacoda 环境：在终端窗格的顶部，点击加号，然后点击 **Open a new terminal**。 </del> <ins> 1. 仅 Katacoda 环境：在终端窗格的顶部，点击加号，然后点击 **Open New Terminal**。 </ins> <!-- 1. Use the `kubectl create` command to create a Deployment that manages a Pod. The

``` <!-- <del> Use `CTRL-C` to terminate to kubectl. </del> <ins> Use `CTRL-C` to terminate kubectl. </ins> You cannot drain the third node because evicting `zk-2` would violate `zk-budget`. However, the node will remain cordoned.
Change:
This is a Feature Request What would you like to be In ja website, the link from kubectl tooltip should be ja. For example, when I click "kubectl" tooltip at , it jumps to Why is this needed In ja website, the link from kubectl tooltip should be ja. Comments /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

Discussion:
title: Kubectl id: kubectl date: 2018-04-12 <del> full_link: /docs/reference/kubectl/ </del> <ins> full_link: /ja/docs/reference/kubectl/ </ins> short_description: > Kubernetesクラスターと通信するためのコマンドラインツールです。