jiebi/CodeConvo huggingface dataset:
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 enhanced? I think "Subscribe to KubeWeekly Newsletter" section at bottom of Home page is:- too much white/grey space that can be shortend. input area where user will enter his/her email id is a little small and maybe it will be better if that gets a little enlarged. <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --!
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
/area web-development
/priority backlog
Page:
/good-first-issue The files to edit can be found in assets/scss
/remove-help /remove-good-first-issue Don't label issues as good first issues unless they are also triaged as Accepted
/assign
when we shorten this white space I feel there is no need to enlarge the input area as it aligns perfectly once shorten. !
/close
Closing this issue. <detailsIn response to : /close </details

Discussion:
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */ </style> <br> <del> <br> </del> <div id="mc_embed_signup"> <form action="https://kubeweekly.us10.list-manage.com/subscribe/post?u=3885586f8f1175194017967d6&amp;id=11c1b8bcb2" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate> <div id="mc_embed_signup_scroll"> <p style="font-size: 20px">{{ T "main_kubeweekly_baseline" }}</p> <del> <br /> </del> <input type="email" value="" name="EMAIL" class="email" id="mce-EMAIL" placeholder="{{ T "input_placeholder_email_address" }}" aria-label="email" required> <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups--> <div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_3885586f8f1175194017967d6_11c1b8bcb2" tabindex="-1" value=""></div>

</form> <h5 style="text-align: center"><a href="https://us10.campaign-archive.com/home/?u=3885586f8f1175194017967d6&id=11c1b8bcb2" aria-label="Kube Weekly" style="color: #3371E3; font-weight: 400; font-size: 20px">{{ T "main_kubeweekly_past_link" }}</a></h5> </div> <del> <br> <br> </del> <!--End mc_embed_signup--> </div> </section>
Change:
This is a Bug Report Problem: There are whitespaces on both sides of the footer on the blog page. ! Page to Update:
/area web-development
/priority backlog /triage accepted
A little whitespace line across whole page is also present , but maybe in this case it will get resolved by fixing footer.

Discussion:
</div> </div> </div> <del> {{ partial "footer.html" . }} </del> </div> <ins> {{ partial "footer.html" . }} </ins> {{ partial "scripts.html" . }} </body> </html>  No newline at end of file
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: One of the parameters, , is incorrectly listed as . Proposed Solution: Change 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
/language en /sig docs /remove-kind bug /kind feature

Discussion:
{{< feature-state for_k8s_version="v1.17" state="stable" >}} **Kubelet Flag**: `--reserved-cpus=0-3` <del> **KubeletConfiguration Flag**: `reservedSystemCpus: 0-3` </del> <ins> **KubeletConfiguration Flag**: `reservedSystemCPUs: 0-3` </ins> `reserved-cpus` is meant to define an explicit CPU set for OS system daemons and kubernetes system daemons. `reserved-cpus` is for systems that do not intend to
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 enhanced? At feature section, Original K8s site contain 10 highlighted features and in "Ja" Localized version contain 9 highlighted features. That's the mismatch i wanted to address with this issue. ! !
/language ja /sig docs /area web-development
/assign
/assign
It looks no change on this issue for several months, so I remove the assignee. feel free to re-assign :) /unassign /unassign
/triage accepted
/assign
Target file: Japanese Localization document:
Thank you for your working!!

Discussion:
title: Kubernetesを拡張する weight: 110 description: Kubernetesクラスターの挙動を変えるいろいろな方法 <ins> feature: title: 拡張性を考慮した設計 description: > アップストリームのソースコードを変更することなく、Kubernetesクラスターに機能を追加できます。 </ins> content_type: concept no_list: true ---
Change:
simple typo: "The API server is willing accept updates to resources that are not valid after the update" It probably should be "The API server is willing to accept updates to resources that are not valid after the update"
Page related to the issue: /language en
/assign
Hi Thank you for raising the issue please let me know if you want to work on this issue; I will unassign it. Also, make sure to follow the community guidelines by not creating multiple issues on a single page.
Issue could have also been here, instead of a separate issue /remove-kind bug /kind feature /sig docs
The issue is resolved here .

Discussion:
cluster. Provided you enabled the feature gate, Kubernetes implements _validation racheting_ <del> for CustomResourceDefinitions. The API server is willing accept updates to resources that </del> <ins> for CustomResourceDefinitions. The API server is willing to accept updates to resources that </ins> are not valid after the update, provided that each part of the resource that failed to validate was not changed by the update operation. In other words, any invalid part of the resource that remains invalid must have already been wrong.

OpenAPIV3 schema under certain conditions. Users can update to the new schema safely without bumping the version of the object or breaking workflows. <del> While most validations placed in the OpenAPIV3 schema of a CRD are support </del> <ins> While most validations placed in the OpenAPIV3 schema of a CRD support </ins> ratcheting, there are a few exceptions. The following OpenAPIV3 schema validations are not supported by ratcheting under the implementation in Kubernetes {{< skew currentVersion >}} and if violated will continue to throw an error as normally:
Change:
The phrase "beyond discovery permissions given to all authenticated users" in these two sections seems inaccurate. It is quite possible to guess that it references to namely , , , but because of "discovery permissions" phrase it seems to only refer to . It would be better to use different wording, for example: beyond the permissions given by beyond the permissions given by and groups beyond the permissions given by , , cluster roles
/language en /sig docs /kind feature
/retitle Ambiguity in 'beyond discovery permissions' wording in "Using RBAC Authorization" page
/sig auth
/triage accepted A clarification seems reasonable.
/assign
PR working on this issue.

Discussion:
Default RBAC policies grant scoped permissions to control-plane components, nodes, and controllers, but grant *no permissions* to service accounts outside the `kube-system` namespace <del> (beyond discovery permissions given to all authenticated users). </del> <ins> (beyond the permissions given by [API discovery roles](#discovery-roles)). </ins> This allows you to grant particular roles to particular ServiceAccounts as needed. Fine-grained role bindings provide greater security, but require more effort to administrate.

Default RBAC policies grant scoped permissions to control-plane components, nodes, and controllers, but grant *no permissions* to service accounts outside the `kube-system` namespace <del> (beyond discovery permissions given to all authenticated users). </del> <ins> (beyond the permissions given by [API discovery roles](#discovery-roles)). </ins> While far more secure, this can be disruptive to existing workloads expecting to automatically receive API permissions. Here are two approaches for managing this transition:
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 /enhanced? As it can be clearly seen at that the layout of this page is looking somewhat inconsistent due to this visible big-small difference in 'Cards' at 2nd and 3rd row. ! ! Solution: I think this issue can be easily resolved by replacing the 'Card' of (3rd Column, 2nd Row) with (1st Row, 3rd Column) like this:- ! ! As 'Cards' of 2nd row are all vertically tall and 'Cards' of 3rd row are all vertically small. So, replacing these 2nd 'Cards' with each other will possibly solve the problem. By Card, i mean that whole thing inside yellow line (Heading, description, hyperlinks and button)
/area web-development
/assign
A was previously filed. See and for more context.
/retitle Poor alignment for tiles and buttons on home page for docs
/triage accepted /priority backlog
/assign
/retitle Poor alignment for tiles on home page for docs

Discussion:
description: Browse terminology, command line syntax, API resource types, and setup tool documentation. button: View Reference button_path: /docs/reference <del> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </del> - name: contribute title: Contribute to Kubernetes description: Anyone can contribute, whether you're new to the project or you've been around a long time. button: Find out how to help button_path: /docs/contribute <ins> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </ins> - name: Download title: Download Kubernetes description: Install Kubernetes or upgrade to the newest version.
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 /enhanced? As it can be clearly seen at that the layout of this page is looking somewhat inconsistent due to this visible big-small difference in 'Cards' at 2nd and 3rd row. ! ! Solution: I think this issue can be easily resolved by replacing the 'Card' of (3rd Column, 2nd Row) with (1st Row, 3rd Column) like this:- ! ! As 'Cards' of 2nd row are all vertically tall and 'Cards' of 3rd row are all vertically small. So, replacing these 2nd 'Cards' with each other will possibly solve the problem. By Card, i mean that whole thing inside yellow line (Heading, description, hyperlinks and button)
/area web-development
/assign
A was previously filed. See and for more context.
/retitle Poor alignment for tiles and buttons on home page for docs
/triage accepted /priority backlog
/assign
/retitle Poor alignment for tiles on home page for docs

Discussion:
/* DOCS */ .launch-cards { <ins> padding: 0; .launch-card{ padding: 0; display: flex; flex-direction: column; background-color: #DAEAf9; border:2px solid #99B7D3; border-radius: 8px; h2 { text-align: center; font-size: 1.75em; padding: .5em; a{ display: none; } } p { padding: .5em; text-align: center; } ul { list-style: disc; color: #99B7D3; margin: 0 auto; margin-block-end: auto; } </ins> button { <ins> height: min-content; margin: 0 auto; padding: .5em .75em; </ins> cursor: pointer; box-sizing: border-box; <del> background: none; margin: 0; border: 0; } ul, li { list-style: none; padding-left: 0; </del> } } <ins> } </ins> // table of contents .td-toc {

description: Browse terminology, command line syntax, API resource types, and setup tool documentation. button: View Reference button_path: /docs/reference <del> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </del> - name: contribute title: Contribute to Kubernetes description: Anyone can contribute, whether you're new to the project or you've been around a long time. button: Find out how to help button_path: /docs/contribute <ins> - name: training title: "Training" description: "Get certified in Kubernetes and make your cloud native projects successful!" button: "View training" button_path: "/training" </ins> - name: Download title: Download Kubernetes description: Install Kubernetes or upgrade to the newest version.
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 /enhanced? I could have directly raised a PR for it, but i didn't found the file where its written, so raising it as issue. I think "Localizing" word could be better fit here than "Translating", and across K8s site "Localization" term is used everywhere so... Page: ! <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --<!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/language en /sig docs
/retitle Update link text terminology to 'Localizing' instead of 'Translating' on docs home page
/priority backlog /triage accepted
plz plz i want work this. /assign
Can you please let me know how to proceed with making the change? I'm relatvely new contributor. Any pointers will be help me. Thanks:)
The employs to render the Markdown file as a corresponding HTML page. (See and ) To address the issue with link text displayed on the page. Navigate to the markdown file  , go to , and change the attribute in the markdown front matter, to see if it resolves the problem. I hope this suggestion will be of assistance!
wow thanks for taking effort to explain this. Would have taken you less time to fix this yourself than explain me here(lol). Appreciate it, thanks a lot!
Submitted pull request please review when get time. thanks!

Discussion:
card: name: contribute weight: 50 <del> title: Translating the docs </del> <ins> title: Localizing the docs </ins> --- <!-- overview -->
Change:
While Creating the custom scheduler, this image is not available for the general public. If my understanding is correct then my-gcp-project is private and not publically available to eveyone.
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
hi , We sincerely appreciate your inquiry and your effort in seeking assistance. While we value your question, we would like to suggest that the GitHub issue tracker may not be the most ideal platform for obtaining advice on Kubernetes-related matters. We kindly recommend exploring alternative resources, such as the or the Discuss , where you can often find the comprehensive support you are seeking. Thank you for your understanding.
Well noted Mr pranav Get Outlook for iOS
for reference, check out this:
Furthermore, the issue arises from the fact that the custom Kubernetes scheduler image is hosted in a private Google Container Registry, and access to this image is restricted. You can adjust the permissions for the image or make it public if that is acceptable in your use case.
is an example and not an actual project we expect people to use. The page could be clear about this to help people to whom it is not obvious. /kind bug /remove-kind support /retitle Configure Multiple Schedulers content confuses some readers
/language en

Discussion:
pushes the image to [Google Container Registry (GCR)](https://cloud.google.com/container-registry/). For more details, please read the GCR <del> [documentation](https://cloud.google.com/container-registry/docs/). </del> <ins> [documentation](https://cloud.google.com/container-registry/docs/). Alternatively you can also use the [docker hub](https://hub.docker.com/search?q=). For more details refer to the docker hub [documentation](https://docs.docker.com/docker-hub/repos/create/#create-a-repository). </ins> ```shell <del> docker build -t gcr.io/my-gcp-project/my-kube-scheduler:1.0 . gcloud docker -- push gcr.io/my-gcp-project/my-kube-scheduler:1.0 </del> <ins> docker build -t gcr.io/my-gcp-project/my-kube-scheduler:1.0 .     # The image name and the repository gcloud docker -- push gcr.io/my-gcp-project/my-kube-scheduler:1.0 # used in here is just an example </ins> ``` ## Define a Kubernetes Deployment for the scheduler
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: had some on to pending Proposed Solution: Update to incorporate the feedback from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog /help Kubernetes documentation .
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: had some on to pending Update to incorporate the feedback from <!--Kubernetes Version:--/language en /priority backlog /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
/triage accepted
I want to help with this. /assign
Submitted pull request please review.

Discussion:
<code><b>echo "NODE_PORT=$NODE_PORT"</b></code></p> <p>Now we can test that the app is exposed outside of the cluster using <code>curl</code>, the IP address of the Node and the externally exposed port:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></code></p> <del> {{< note >}}<p>If Docker is the container runtime, a minikube tunnel is needed. This is because Docker Desktop does not support ports. <br> </del> <ins> {{< note >}}<p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> </ins> <p>In a separate terminal window, execute:<br> <del> <code><b>$ minikube service kubernetes-bootcamp --url</b></code></p> </del> <ins> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> </ins> <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <del> <code><b>$ curl 127.0.0.1:51082</b></code></p> </del> <ins> <code><b>curl 127.0.0.1:51082</b></code></p> </ins> {{< /note >}} <p>And we get a response from the server. The Service is exposed.</p> </div>
Change:
This is a Bug Report Problem: Sub section " under is having a redundant text(sub section name is repeating as a normal text). ! Proposed Solution: Remove the text that present under "Configure a kubelet image credential provider". Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig docs /language en
I want to help with this. /assign
I try to fix this in

Discussion:
reviewers: - liggitt - cheftako <del> description: Configure the kubelet's image credential provider plugin </del> content_type: task min-kubernetes-server-version: v1.26 weight: 120
Change:
This is a Bug Report <!--Required Information--Problem: The link for under in is incorrect. It is redirecting to the instead of that it should redirect to the . As given in the , the (line 195) shows the heading is changed to from . Proposed Solution: should redirect to the instead of Page to Update:
/language en /sig docs /sig storage
I would like to work on it. /assign
/triage accepted A fixup/clarification is welcome.
/assign
The issue is fixed here:

Discussion:
* Block device mapping * Memory as the storage medium (for example, `emptyDir.medium` set to `Memory`) * File system features like uid/gid; per-user Linux filesystem permissions <del> * Setting [secret permissions with DefaultMode](/docs/concepts/configuration/secret/#secret-files-permissions) (due to UID/GID dependency) </del> <ins> * Setting [secret permissions with DefaultMode](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) (due to UID/GID dependency) </ins> * NFS based storage/volume support * Expanding the mounted volume (resizefs)