jiebi/CodeConvo huggingface dataset:
Change:
outline: none; padding: .5em 0 .5em 0; } <ins> /* CSS for 'figure' full-screen display */ /* Define styles for full-screen overlay */ .figure-fullscreen-overlay { position: fixed; inset: 0; z-index: 9999; background-color: rgba(255, 255, 255, 0.95); /* White background with some transparency */ display: flex; justify-content: center; align-items: center; padding: calc(5% + 20px); box-sizing: border-box; } /* CSS class to scale the image when zoomed */ .figure-zoomed { transform: scale(1.2); } /* Define styles for full-screen image */ .figure-fullscreen-img { max-width: 100%; max-height: 100%; object-fit: contain; /* Maintain aspect ratio and fit within the container */ } /* Define styles for close button */ .figure-close-button { position: absolute; top: 1%; right: 2%; cursor: pointer; font-size: calc(5vw + 10px); color: #333; } </ins>  No newline at end of file

Discussion:
This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:
/area web-development /kind feature
/area web-development Something similar to https://medium- ?
/retitle Enable click-to-zoom for some diagrams and other images
/triage accepted /priority backlog /lifecycle frozen
Thanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.
For now I'll investigate more and try to find out what can work so assigning it to myself /assign
A couple of hints:
There is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code
one is a good reference for same functionality with example. I'll try both and raise a PR after that.
We using vector images.
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
My apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.
This could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen
Let me see if I can assist with this. Edit: I request review and feedback on pull request
Change:
Let's now recreate the Service to use a cloud load balancer, just change the `Type` of `my-nginx` Service from `NodePort` to `LoadBalancer`: --> <del> 让我们重新创建一个 Service，使用一个云负载均衡器，只需要将 `my-nginx` Service 的 `Type` 由 `NodePort` 改成 `LoadBalancer`。 </del> <ins> 让我们重新创建一个 Service，使用一个云负载均衡器，只需要将 `my-nginx` Service 的 `Type` 由 `NodePort` 改成 `LoadBalancer`。 </ins> ```shell kubectl edit svc my-nginx

Discussion:
Nginx https 404
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 It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
* The rollout gets stuck. You can verify it by checking the rollout status: ```shell <del> kubectl rollout status deployment.v1.apps/nginx-deployment </del> <ins> kubectl rollout status deployment/nginx-deployment </ins> ``` The output is similar to this:

Discussion:
I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.
I think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : I think that an appropriate improvement that's in line with your comment is to change to run instead. /language en /kind cleanup /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
/retitle Multiple way to refer to Deployment resource confusing in Deployment concept page
/assign
Change:
What constitutes a compatible change and how to change the API are detailed by the [API change document](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/api_changes.md). <del> ## API Swagger definitions </del> <ins> ## OpenAPI and Swagger definitions </ins> <del> Complete API details are documented using [Swagger v1.2](http://swagger.io/). The Kubernetes apiserver (aka "master") exposes an API that can be used to retrieve the Swagger Kubernetes API spec located at `/swaggerapi`. You can also enable a UI to browse the API documentation at `/swagger-ui` by passing the `--enable-swagger-ui=true` flag to apiserver. </del> <ins> Complete API details are documented using [Swagger v1.2](http://swagger.io/) and [OpenAPI](https://www.openapis.org/). The Kubernetes apiserver (aka "master") exposes an API that can be used to retrieve the Swagger v1.2 Kubernetes API spec located at `/swaggerapi`. You can also enable a UI to browse the API documentation at `/swagger-ui` by passing the `--enable-swagger-ui=true` flag to apiserver. </ins> <del> We also host a version of the [latest API documentation](http://kubernetes.io/docs/api-reference/README/). This is updated with the latest release, so if you are using a different version of Kubernetes you will want to use the spec from your apiserver. </del> <ins> We also host a version of the [latest v1.2 API documentation UI](http://kubernetes.io/kubernetes/third_party/swagger-ui/). This is updated with the latest release, so if you are using a different version of Kubernetes you will want to use the spec from your apiserver. Staring kubernetes 1.4, OpenAPI spec is also available at `/swagger.json`. While we are transitioning from Swagger v1.2 to OpenAPI (aka Swagger v2.0), some of the tools such as kubectl and swagger-ui are still using v1.2 spec. OpenAPI spec is in Beta as of Kubernetes 1.5. </ins> Kubernetes implements an alternative Protobuf based serialization format for the API that is primarily intended for intra-cluster communication, documented in the [design proposal](https://github.com/kubernetes/kubernetes/blob/{{ page.githubbranch }}/docs/proposals/protobuf.md) and the IDL files for each schema are located in the Go packages that define the API objects.

Discussion:
In we mentioned swagger 1.2 however as of 1.5 we will support OpenAPI (swagger 2.0) spec. We should update docs to reflect that.
I believe this is pending with the 1.5 changes that are coming out.
Excellent, is there any staging area with that change I can look at?
I don't see any doc changes for OpenAPI. Please link to the change if I am wrong, otherwise we should at lets mention OpenAPI in the docs and later on (1.6 maybe) remove swagger 1.2 references completely.
Change:
padding-top: 2rem !important; } } <ins> .ui-widget { font-family: inherit; font-size: inherit; } .ui-widget-content a { color: $blue; } </ins> } section {

Discussion:
This is a Bug Report Links within the tab component are not displaying using the site link color. Problem: The color of links within tab components is defaulting to . The link is inheriting the color value from jquery-ui- Proposed Solution: Update the style for ui-widget-content -a Page to Update: Start by looking at . Examples: See link in Flatcar Container Linux tab in Look as the "vSphere" tab at the bottom of the page.
Related to PR .
/kind bug /priority backlog /area web-development Feel free to reprioritize
/assign
Change:
clear: both; padding: 0px; margin-bottom: 2em; <ins> width: 100%; </ins> } <del> .col { </del> <ins> section.call-to-action { color: #ffffff; background-color: #3371e3; } section.call-to-action .main-section { max-width: initial; } section.call-to-action .main-section > div.call-to-action { display: flex; flex-direction: row; flex-wrap: wrap; flex-basis: auto; justify-content: center; align-items: center; margin: initial; padding-top: 5rem; padding-bottom: 5rem; } section.call-to-action .main-section > div.call-to-action > div { order: 1; padding: 20px; } section.call-to-action .main-section .cta-text { text-align: center; flex: 1 1 auto; max-width: 50vw; } /* if max() and min() are available, use them */ section.call-to-action .main-section .cta-text { min-width: min(20em, 50vw); max-width: min(1000px, 50vw); } section.call-to-action .main-section .cta-image.cta-image-before { order: 0 } section.call-to-action .main-section .cta-image.cta-image-after { order: 2 } section.call-to-action .main-section .cta-image > img { </ins> display: block; <del> float:left; </del> <ins> width: 150px; margin: auto; } .col { display: flex; flex-direction: row; float: left; </ins> margin: 1% 0 1% 1.6%; <del> background-color: #f9f9f9; </del> } .col:first-child { margin-left: 0; } .col-container { <del> display: table; /* Make the container element behave like a table */ </del> <ins> display: flex; /* Make the container element behave like a table */ flex-direction: row; </ins> width: 100%; /* Set full-width to expand the whole page */ padding-bottom: 30px; } .col-nav { <del> display: table-cell; /* Make elements inside the container behave like table cells */ </del> <ins> display: flex; flex-grow: 1; </ins> width: 18%; background-color: #f9f9f9; padding: 20px;

Discussion:
This is feedback by email from within the CNCF/Linux Foundation: add the CKA/CKAD logos from to the page.
I'll take care of this, so assign it to me :)
/assign
Change:
> यदि आप विंडोज पर हैं, तो आपको कुछ और टूल्स की आवश्यकता होगी जिन्हें आप [Chocolatey](https://chocolatey.org) के साथ इंस्टॉल कर सकते हैं। <del> > यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे Hugo का उपयोग करके स्थानीय रूप से साइट चलाना देखें। </del> यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिए गए Hugo का उपयोग करके स्थानीय रूप से [साइट को चलाने](#hugo-का-उपयोग-करते-हुए-स्थानीय-रूप-से-साइट-चलाना) का तरीका देखें। यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो स्थानीय रूप से `कुबेरनेट्स-ह्यूगो` Docker image बनाएँ:

Discussion:
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
Change:
コントロールプレーンコンポーネントは、クラスターに関する全体的な決定(スケジューリングなど)を行います。また、クラスターイベントの検出および応答を行います(たとえば、deploymentの`replicas`フィールドが満たされていない場合に、新しい {{< glossary_tooltip text="Pod" term_id="pod">}} を起動する等)。 コントロールプレーンコンポーネントはクラスター内のどのマシンでも実行できますが、シンプルにするため、セットアップスクリプトは通常、すべてのコントロールプレーンコンポーネントを同じマシンで起動し、そのマシンではユーザーコンテナを実行しません。 <del> マルチマスター VMセットアップの例については、[高可用性クラスターの構築](/docs/admin/high-availability/) を参照してください。 </del> <ins> 複数のマシンにまたがって実行されるコントロールプレーンのセットアップ例については、[kubeadmを使用した高可用性クラスターの構築](/ja/docs/setup/production-environment/tools/kubeadm/high-availability/) を参照してください。 </ins> ### kube-apiserver

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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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
Change:
ガベージコレクションは、最後に使用された時間に基づいて、最も古いものから順にイメージを削除します。 kubeletは、ディスク使用量が`LowThresholdPercent`値に達するまでイメージを削除します。 <del> ### コンテナイメージのガベージコレクション {#container-image-garbage-collection} </del> <ins> ### コンテナのガベージコレクション {#container-image-garbage-collection} </ins> kubeletは、次の変数に基づいて未使用のコンテナをガベージコレクションします。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. A link text to this page from other pages have already been fixed. The current page is still "" and it should be fixed "". 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
Change:
* [Cluster DNS](/zh/docs/concepts/services-networking/dns-pod-service/) * [Headless Services](/zh/docs/concepts/services-networking/service/#headless-services) * [PersistentVolumes](/zh/docs/concepts/storage/persistent-volumes/) <del> * [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/{{< param "githubbranch" >}}/staging/persistent-volume-provisioning/) </del> <ins> * [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/) </ins> * [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) * [kubectl CLI](/zh/docs/user-guide/kubectl/)

Discussion:
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
Link: /retitle [zh] Issue with /zh/docs/tutorials/stateful-application/basic-stateful-set
/assign
Change:
Descargue el archivo de comprobación kubectl-convert: ```powershell <del> curl -LO https://dl.k8s.io/{{% param "fullversion" %}}/bin/windows/amd64/kubectl-convert.exe.sha256 </del> <ins> curl -LO https://dl.k8s.io/v{{% skew currentPatchVersion %}}/bin/windows/amd64/kubectl-convert.exe.sha256 </ins> ``` Valide el binario kubectl-convert con el archivo de comprobación:

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 param is deprecated. Proposed Solution: Replace the shortcode (Spanish pages), for example with or something close. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Part of /language es
/triage accepted /area localization /priority backlog
Change:
- operation --- <del> एग्रीगेशन लेयर आपको अपने क्लस्टर में अतिरिक्त कुबेरनेट्स-शैली API स्थापित करने देता है।``` </del> <ins> एग्रीगेशन लेयर आपको अपने क्लस्टर में अतिरिक्त कुबेरनेट्स-शैली API स्थापित करने देता है। </ins> <!--more--> <del> जब आपने {{< glossary_tooltip text="कुबेरनेट्स API सर्वर" term_id="kube-apiserver" >}} को [अतिरिक्त API का समर्थन](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) करने के लिए कॉन्फ़िगर किया हो, आप कुबेरनेट्स एपीआई में URL पथ का "दावा" करने के लिए `APIService` ऑब्जेक्ट जोड़ सकते हैं। </del> <ins> जब आपने {{< glossary_tooltip text="कुबेरनेट्स API सर्वर" term_id="kube-apiserver" >}} को [अतिरिक्त API का समर्थन](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) करने के लिए कॉन्फ़िगर किया हो, आप कुबेरनेट्स API में URL पाथ का "दावा" करने के लिए `APIService` ऑब्जेक्ट जोड़ सकते हैं। </ins>

Discussion:
Observed this issue while reading . I have gone through the the whole file need to do these changes. ्रीगेशन लेयर आपको अपने क्लस्टर में अतिरिक्त कुबेरनेट्स-शैली API स्थापित करने देता है। Need to remove this कुबेरनेट्स need to change this to -API ें URL -URL पाथ /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
/language hi /kind bug
Change:
[blackfriday] hrefTargetBlank = true fractions = false <ins> smartDashes = false </ins> [frontmatter] date = ["date", ":filename", "publishDate", "lastmod"]

Discussion:
reference docs render with (single UTF8 8211) instead of (ANSI 45) even if a generated reference page contains the regular double dash . see vs this makes users copy-pasting command line flags insert bogus flags in their setup. request: please make the website render the double dash . /kind bug /sig docs /cc
reported here on slack:
/priority important-longterm (or higher)
Thanks for filing the issue
Emm. Hugo is again doing some conversion behind the scene. If you check the reference page we generated: you can see that the is in the source. Hugo converted into , for unknown reason.
I suspect we will find pages that have relied on the smart dashes behavior. For a different, lasting fix, maybe we change the docs generation to write HTML/Markdown that looks like: or maybe we switch to a newer Hugo that implements more of CommonMark and that lets us re-enable smart dashes without breaking reference docs?
Wow thanks for implementing the change so quickly after the report <3 you guys rock!!
Change:
{{< feature-state for_k8s_version="v1.14" state="stable" >}} <del> 追加のフィードバックやシグナルをPodStatus:_Pod readiness_に注入できるようにします。これを使用するには、Podの`spec`で`readinessGates`を設定して、kubeletがPodのReadinessを評価する追加の状態のリストを指定します。 </del> <ins> 追加のフィードバックやシグナルをPodStatus:*Pod readiness*に注入できるようにします。これを使用するには、Podの`spec`で`readinessGates`を設定して、kubeletがPodのReadinessを評価する追加の状態のリストを指定します。 </ins> ReadinessゲートはPodの`status.conditions`フィールドの現在の状態によって決まります。Kubernetesが`Podのstatus.conditions`フィールドでそのような状態を発見できない場合、ステータスはデフォルトで`False`になります。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted
Change:
<ins> {{/* Link directly to documentation etc., if possible. */}} {{ $langPage := cond (gt (len .Translations) 0) . .Site.Home }} <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> {{ $langPage.Language.LanguageName }} </a> <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdownMenuLink"> {{ range $langPage.Translations }} <a class="dropdown-item" href="{{ .RelPermalink }}">{{ .Language.LanguageName }}</a> {{ end }} </div> </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!
Change:
title: kube-apiserver id: kube-apiserver date: 2018-04-12 <del> full_link: /docs/reference/generated/kube-apiserver/ </del> <ins> full_link: /zh/docs/reference/command-line-tools-reference/kube-apiserver/ </ins> short_description: > <del> 主节点上负责提供 Kubernetes API 服务的组件；它是 Kubernetes 控制面的前端。 </del> <ins> 提供 Kubernetes API 服务的控制面组件。 </ins> aka: tags:

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: when I finished the translation of docs/reference/using-api/health-, I found a broken link when clicked the "API ":  Proposed Solution: fix it in
/language zh /assign /kind bug
/triage accepted
Change:
# # A match exists between an image and a matchImage when all of the below are true: # - Both contain the same number of domain parts and each part matches. <del> # - The URL path of an imageMatch must be a prefix of the target image URL path. # - If the imageMatch contains a port, then the port must match in the image as well. </del> <ins> # - The URL path of an matchImages must be a prefix of the target image URL path. # - If the matchImages contains a port, then the port must match in the image as well. </ins> # # Example values of matchImages: # - 123456789.dkr.ecr.us-east-1.amazonaws.com

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: In , the word appears 3 times: But the exact name of field is actually. Proposed Solution: In , [L85-L86] [L144-L145] And optionally, we might wrap with backticks; like: through the whole doc. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
AFAIK we use backticks only for API Resource names per the style guide. We don't need to have the backticks to wrap matchImages. I agree with the rest of the suggestion, though. /triage accepted
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
I would like to give a try on this. /assign