jiebi/CodeConvo huggingface dataset:
Change:
The basic tutorial starts at , which leads to , which leads to Since one does not know what is exactly meant with in the second site, one does also the deploy step. Because it's not clearly said "" or so. Then you go back to the second site, to read all through, only to do create/expose again (with little extras), only to go back to the first site and do create/expose again. Back to the first site on step 2, pretty much at the beginning it says: But I did it already 2 times in the current tutorial flow. Now I have 3 deployments, still in the basics deployment tutorial. Its like, there are 3 tutorials to do, which are the same, but also not the same. Instead of leading the user back and forth, I suggest to do one single sufficient tutorial.
Page related to issue: /language en
/retitle Consolidate and streamline Kubernetes basics tutorials to avoid redundancy and confusion
/sig docs
the three tutorial have different purpose. What I understood the purpose of having these as three.: Yes, Its leading to back and forth of the users but I think First link showing the general functionality of the cluster's component. It Should have the link To and then link will be helpful for readers to traverse. This sequence is lacking in the page. Thats the reason why i thing its taking user back and forth several times .
There was a previous attempt at de-duplicating, but it probably has to be done again - after the removal of the Katacoda tutorials, which were using a hosted setup of to run through the tutorials "inline" with the docs
I'll change the title to frame this as a bug. /retitle Multiple, similar Kubernetes basics tutorials that cause confusion /kind bug /triage accepted /priority important-longterm
/lifecycle frozen
Yes You are right! +1
/assign
I will start working on this.

Discussion:
This tutorial assumes that you have already set up `minikube`. <del> See [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions. </del> <ins> See __Step 1__ in [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions. {{< note >}} Only execute the instructions in __Step 1, Installation__. The rest is covered on this page. {{< /note >}} </ins> You also need to install `kubectl`. See [Install tools](/docs/tasks/tools/#kubectl) for installation instructions.

If you want to use minikube again to learn more about Kubernetes, you don't need to delete it. <ins> ## Conclusion This page covered the basic aspects to get a minikube cluster up and running. You are now ready to deploy applications. </ins> ## {{% heading "whatsnext" %}}

</div> </div> <del> <div class="row"> <p>Once you've done that, move on to <a href="/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/">Using <tt>kubectl</tt> to create a Deployment</a>.</p> </div> </del> </main>
Change:
This is a Bug Report Problem: The intial definiton given in doesn't describe that if the first probe time will be = . For example: The pod will be marked as after 60s, (tested in k8s v1.22.10). Moreover, the given if i read this code correctly, then the check is done for and the check for is done after assuming that value of Proposed Solution: Allign code and the documentation. Page to Update:
/sig docs /language en
/assign
I did tested this on the k8s 1.27 and it's still same.
I believe this is a corner case. Why do you set initialDelaySeconds to be shorter than perdioSeconds in the first place? I'm not objecting the clarification, BTW. What I am wondering is if there is a real case people will do this.
Okay. I get it now. The example manifest has a problem to fix. Thanks for raising up this.
/triage accepted
thanks :)

Discussion:
As you can see, configuration for a TCP check is quite similar to an HTTP check. This example uses both readiness and liveness probes. The kubelet will send the <del> first readiness probe 5 seconds after the container starts. This will attempt to </del> <ins> first readiness probe 15 seconds after the container starts. This will attempt to </ins> connect to the `goproxy` container on port 8080. If the probe succeeds, the Pod will be marked as ready. The kubelet will continue to run this check every 10 seconds.

* `initialDelaySeconds`: Number of seconds after the container has started before startup, liveness or readiness probes are initiated. If a startup  probe is defined, liveness and <del> readiness probe delays do not begin until the startup probe has succeeded. Defaults to 0 seconds. Minimum value is 0. </del> <ins> readiness probe delays do not begin until the startup probe has succeeded. If the value of `periodSeconds` is greater than `initialDelaySeconds` then the `initialDelaySeconds` would be ignored. Defaults to 0 seconds. Minimum value is 0. </ins> * `periodSeconds`: How often (in seconds) to perform the probe. Default to 10 seconds. The minimum value is 1. * `timeoutSeconds`: Number of seconds after which the probe times out.

readinessProbe: tcpSocket: port: 8080 <del> initialDelaySeconds: 5 </del> <ins> initialDelaySeconds: 15 </ins> periodSeconds: 10 livenessProbe: tcpSocket: port: 8080 initialDelaySeconds: 15 <del> periodSeconds: 20 </del> <ins> periodSeconds: 10 </ins>
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. --I want to add a hyperlink to the "GitHub repo". ! Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Link to be :
/sig docs
/language en /triage needs-information
Hi Could you please describe on which page of the documentation you are facing issue?
This is under the feedback section of too many pages. We have to change all of them.
I think we need not change much here, A slight change in i18n markdown should do the trick
/assign I'll do that
/remove-triage needs-information
Thanks for raising the PR . Also, Please focus on those issues first which have label.
/triage accepted /priority backlog

Discussion:
other = "suggest an improvement" [layouts_docs_partials_feedback_issue] <del> other = "Open an issue in the GitHub repo if you want to " </del> <ins> other = """Open an issue in the [GitHub Repository](https://www.github.com/kubernetes/website/) if you want to """ </ins> [layouts_docs_partials_feedback_or] other = "or"

<a target="_blank" rel="noopener" href="https://stackoverflow.com/questions/tagged/kubernetes"> Stack Overflow</a>. <del> {{ T "layouts_docs_partials_feedback_issue" }} </del> <ins> {{ T "layouts_docs_partials_feedback_issue" | markdownify }} </ins> <a class="feedback--link" target="_blank" rel="noopener" href="https://github.com/kubernetes/website/issues/new?title=Issue%20with%20k8s.io"> {{ T "layouts_docs_partials_feedback_problem" }}</a>
Change:
We say that the ImageGCHighThresholdPercent/ImageGCLowThresholdPercent config option is deprecated for evictionHard settings but this is not true. ImageGC uses and for Garbage collection so these flags are not We should update our documentation to reflect this.
/language en /sig docs /kind bug
/assign
/sig scheduling
/remove-sig scheduling /sig node Eviction is done in kubelet which is in sig-node's domain.
/triage accepted indeed this needs to be clarified. We unlikely will remove these flags soon. So need to fix up docs

Discussion:
Some kubelet garbage collection features are deprecated in favor of eviction: <del> | Existing Flag | New Flag | Rationale | | ------------- | -------- | --------- | | `--image-gc-high-threshold` | `--eviction-hard` or `--eviction-soft` | existing eviction signals can trigger image garbage collection | | `--image-gc-low-threshold` | `--eviction-minimum-reclaim` | eviction reclaims achieve the same behavior | | `--maximum-dead-containers` | - | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | - | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | - | deprecated once old logs are stored outside of container's context | </del> <ins> | Existing Flag | Rationale | | ------------- | --------- | | `--maximum-dead-containers` | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | deprecated once old logs are stored outside of container's context | </ins> ### Eviction thresholds
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: On the home page of website I found that the Learn Kubernetes Basics button needs to be edited as when we hover upon it the words are not clearly visible. Proposed Solution: We can make this button same as the buttons in other pages of the website like for example, under the documentation tab we have View Concepts and View Tutorial buttons. 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 upon this issue if you assign it to me. Thankyou.
/sig docs /area web-development /language en
Hi Thank you for raising this issue. You can assign this issue to yourself by commenting tag.
/assign
/retitle Learn Kubernetes Basics button difficult to read when hovered
/triage accepted /priority important-longterm Fixes are welcome.
I have a few options for the title: "Getting Started with Kubernetes Basics" "Exploring the Fundamentals of Kubernetes" "K8s Fundamentals" Please review these suggestions. Thanks
Hi The title seems interesting; we can use 'Exploring the Fundamentals of Kubernetes' as the new title.
Waiting for suggestions from other members.
'Learn Kubernetes Basics' is simple and conveys the correct message as is imo
Let's leave the text as is, and fix the poor color contrast that happens when someone hovers over the button.
Thank you
Untested, But a probable alternate fix Try modifying to wrap the with a like: css changes would not be necessary
It's been a month since this is waiting, Would any contributor like a take on this? (I think this can be a good first issue)
Just one thing; it's handy to cover even older issues that we're prioritizing too. See

Discussion:
{{ define "hero-more" }} {{ with site.GetPage "section" "docs/tutorials/kubernetes-basics" }} <del> <a href="{{ .RelPermalink }}" id="quickstartButton" class="button">{{ .LinkTitle }}</a> </del> <ins> <a href="{{ .RelPermalink }}"><button id="quickstartButton" class="button">{{ .LinkTitle }}</button></a> </ins> {{ end }} {{ end }}
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 Update Hugo to (or later), by editing Update 2024-01-01: v0.121.1 would be ideal. Why is this needed There are some security fixes for Go that we might want to pull in. Comments /sig security /sig docs
/triage accepted /priority important-longterm
/assign I'd like to help with this
I think just editing the won't work, Would need to update some images or makefile as well?
We use ~magic~ technology so that the one edit is all you need to do.
To test it locally, edit the configuration and then run:
Alright sounds good, I'll do the needful

Discussion:
[build.environment] NODE_VERSION = "10.20.0" <del> HUGO_VERSION = "0.111.3" </del> <ins> HUGO_VERSION = "0.120.3" </ins> [context.production.environment] HUGO_BASEURL = "https://kubernetes.io/"
Change:
‘’ TCP ‘’ ‘initialDelaySeconds: 5’“kubelet 15 ”“kubelet 5 ”
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
It is advisable to raise issues in English language. So, that everyone will be able to understand it. Translation of issue:- In the case of "defining TCP survival detection", the sample code of the readiness probe is configured as 'initialDelaySeconds: 5', but in the subsequent description, it is said that "kubelet will send the first readiness probe 15 seconds after the container starts. Needle", does it need to be changed to "kubelet will send the first readiness probe 5 seconds after the container starts"?
/sig docs /kind support
ok, thanks for translating for me.
/triage needs-information Even with a translation, I don't understand if this is a bug report, a support query, or a feature request. If this is a report of a problem with the Chinese page, and the page in Chinese faithfully localizes an English page where there is room for improvement, then we'd want a report against the English page.
Page related Issue: /language zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Page related Issue: /language zh-cn 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 zh
I think the issue raised is correct as readinessprobe initialdelayseconds should also be 15 as the description involve 15 sec. So I think it needs to be change. "kubelet 15 " Referring the english documented part I think it needs to be changed.
I think you should raise the issue in English. It will be more useful for contributor to approach the issue. Please try to raise it in English.
Right, the of the readinessProbe should be 15 instead of 5. Refer to the english documented part and the following description /assign
/retitle Inconsistent between en and zh in an example of tcp-liveness- Hi , please use english to describe your issue instead of a localized language (zh-cn), thanks.

Discussion:
readinessProbe: tcpSocket: port: 8080 <del> initialDelaySeconds: 5 </del> <ins> initialDelaySeconds: 15 </ins> periodSeconds: 10 livenessProbe: tcpSocket:
Change:
skipPhases Phases skipPhases Phases
/triage accepted /kind bug PRs welcomed.
/language zh
/assign

Discussion:
The list of phases can be obtained with the <code>kubeadm init --help</code> command. The flag &quot;--skip-phases&quot; takes precedence over this field.</p> --> <del> <p><code>skipPhases</code> 是命令执行过程中药略过的阶段（Phases）。 </del> <ins> <p><code>skipPhases</code> 是命令执行过程中要略过的阶段（Phases）。 </ins> 通过执行命令 <code>kubeadm init --help</code> 可以获得阶段的列表。 参数标志 &quot;--skip-phases&quot; 优先于此字段的设置。</p> </td>
Change:
This is a Bug Report default value for StatefulsetAutoDeletePVC is true in 1.27 <!-- 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 en
page to update
/assign
/triage accepted /sig apps

Discussion:
fromVersion: "1.23" toVersion: "1.26" - stage: beta <del> defaultValue: false </del> <ins> defaultValue: true </ins> fromVersion: "1.27" --- Allows the use of the optional `.spec.persistentVolumeClaimRetentionPolicy` field,
Change:
In Step 6 of , The command says to delete kubectl along with kubectl.sha256 file, but kubectl is already moved in step 4. The command needs to be rm kubectl.sha256 instead of rm kubectl kubectl.sha256
/language en
/retitle Incorrect cleanup instruction in macOS kubectl installation guide /kind bug
Indeed there appears to be discrepancy in the cleanup instruction as the removal command in Step 6 erroneously attempts to delete the already-moved kubectl binary as part of Step 4. We should address this inconsistency. /triage accepted /priority backlog
I can help with this. Worked on this files before too. /assign
i submited PR pelase review when got time. Thanks!

Discussion:
kubectl version --client --output=yaml ``` <del> 1. After installing the plugin, clean up the installation files: </del> <ins> 1. After installing and validating kubectl, delete the checksum file: </ins> ```bash <del> rm kubectl kubectl.sha256 </del> <ins> rm kubectl.sha256 </ins> ``` ### Install with Homebrew on macOS
Change:
Issue: Sentences under a subsection starts with small letters. Visit this link to see the issue: <img width="645" alt="Screenshot 2023-11-22 " src=""
/language en /sig docs
Yes i do agree that the sentence must be Capitalise and if the abbrevation of any word is address it should also be Capitalize in proper format. So that it look good to the reader.
/assign
/triage accepted

Discussion:
{{< /comment >}} [NAT](https://en.wikipedia.org/wiki/Network_address_translation) <del> : network address translation </del> <ins> : Network address translation </ins> [Source NAT](https://en.wikipedia.org/wiki/Network_address_translation#SNAT) <del> : replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node. </del> <ins> : Replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node. </ins> [Destination NAT](https://en.wikipedia.org/wiki/Network_address_translation#DNAT) <del> : replacing the destination IP on a packet; in this page, that usually means replacing with the IP address of a {{< glossary_tooltip term_id="pod" >}} </del> <ins> : Replacing the destination IP on a packet; in this page, that usually means replacing with the IP address of a {{< glossary_tooltip term_id="pod" >}} </ins> [VIP](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) <del> : a virtual IP address, such as the one assigned to every {{< glossary_tooltip text="Service" term_id="service" >}} in Kubernetes </del> <ins> : A virtual IP address, such as the one assigned to every {{< glossary_tooltip text="Service" term_id="service" >}} in Kubernetes </ins> [kube-proxy](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) <del> : a network daemon that orchestrates Service VIP management on every node </del> <ins> : A network daemon that orchestrates Service VIP management on every node </ins> ### Prerequisites
Change:
There is something wrong with this format
Please mention issue title and description in Primary (English) language.
/triage needs-information
Page:
chinese
/language zh Yes, there is a format issue in Chinese translation page under metadata and spec secession. English website content is having accurate format. I think we should sync this page with English translation.
/kind bug Below is the correct format:
/remove-triage needs-information /assign
/retitle [zh] Incorrect YAML format in example in "Create static Pods" page
/triage accepted
Seems there are some other changes also present in page. better someone who knows zh language can pick this issue to resolve. /unassign
/assign

Discussion:
<!-- 1. Choose a directory, say `/etc/kubernetes/manifests` and place a web server Pod definition there, for example `/etc/kubernetes/manifests/static-web.yaml`: <ins> # Run this command on the node where kubelet is running </ins> --> 2. 选择一个目录，比如在 `/etc/kubernetes/manifests` 目录来保存 Web 服务 Pod 的定义文件，例如 `/etc/kubernetes/manifests/static-web.yaml`： <del> <!-- # Run this command on the node where kubelet is running --> </del> ```shell # 在 kubelet 运行的节点上执行以下命令 mkdir -p /etc/kubernetes/manifests/
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: <img width="470" alt="image" src="" quick navigation link is broken Proposed Solution: It looks like it's due to a small typo. <img width="391" alt="image" src=""Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en Yes its a typo mistake
Let's first the issue have the label triage accepted, then only work on this!!
/triage accepted /priority backlog

Discussion:
This repository contains the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute! - [Contributing to the docs](#contributing-to-the-docs) <del> - [Localization READMEs](#localization-readmemds) </del> <ins> - [Localization READMEs](#localization-readmes) </ins> ## Using this repository
Change:
This is a Bug Report Problem: The link available for is broken. The has whose value is which is "broken". Proposed Solution: changes to Page to Update: Additional Information: I am willing to submit the PR.
/kind documentation
/assign
/retitle Broken hyperlink for "Translating content" in "Localizing Kubernetes documentation" page /language en
/triage accepted /priority backlog

Discussion:
### Suggest changes Create or update your chosen localized page based on the English original. See <del> [translating content](#translating-content) for more details. </del> <ins> [localize content](#localize-content) for more details. </ins> If you notice a technical inaccuracy or other problem with the upstream (English) documentation, you should fix the upstream documentation first and
Change:
This is a Bug Report Problem: This line present is same as यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिए गए Hugo का उपयोग करके स्थानीय रूप से का तरीका देखें। which is also present in the same place  Page to Update:
/retitle [hi] Duplicate instruction in Hindi README- /language hi
/triage accepted

Discussion:
> यदि आप विंडोज पर हैं, तो आपको कुछ और टूल्स की आवश्यकता होगी जिन्हें आप [Chocolatey](https://chocolatey.org) के साथ इंस्टॉल कर सकते हैं। <del> > यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे Hugo का उपयोग करके स्थानीय रूप से साइट चलाना देखें। </del> यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिए गए Hugo का उपयोग करके स्थानीय रूप से [साइट को चलाने](#hugo-का-उपयोग-करते-हुए-स्थानीय-रूप-से-साइट-चलाना) का तरीका देखें। यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो स्थानीय रूप से `कुबेरनेट्स-ह्यूगो` Docker image बनाएँ: