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 The narrow (square grid) and wide (single row) logo layouts for are fine, however there is an intermediate state that we'd like to cut out. See for an animation showing the issue Why is this needed It's odd to show the logos in a 3:1 split. Two even rows would look better. Comments The fix for this should be Sass / CSS changes only. /area web-development Follows on from
/kind cleanup
I'm interested to see how this works. I spent a good hour fiddling with flexboxes and now I cascadingly hate stylesheets
Flexbox was handy when we had 3 items. Now we have a different challenge. The way I'd do it is with CSS grid, and assign items to specific grid columns and rows using media queries (default to a single row; use a square for narrow viewports only). If we wanted to not use a media query here then I think we'd have to change the HTML to add helper elements, and I'm not so keen on that.
/remove-kind feature
/assign
Also /triage accepted

Discussion:
body.cid-training section.call-to-action .main-section > div.call-to-action > div { padding: 0 2rem 0 2rem; } <ins> body.cid-training section.call-to-action .main-section > div.call-to-action div.cta-image { padding: 0 2rem 0 2rem; /* Change display to CSS Grid layout with 2 columns that autofill */ display: grid; grid-template-columns: repeat(auto-fill, minmax(50%, 1fr)); } /* Make the CTA text fill 100% of the viewport */ body.cid-training section.call-to-action .main-section > div.call-to-action > div.cta-text { width: 100%; } /* Resize the div that contains the images so that the images wrap 2 at a time and have no margin issues */ body.cid-training section.call-to-action .main-section > div.call-to-action { width: 60%; margin: auto; padding-top: 20px; } </ins> }
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: All the current maintainers of Hindi localization are not mentioned in README- isn't grammatically correct. Proposed Solution: Add and with appropriate links to -Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language hi
Can I work on this?
Sure, Here are the links to be Slack: Twitter: GitHub: Slack: Twitter: /assign
/triage accepted
/good-first-issue
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 : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hey I'm working on this right now
Sorry but is already assigned to fix this. We would love to see more contributions from you.
/unassign

Discussion:
## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन <del> आप पर हिंदी स्थानीयकरण के maintainers तक पहुँच सकते हैं: </del> <ins> आप हिंदी स्थानीयकरण के मैन्टेनरों तक पहुँच सकते हैं: * Anubhav Vardhan ([Slack](https://kubernetes.slack.com/archives/D0261C0A3R8), [Twitter](https://twitter.com/anubha_v_ardhan), [GitHub](https://github.com/anubha-v-ardhan)) * Divya Mohan ([Slack](https://kubernetes.slack.com/archives/D027R7BE804), [Twitter](https://twitter.com/Divya_Mohan02), [GitHub](https://github.com/divya-mohan0209)) </ins> * Yashu Mittal ([Twitter](https://twitter.com/mittalyashu77), [GitHub](https://github.com/mittalyashu)) * [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-hi) ## स्थानीय रूप से डॉकर का उपयोग करके साइट चलाना
Change:
This is a Bug Report <!--Required Information--Problem: All the hyperlinks which are pointing to this are broken. Proposed Solution: I suppose it should point to this now. Page to Update: /language en <!--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
Can I work on this?
/assign

Discussion:
[handbook-patch-release]: https://git.k8s.io/sig-release/release-engineering/role-handbooks/patch-release-team.md [k-sig-release-releases]: https://git.k8s.io/sig-release/releases [patches]: /patch-releases.md <del> [src]: https://git.k8s.io/community/committee-product-security/README.md </del> <ins> [src]: https://git.k8s.io/community/committee-security-response/README.md </ins> [release-team]: https://git.k8s.io/sig-release/release-team/README.md [security-release-process]: https://git.k8s.io/security/security-release-process.md
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like Proposed Solution: Changing the shortcode to use and instead of and should fix this. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Please let us know if any help is needed! /good-first-issue /help
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: The skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Please let us know if any help is needed! /help </details
/assign
/triage accepted
Hi is this what you are asking to do in this pr --! sorry, actually I am new to k8s so not much familiar with its related terminologies!
Your PR is the right fix :) You don't see the change in markdown because this is something hugo does. If you visit the deployed preivew on the PR you'll see your change in action.

Discussion:
For example: - a localization branch sourced from `main` must be merged into `main`. <del> - a localization branch sourced from `release-{{ skew "prevMinorVersion" }}` must be merged into `release-{{ skew "prevMinorVersion" }}`. </del> <ins> - a localization branch sourced from `release-{{% skew "prevMinorVersion" %}}` must be merged into `release-{{% skew "prevMinorVersion" %}}`. </ins> {{< note >}} If your localization branch was created from `main` branch but it is not merged into `main` before new release branch `{{< release-branch >}}` created, merge it into both `main` and new release branch `{{< release-branch >}}`. To merge your localization branch into new release branch `{{< release-branch >}}`, you need to switch upstream branch of your localization branch to `{{< release-branch >}}`.
Change:
Recently I am exploring the and found that section of in the Chinese document is outdated so I tried to update it. en: zh:
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 zh

Discussion:
<!-- ## Debugging via a shell on the node {#node-shell-session} <del> If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host, but this should generally not be necessary given tools in the Kubernetes API. Therefore, if you find yourself needing to ssh into a machine, please file a feature request on GitHub describing your use case and why these tools are insufficient. </del> <ins> If none of these approaches work, you can find the Node on which the Pod is running and create a privileged Pod running in the host namespaces. To create an interactive shell on a node using `kubectl debug`, run: </ins> --> <del> ## 在节点上通过 shell 来调试 {#node-shell-session} </del> <ins> ## 在节点上通过 shell 来进行调试 {#node-shell-session} </ins> <del> 如果这些方法都不起作用，你可以找到运行 Pod 的主机并通过 SSH 进入该主机， 但是如果使用 Kubernetes API 中的工具，则通常不需要这样做。 因此，如果你发现自己需要使用 ssh 进入主机，请在GitHub 上提交功能请求， 以描述你的用例以及这些工具不足的原因。 </del> <ins> 如果这些方法都不起作用，你可以找到运行 Pod 的节点，然后在节点上部署一个运行在宿主名字空间的特权 Pod。 你可以通过`kubectl debug` 在节点上创建一个交互式 shell： ```shell kubectl debug node/mynode -it --image=ubuntu ``` ``` Creating debugging pod node-debugger-mynode-pdx84 with container debugger on node mynode. If you don't see a command prompt, try pressing enter. root@ek8s:/# ``` <!-- When creating a debugging session on a node, keep in mind that: * `kubectl debug` automatically generates the name of the new Pod based on the name of the Node. * The container runs in the host IPC, Network, and PID namespaces. * The root filesystem of the Node will be mounted at `/host`. Don't forget to clean up the debugging Pod when you're finished with it: --> 当在节点上创建调试会话，注意以下要点： * `kubectl debug` 基于节点的名字自动生成新的 Pod 的名字。 * 新的调试容器运行在宿主命名空间里（IPC, 网络 还有PID命名空间）。 * 节点的根文件系统会被挂载在 `/host`。 当你完成节点调试时，不要忘记清理调试 Pod： ```shell kubectl delete pod node-debugger-mynode-pdx84 ``` </ins>  No newline at end of file
Change:
The "Install kubeadm" page has an incorrect capitalization in the "" section. Should be /language en /kind cleanup /good-first-issue
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 : The "Install kubeadm" page has an incorrect capitalization in the "" section. You can use telnet to check if a port is open. For example: /kind cleanup /good-first-issue </details
/triage accepted
/remove-kind bug
Hey, could you please assign me ?
/assign

Discussion:
## Check required ports These [required ports](/docs/reference/ports-and-protocols/) <del> need to be open in order for Kubernetes components to communicate with each other. You can use `telnet` to check if a port is open. for example: </del> <ins> need to be open in order for Kubernetes components to communicate with each other. You can use telnet to check if a port is open. For example: </ins> ```shell telnet 127.0.0.1 6443
Change:
In Kubernetes Tutorials page- It is mentioned that a Kubernetes cluster that handles production traffic should have a minimum of three nodes. But there is no explanation provided as to why this is so. Suggestion to add a one-liner that a minimum of 3 master nodes is necessary for high availability.
/triage accepted
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind improvements 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
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind improvement 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

Discussion:
<div class="row"> <div class="col-md-8"> <p><b>The Control Plane is responsible for managing the cluster.</b> The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p> <del> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </del> <ins> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an etcd member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.</p> </ins> </div> <div class="col-md-4">
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 The version of the crictl in "install kubeadm" doc when installing without package managers is v1.17.0. It should be v1.22.0. Why is this needed I think it should be updated because newer versions are available unless there are compatibility issues with Kubelet. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This is where problem exists:
/sig cluster-lifecycle /triage accepted /help
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 : /sig cluster-lifecycle /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
Hello, I would want to work on this issue as my 1st PR . Can you please assign this to me :)
Hi I think you can start working on it and submit a pull request. I do not know how to assign it to you.
/assign
Thanks. Just to confirm I have to change the crictl version to v1.22.0.
I'not sure. Maybe kubelet is not compatible with crictl v1.22.0 or there was another reason.
this matrix might be out of date, but according to it =1.16 critools are compatible with =1.16 kubernetes:
i'd say just send the PR to update and if something breaks for someone users will report it. (our current e2e tests are not using the latest 1.22 critools release...)
Okay sure. Thanks I will send the PR

Discussion:
Install crictl (required for kubeadm / Kubelet Container Runtime Interface (CRI)) ```bash <del> CRICTL_VERSION="v1.17.0" </del> <ins> CRICTL_VERSION="v1.22.0" </ins> ARCH="amd64" curl -L "https://github.com/kubernetes-sigs/cri-tools/releases/download/${CRICTL_VERSION}/crictl-${CRICTL_VERSION}-linux-${ARCH}.tar.gz" | sudo tar -C $DOWNLOAD_DIR -xz ```
Change:
This is a Bug Report Problem: The link for Authorization under in is wrong. It is redirected to the which is wrong, It should redirect to Proposed Solution: We will have to use this link: for Authorization instead of . Page to Update:
/assign
Fixed it here:
Hey Do check on issue triage for this! Thank you.
/triage accepted
/language en

Discussion:
### Authorization <del> [Authorization](/docs/reference/access-authn-authz/webhook/) determines whether specific users can read, write, and do other operations on API resources. It works at the level of whole resources -- it doesn't discriminate based on arbitrary object fields. If the built-in authorization options don't meet your needs, and [Authorization webhook](/docs/reference/access-authn-authz/webhook/) allows calling out to user-provided code to make an authorization decision. </del> <ins> [Authorization](/docs/reference/access-authn-authz/authorization/) determines whether specific users can read, write, and do other operations on API resources. It works at the level of whole resources -- it doesn't discriminate based on arbitrary object fields. If the built-in authorization options don't meet your needs, [Authorization webhook](/docs/reference/access-authn-authz/webhook/) allows calling out to user-provided code to make an authorization decision. </ins> ### Dynamic Admission Control
Change:
Following link redirects to an empty page without any content
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
Same issue as

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
Change:
page not rendering correctly.
Wrong formatting, flows across the width of screen Similar issue ! /triage accepted
Removing the property from the body tag seems to fix the problem. Not sure if the invalid property is intended? !
Most likely caused by 2 days ago. Suggest removing these two lines from the css global body selector in that PR.
would you mind renaming this issue, to make it more descriptive; indicating it's a bug and that the layout it broken for multiple pages?
Thanks for fixing this at priority

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
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: Contents for <emConnecting Applications with Services</emwhich is under Services, Load Balancing, and Networking Concept in the Documentation is not displaying. I tried accessing it on both Chrome and Firefox but the same result. Proposed Solution: Page content for <emConnecting Applications with Services</emwhich is under Services, Load Balancing, and Networking Concept in the Documentation should display and not be blank. 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
!
Hey thank you for raising this issue I tried opening this too it seems to be blank also I tried opening in my mobile browser without desktop mode on and I found the content correctly
Just check the mobile version and its available but the text are not fully responsive. I personally read the docs from my laptop and it will be nice to have the content available for larger screens.
yeah definately and as I see we have a PR for the same issue in
That's really great!

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
Change:
I've got a 3440x1440 display, but doesn't fit on my screen without horizontal scrolling. The pages for 'Configuration Best Practices' and 'ConfigMaps' are OK, but 'Secrets' and 'Managing Resources for Containers' are not.
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 would be very helpful if you could avoid all this blank space on the web pages, anyway. It just reduces the amount of information that can be read without being distracted by looking for your mouse to scroll the text.

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
Change:
Page is not lined out in the correct way, which makes it unreadable.
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
Same issue as

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;