jiebi/CodeConvo huggingface dataset:
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: I tried to run the cloned website, which I forked on my Ubuntu Machine, but am getting error. I tried both running via docker and my running locally using Hugo but getting some issues in both. Following is the error while running via docker ! and this is while running locally via Hugo ! I also initialized modules by running the command: make module-init
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 support
I tried to analyze a bit. On first investigation, it seems like a valid issue. However, I do not know the root cause. I created a new Ubuntu VM, and tried to setup k/w from scratch. On running , the hugo command was stuck at: I then executed and managed to reproduce the issue you reported. (Note that at times this command gets stuck without an output as well). On my local machine, I have older versions of npm, hugo, go and docker and k/w builds fine. It could be related to one of the upgrades in the dependencies (most probably Hugo), however I cannot state for certain.
The issue is in the Hugo version. Upon changing the version, it worked perfectly. Thanks for your input. I think this issue should be raised.
Can you please mention the exact combination of versions (npm, Hugo, go, docker) that worked for you?
here, it is but I think the issue is with Hugo's version only.
Try whilst you have the latest main branch checked out. That works for me. You should find that you're using Hugo 0.121.2 (see ). If you want to test a Hugo upgrade, run before .
The instruction to install a specific Hugo extended version as defined in is mentioned in the section. However, I believe it would be helpful to move the instruction to the section. This would prevent readers from inadvertently installing the latest Hugo extended version (currently v0.124.1) which is incompatible with k/w. I'll try to work on a PR for this.
/assign

Discussion:
- [Hugo (Extended version)](https://gohugo.io/) - A container runtime, like [Docker](https://www.docker.com/). <ins> > [!NOTE] Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </ins> Before you start, install the dependencies. Clone the repository and navigate to the directory: ```bash

## Running the website locally using Hugo <del> Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L11) file. </del> To install dependencies, deploy and test the site locally, run: - For macOS and Linux
Change:
Hello there! In the , the statement is made that: While this is correct, it's misleading in context because go-yaml has an regarding compatibility with the spec. While I understand this is particularly nitpicky, I think it's worth documenting this case because: issue was raised more than two years ago. are open that have been pending to resolve this for years. are major languages and libraries where the default options generate valid JSON/YAML that run into this case (e.g., PHP). The escape sequence is explicitly listed in , near the top of page 9, as being an allowed escape sequence. I'd argue that this section should either: Explicitly call out the incompatibility; or Soften the language to some thing like "Most JSON documents are accepted as YAML by Kubernetes." At least in softening the language, people may be encouraged to explore the possibility that it's not their code that's broken, but instead an issue with the YAML that kubernetes accepts and attempt to find workarounds instead of spending an embarrassing amount of time looking in the wrong place like I just did. Thank you for your time! Adam
Page reported in issue: /language en
/retitle Improve "Server-Side Apply" page to address JSON/YAML compatibility with go-yaml
/kind feature We can document the bug in Kubernetes. I'd prefer to make it clear that it's a bug, rather than document the bug as our expected behavior.
/wg api-expression /priority backlog /triage accepted
/assign

Discussion:
Whether you are submitting JSON data or YAML data, use `application/apply-patch+yaml` as the `Content-Type` header value. <del> All JSON documents are valid YAML. </del> <ins> All JSON documents are valid YAML. However, Kubernetes has a bug where it uses a YAML parser that does not fully implement the YAML specification. Some JSON escapes may not be recognized. </ins> {{< /note >}} The serialization is the same as for Kubernetes objects, with the exception that
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: The feature state is not consistent between English version (v1.27 beta) and Chinese version (v1.26 beta). Proposed Solution: Make the translation(s) be consistent. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hey If you want to work on this issue then you may assign it. /sig docs /language zh
/triage accepted /assign
/retitle [zh] Stale feature state for Chinese version of “Specifying a Disruption Budget for your Application”

Discussion:
--> ## 不健康的 Pod 驱逐策略   {#unhealthy-pod-eviction-policy} <del> {{< feature-state for_k8s_version="v1.26" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.27" state="beta" >}} </ins> {{< note >}} <!--
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: The Link for under in docs redirects to which is incorrect. The correct link is Proposed Solution: should redirect to instead of Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I would like to work on it. /assign
/language en /sig network /sig docs
/triage accepted /priority backlog

Discussion:
You can expose a Service in multiple ways that don't directly involve the Ingress resource: * Use [Service.Type=LoadBalancer](/docs/concepts/services-networking/service/#loadbalancer) <del> * Use [Service.Type=NodePort](/docs/concepts/services-networking/service/#nodeport) </del> <ins> * Use [Service.Type=NodePort](/docs/concepts/services-networking/service/#type-nodeport) </ins> ## {{% heading "whatsnext" %}}
Change:
The is a command code but not marked as inline code. I think marking it will help learners
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
Raised PR with fix /assign

Discussion:
For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like [Minikube](https://minikube.sigs.k8s.io/docs/start/) to be installed first and then re-run the commands stated above. <del> If kubectl cluster-info returns the url response but you can't access your cluster, </del> <ins> If `kubectl cluster-info` returns the url response but you can't access your cluster, </ins> to check whether it is configured properly, use: ```shell
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: While following the Kubernetes tutorial on exposing an external IP address at , using the command results in an error. The error message indicates a failure to pull the Docker image due to deprecated image format: This issue prevents the tutorial from being completed as described. Proposed Solution: Update the tutorial page to use a newer version of the Docker image that complies with the current Docker Image specifications (OCI Format or Docker Image manifest v2, schema 2). Alternatively, provide a note or warning about this issue with guidance on how to proceed or troubleshoot this specific deprecation issue. 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
The image going to be deprecated. so the example has to be updated !
So, what can be the alternate image to use?
This issue might be fixed similar to , I'm happy to draft a PR if no one was working on it already.

Discussion:
The response to a successful request is a hello message: ```shell <del> Hello Kubernetes! </del> <ins> Hello, world! Version: 2.0.0 Hostname: hello-world-2895499144-2e5uh </ins> ``` ## {{% heading "cleanup" %}}

app.kubernetes.io/name: load-balancer-example spec: containers: <del> - image: gcr.io/google-samples/node-hello:1.0 </del> <ins> - image: us-docker.pkg.dev/google-samples/containers/gke/hello-app:2.0 </ins> name: hello-world ports: - containerPort: 8080
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: The under in docs redirects to this link: which shows the message that 'This document has been moved to' this link: Proposed Solution: Update link of from to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I would like to work on this. /assign /language en /sig network /sig docs
I'd link to which seems to be the relevant documentation.
Hi this link looks more relevant to me. Thank you for sharing this. I will update this link in the documentation.

Discussion:
* [Emissary-Ingress](https://www.getambassador.io/products/api-gateway) API Gateway is an [Envoy](https://www.envoyproxy.io)-based ingress controller. * [EnRoute](https://getenroute.io/) is an [Envoy](https://www.envoyproxy.io) based API gateway that can run as an ingress controller. <del> * [Easegress IngressController](https://github.com/megaease/easegress/blob/main/doc/reference/ingresscontroller.md) is an [Easegress](https://megaease.com/easegress/) based API gateway that can run as an ingress controller. </del> <ins> * [Easegress IngressController](https://megaease.com/docs/easegress/04.cloud-native/4.1.kubernetes-ingress-controller/) is an [Easegress](https://megaease.com/easegress/) based API gateway that can run as an ingress controller. </ins> * F5 BIG-IP [Container Ingress Services for Kubernetes](https://clouddocs.f5.com/containers/latest/userguide/kubernetes/) lets you use an Ingress to configure F5 BIG-IP virtual servers. * [FortiADC Ingress Controller](https://docs.fortinet.com/document/fortiadc/7.0.0/fortiadc-ingress-controller/742835/fortiadc-ingress-controller-overview) support the Kubernetes Ingress resources and allows you to manage FortiADC objects from Kubernetes
Change:
This seems to be a typo, shouldn't it be traffic-distribution and not trafic-distribution ?
/triage accepted /good-first-issue Yep, looks like that was a typo in the recent updates.
This request has been marked as suitable for new contributors. 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 : /triage accepted /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
/language en
/retitle Typo in "Service" concept page /kind bug

Discussion:
See [Traffic Policies](/docs/reference/networking/virtual-ips/#traffic-policies) for more details. <del> ### Trafic distribution </del> <ins> ### Traffic distribution </ins> {{< feature-state feature_gate_name="ServiceTrafficDistribution" >}}
Change:
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 button for "" in Why is this needed Because it exists in en() but not in ja( ). Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/retitle [ja] Add button in /area localization /triage accepted

Discussion:
- name: about title: ドキュメントについて description: このWebサイトには、Kubernetesの最新バージョンと過去4世代のドキュメントが含まれています。 <ins> button: "利用可能なバージョンを見る" button_path: "/docs/home/supported-doc-versions" </ins> ---
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: Compared with [en] The [zh] miss in section Proposed Solution: add in section 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

Discussion:
* runc：v1.1 或更新版本 * crun: v1.8.6 或更新版本 <ins> * Linux 内核: v5.12 或更新版本 </ins> <!-- ## What's next?
Change:
This is a Bug Report There is a wrong reference to the Container runtime interface in page. It take to container runtime instead of CRI. Should be updated with correct reference to CRI page.
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

Discussion:
The [kubelet](/docs/reference/command-line-tools-reference/kubelet/) collects pod and container metrics via [cAdvisor](https://github.com/google/cadvisor). As an alpha feature, Kubernetes lets you configure the collection of pod and container <del> metrics via the {{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI). You </del> <ins> metrics via the {{< glossary_tooltip term_id="container-runtime-interface" text="Container Runtime Interface">}} (CRI). You </ins> must enable the `PodAndContainerStatsFromCRI` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and use a compatible CRI implementation (containerd >= 1.6.0, CRI-O >= 1.23.0) to use the CRI based collection mechanism.
Change:
This is a Bug Report Problem: Using as an example, Note blocks that start with a bullet appear malformed, same outcome in both Chrome and Safari, note the dot over the e characters and incorrect indentation - <img width="723" alt="image" src=""Proposed Solution: Let's discuss further, possibly, maybe this can be fixed via hugo, otherwise we could investigate an update to all affected pages. Page to Update: We should update all notes that meet this criteria, investigate after a proposed solution is agreed.
/area web-development
It seems that our recent update to align with Docsy-style callouts in may have unintentionally caused this issue. There's definitely room for improvement here, and we should address this to ensure the content is displayed properly. /priority backlog /triage accepted
Oops. I think we can address this with a CSS fix; for example, not making the “note” text an inline block when the parent contains either or (using and selectors). For a simple fix, make the “Note:” text never be an inline block.
i would like to try
/assign

Discussion:
h4, h4.alert-heading { color: #000; display: block; <del> float: left; </del> <ins> float: initial; </ins> font-size: 1rem; padding: 0; padding-right: 0.5rem;
Change:
This is a Bug Report Problem: The main page currently offers to visit KubeCon Europe 2024 (which has passed already) and KubeCon NA 2024 (which is valid). AFAIR, this page has always listed two upcoming KubeCon events in Europe + NA. However: doesn't seem to be an official date for the next KubeCon Europe yet. seems reasonable to promote other locations as well. According to the , the next KubeCon will happen in Hong Kong (21-23 August, 2024). There also will be a KubeCon India in December. Proposed Solution: I suggest removing the past KubeCon Europe and adding KubeCon Hong Kong and KubeCon India to the page. I'm ready to make a relevant PR if/then this suggestion is approved. P.S. In the future, I think it would be great to elaborate a better solution with all needed future events listed in some kind of YAML and displayed automatically on the website depending on the current date. Page to Update:
/language en /sig docs
/triage accepted /retitle Stale KubeCon 2024 events at main page (it's not a bug to list upcoming events; the bug is that the list is stale)
hey Are you going to follow up with this? Or could I?
Hi I just created to resolve it. However, when this PR is finalised and approved, your help in promoting these changes to other localisations will be much appreciated!

Discussion:
<button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button> <br> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon Europe on March 19-22, 2024</a> </del> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon China on August 21-23</a> </ins> <br> <br> <br> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america-2024/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon North America on November 12-15</a> </ins> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america-2024/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon North America on November 12-15, 2024</a> </del> <ins> <br> <br> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-india/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon India on December 11-12</a> </ins> </div> <div id="videoPlayer"> <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
Change:
I find this small bit in the scale-intro a bit confusing: and then directly under that paragraph, there is this highlighted "Note" section, that states: TL;DR; Paragraph instructs me to delete the "NodePort" service, because this sections expects a "Loadbalancer" service to be active. Highlighted Note instructs me to re-create the "NodePort" service after the "Loadbalancer" service was created.
Page reported in issue (based on the issue title): /language en
/retitle Conflicting guidance regarding Service creation in "Scale Your App" tutorial /kind bug
Removing this ambiguity will improve the tutorial's usability. /priority backlog /triage accepted
I will try to help with this. /assign

Discussion:
<p>If you haven't worked through the earlier sections, start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">Using minikube to create a cluster</a>.</p> <p><em>Scaling</em> is accomplished by changing the number of replicas in a Deployment</p> <del> <p><b>NOTE</b> If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, then you may have deleted the service you created, or have created a Service of <tt>type: NodePort</tt>. In this section, it is assumed that a service with <tt>type: LoadBalancer</tt> is created for the kubernetes-bootcamp Deployment.</p> <p>If you have <em>not</em> deleted the Service created in <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro">the previous section</a>, first delete that Service and then run the following command to create a new Service with its <tt>type</tt> set to <tt>LoadBalancer</tt>:</p> <p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="LoadBalancer" --port 8080</b></code></p> </del> </br> </div> <div class="col-md-4">

<div class="row"> <div class="col-md-12"> {{< note >}} <del> <p>If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section</a>, you may have deleted the Service exposing the Deployment. In that case, please expose the Deployment again using the following command:</p><p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080</b></code></p> </del> <ins> <p>If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, then you may have deleted the service you created, or have created a Service of <tt>type: NodePort</tt>. In this section, it is assumed that a service with <tt>type: LoadBalancer</tt> is created for the kubernetes-bootcamp Deployment.</p> <p>If you have <em>not</em> deleted the Service created in <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro">the previous section</a>, first delete that Service and then run the following command to create a new Service with its <tt>type</tt> set to <tt>LoadBalancer</tt>:</p> <p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="LoadBalancer" --port 8080</b></code></p> </ins> {{< /note >}} </div> </div>