jiebi/CodeConvo huggingface dataset:
Change:
: A service defines a set of pods and a means by which to access them, such as single stable IP address and corresponding DNS name. [**Volume**](/docs/user-guide/volumes/) <del> : A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/), adding provisioning of the volume directory and/or device. </del> <ins> : A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/engine/tutorials/dockervolumes/), adding provisioning of the volume directory and/or device. </ins> [**Secret**](/docs/user-guide/secrets/) : A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request.

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x ] Bug Report Problem: The link to Docker Volumes is broken: it does not exist anymore. Proposed Solution: Fix the link to point to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
looks like there's a redirect to the correct page on Docker so this link isn't broken anymore. It's probably still worth updating to point users to the right page to begin with
Updated w/ PR
Change:
--- title: Tutorial interativo - Criando um cluster weight: 20 <ins> headless: true toc_hide: true _build: list: never publishResources: false </ins> --- <!DOCTYPE html> <del> <html lang="en"> </del> <ins> <html lang="pt-BR"> </ins> <body>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
![Using a node level logging agent](/images/docs/user-guide/logging/logging-with-node-agent.png) <del> You can implement cluster-level logging by including a _node-level logging agent_ on each node. The logging agent is a dedicated tool that exposes logs or pushes logs to a backend. Commonly, the logging agent is a container that has access to a directory with log files from all of the application containers on that node. </del> <ins> You can implement cluster-level logging by including a _node-level logging agent_ on each node. The logging agent is a dedicated tool that exposes logs or pushes logs to a backend. Commonly, the logging agent is a container that has access to a directory with log files from all of the application containers on that node. </ins> Because the logging agent must run on every node, it is recommended to run the agent as a `DaemonSet`. Node-level logging creates only one agent per node and doesn't require any changes to the applications running on the node. <del> Containers write to stdout and stderr, but with no agreed format. A node-level agent collects these logs and forwards them for aggregation. </del> <ins> Containers write to stdout and stderr, but with no agreed format. A node-level agent collects these logs and forwards them for aggregation. </ins> ### Using a sidecar container with the logging agent {#sidecar-container-with-logging-agent}

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs 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
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
* the kubelet's [checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) * a list of [Articles on dockershim Removal and on Using CRI-compatible Runtimes](/docs/reference/node/topics-on-dockershim-and-cri-compatible-runtimes/) <ins> * [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions) * [Node Labels Populated By The Kubelet](/docs/reference/node/node-labels) </ins> * [Node `.status` information](/docs/reference/node/node-status/) You can also read node reference details from elsewhere in the

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: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Proposed Solution: Add more links into (look at the left nav to see which ones they are) Page to Update: /language en /priority backlog /good-first-issue /triage accepted :information_source: have you already worked on an issue? Please save this for a contributor who has not.
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Add more links into (look at the left nav to see which ones they are) /good-first-issue /triage accepted 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
I want to work on this. /assign
Pr to fix this issue
Change:
## {{% heading "whatsnext" %}} <del> より詳しい情報は、[LimitRangerの設計ドキュメント](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md)を参照してください。 </del> <ins> より詳しい情報は、[LimitRangerの設計ドキュメント](https://git.k8s.io/design-proposals-archive/resource-management/admission_control_limit_range.md)を参照してください。 </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: Link to LimitRanger design document in is broken. F) T) Proposed Solution: fix link in doc 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 ja /assign
Change:
```none deployment.apps/web2 created ``` <ins> Verify that the Deployment is in a Ready state: ```shell kubectl get deployment web2 ``` The output should be similar to: ```none NAME   READY   UP-TO-DATE   AVAILABLE   AGE web2   1/1     1            1           16s ``` </ins> 1. Expose the second Deployment:

Discussion:
Problem: Going through the documentation provided by the link such issue has being met on the step of verification that Ingress controller is directing the traffic using the command below: curl --resolve "hello-$( minikube ip )" -i http://hello- After running this command the terminal returns: Failed to connect to hello- port 80 after ms: Couldn't connect to server Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Kubernetes version: v1.28.3 <!--Additional Information:--Environment that is used: Macbook M1 Pro Minikube version: v1.32.0 Minikube uses the docker driver. Step on which problem has been met:
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
Page reported in issue: /language en
This is same as issue /triage duplicate I believe this should be fixed by updating the page by mentioning the instructions to create a for MacOS and Windows users. I'll try to work on a PR for this. Till the time the page is modified, the way around this is mentioned . The reason why it fails on MacOS and Windows is documented here , , You can also visit the page and view the tab in Step 4 Deploy applications.
/assign

you need start and then to solve same problem in mac
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
/triage needs-information Hi. Is this about a particular web page?
sorry, this is about following tutorial Create an Ingress step 4
/retitle Ingress tutorial does not mention commands needed for Mac /remove-triage needs-information
/kind bug /language en
I can confirm that this is a valid issue on MacOS and the page needs to be updated. I think we should move this to /triage accepted. I cannot test this on Windows at the moment, but suggests that the behaviour on Windows will be the same as MacOS. The network is limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly.
/assign
Change:
- fundamental --- The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers. <ins> <!--more--> This layer is composed by many different components, such as (but not restricted to): * {{< glossary_tooltip text="etcd" term_id="etcd" >}} * {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}} * {{< glossary_tooltip text="Scheduler" term_id="kube-scheduler" >}} * {{< glossary_tooltip text="Controller Manager" term_id="kube-controller-manager" >}} * {{< glossary_tooltip text="Cloud Controller Manager" term_id="cloud-controller-manager" >}} These components can be run as traditional operating system services (daemons) or as containers. The hosts running these components were historically called {{< glossary_tooltip text="masters" term_id="master" >}}. </ins>  No newline at end of file

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:--
The glossary does not contain a definition for Kubernetes object, or Kubernetes master.
Good point /priority backlog /language en We could possibly add a “master” for a synonym for “control plane”, and then in the entry for “control plane” explain the similarities and differences between the two terms.
/help
I'll work on that! /remove-help /assign
and What about creating a entry explaining the concept and listing and as most common values used on it?
Hmm. That term “master” has nuances (it's not as controversial as “slave”, but the implication is still there). Newer thinking seems to favor “control plane” rather than “master”. So you can have nodes that also run the control plane. Does that help guide how to approach this?
I understand your point, but may tools still uses and for the label (ex. ). Also, looks like we already have covered in the glossary (). What about to refactor entry, explaining that nodes can also have a role label, and these are the most common values (and linking to )?
the "master" node role is exclusive to deployers like kubeadm (+some others) and has been excluded from core k8s.
Change:
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" %}}

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: 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
Change:
to the REST api. For further documentation refer to the authorization.v1beta1 API objects and <del> [webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go). </del> <ins> [webhook.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go). </ins>

Discussion:
This is a Bug Report <!--Required Information--Problem: In docs, link give 404 error. Proposed Solution: should be linked to 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
/assign I can work on this.
Fixed it here:
ref
Hi I think we don't change in file as it is used as configuration when building the website. It was changed in this , as for website repo master branch renamed to main in k8s v1.22.
Change:
#### Persisting kubelet reconfiguration <del> Any changes to the `KubeletConfiguration` stored in `/var/lib/kubelet/config.conf` will be overwritten on </del> <ins> Any changes to the `KubeletConfiguration` stored in `/var/lib/kubelet/config.yaml` will be overwritten on </ins> `kubeadm upgrade` by downloading the contents of the cluster wide `kubelet-config` ConfigMap. <del> To persist kubelet node specific configuration either the file `/var/lib/kubelet/config.conf` </del> <ins> To persist kubelet node specific configuration either the file `/var/lib/kubelet/config.yaml` </ins> has to be updated manually post-upgrade or the file `/var/lib/kubelet/kubeadm-flags.env` can include flags. The kubelet flags override the associated `KubeletConfiguration` options, but note that some of the flags are deprecated. <del> A kubelet restart will be required after changing `/var/lib/kubelet/config.conf` or </del> <ins> A kubelet restart will be required after changing `/var/lib/kubelet/config.yaml` or </ins> `/var/lib/kubelet/kubeadm-flags.env`. ## {{% heading "whatsnext" %}}

Discussion:
Run kubeadm upgrade node phase kubelet-config to download the latest kubelet-config ConfigMap contents into the local file The local file name should be
Page related to issue: /language en
/retitle Incorrect file mentioned in command
/sig cluster-lifecycle
plz I want help to fix this /assign
FYI, the same incorrect filename exists in other places on the same page. Two are in the second blue-barred Note pane below the command, and three are further down in the section
(or other maintainers) Can I get confirmation and go ahead please; if this be a tirage-accepted issue to that i can proceed with the fix.
/triage accepted /kind bug Thanks for spotting this.
I have attempt to make fix for this in
Change:
[Cluster API](https://github.com/kubernetes-sigs/cluster-api) for infrastructure provisioning and management. Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the <del> [control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane). </del> <ins> [control plane](/docs/concepts/overview/components/#control-plane-components). </ins> ![Cluster Lifecycle Layers](/images/blog/2019-06-24-kubeadm-ha-v115/overview.png)

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--Hyperlinks don't work Hyperlinks to topics <bKubernetes control plane</band <bKubernetes objects</btakes to back to <bConcepts</bpage rather than respective topics. Proposed Solution: Update linkw to point to correct content. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi If related documents are not missing, then Perhaps Kubernetes control plane should point to I noticed that the corresponding file , later than the link on page . And Kubernetes objects perhaps should point to . Seems a little bit weird. These documents should be in the same hierarchy I think. Let me create a PR to solve this issue. /assign
/kind bug
I think the link for Kubernetes control-plane should be to and I agree above that the link for Kubernetes objects should be to /assign
Hi Thanks for your PR! I submitted a PR (ref: ) to fix this issue about half a month ago, and just got approved 3 days ago. Since the CLA checking was missing after I migrated to a new github account, this PR was not merged until a few minutes ago after I let the robot recheck my CLA.
Change:
<!-- body --> <del> If you use Docker via dockershim as your container runtime, the Kubernetes project recommends that you migrate to an alternative container runtime. </del> <ins> Dockershim will be removed from Kubernetes following the release of v1.24. If you use Docker via dockershim as your container runtime, and wish to upgrade to v1.24, it is recommended that you either migrate to another runtime or find an alternative means to obtain Docker Engine support. </ins> If you're not sure whether you are using Docker, [find out what container runtime is used on a node](/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/).

Discussion:
While evaluating , it was suggested that we should make a stronger statement about migrating from dockershim on the page. The current wording is: Perhaps it could be more along the lines of:
/language en /triage accepted
Hi, I would like to work on this issue. Thanks. /assign
I have one question: The PR for this issue should target the branch or the branch?
Good question. I think clarity is a good thing right now. So my personal preference is .
Change:
Boot | 부트 | Build | 빌드 | Cache | 캐시 | <ins> Calico | 캘리코(Calico) | </ins> canary | 카나리(canary) | 릴리스 방식에 관련한 용어인 경우에 한함 cascading | 캐스케이딩(cascading) | character set | 캐릭터 셋 | Charts | 차트 | checkpoint | 체크포인트 | <ins> Cilium | 실리움(Cilium) | </ins> CLI | CLI | Cluster | 클러스터 | Command Line Tool | 커맨드라인 툴 |

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. --There are several CNI plugins that need to be translated into Korean to be to . English --- --- Calico Cilium Flannel Kube-router Romana Weave-net Weaveworks 'Weave Net' . Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
Change:
} } } <del> } </del> <ins> } </ins>  No newline at end of file

Discussion:
Expected behavior: https://v1- (drop-downs work) Actual behavior: (drop-downs do not work) This may be a issue or a result of non-translated pages not showing up in autogenerated navs. I'm unsure.
/assign /priority important-soon /kind bug
Hello, calestehorgan I investigated this problem quickly and found that (this is the version and language box) seemed to remain when the mouse cursor has hovered. ! Adding the following style makes the problem disappeared: ! Maybe some style is missing or something blocks a style applied.
Thank you for the help!! I'll try it out.
I'm glad to help!