jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report Problem: spelling is misplaced as under section in . Proposed Solution: Remove in word under . Page to Update:
/assign
This means “belonging to Kubernetes”. It's similar to “Tim's hat” or “Linus' computer” I don't think we need to fix it. We could reword to make the meaning more clear to people not used to less common cases for possessive apostrophes. /language en
Hi Thanks for this information! How about this. If this seems good then I will update it. WDYT?
I'd be happy with that change.
/remove-kind bug /triage accepted /retitle Confusing punctuation in Kubernetes components page
Fixed it here
Hi I raised PR for it , Could you please take a look. so that it will merge soon.
I am happy for anyone to review PR

Discussion:
date: 2018-04-12 full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/ short_description: > <del> Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data. </del> <ins> Consistent and highly-available key value store used as backing store of Kubernetes for all cluster data. </ins> aka: tags:
Change:
In this section the yaml block is not slidable horizontally which should be.
For me, this issue is reproducible. /area web-development [When the browser window's width is about 2500px] ! [When the browser window's width is about 1240px] !
I had the same issue while working on . I had to get around this by splitting the comments into multiple lines.
/retitle Horizontal scroll not working for code snippet
/kind bug /triage accepted Fixes are welcome
hey! can you assign to me? :D I'll make a PR
/assign

Discussion:
// Consistent spacing for yaml code .language-yaml > span { height: 1.6em; <del> overflow: hidden; </del> } .content__box
Change:
This is a Feature Request What would you like to be Add Abbreviation of in as this word mentioned in . Why is this needed This change will help to understand about containerized applications for the people who are unfamiliar with . Comments kind/feature
/assign
When you say ”abbreviation”, do you mean “explanation”? We might like to borrow from or We also already have - maybe we can expand that? /language en
Hi Yes, basic Explanation/information about . Yes, my idea is same to expand this by adding about . WDYT? If you think it's better to borrow from here, i can follow the same. Please provide your opinion.
Hi Can you please comment on above.
I recommend expanding rather than adding a new entry for “containerized application”. I don't mind whether or not you borrow from the Cloud Native Glossary - feel free to do it whichever way you prefer.
Thanks for your comment, I will work on it and raise PR soon.
Fixed it here .
Should we make this change? Any objections?
Personally, I like what's done here, and I was just waiting for someone with "better experience" in the glossary entries to approve it.
Hi Thanks for sharing your feedback. Can anyone else please comment on it.
/triage accepted

Discussion:
<!--more--> Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling. <ins> The applications that run inside containers are called containerized applications. The process of bundling these applications and their dependencies into a container image is called containerization. </ins>
Change:
Problem: ! Proposed Solution: I have no idea because I have never used Hugo Page to Update:
/area web-development /triage accepted
Can I take care of it?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
It is not clear what is the next step to take this issue to closure. I see tried a number of things in Is the issue that the table "borders" are not rendered correctly in the Note admonition? It seems Hugo is not able to render the borders of the table when it is inside a Note admonition block. In this case it should be reported as a bug to Hugo, right? In the meanwhile, I propose we remove the part of having support for a table inside a Note from the Propose to remove from the below section. !
I have raised a for support in the Hugo forums.
There is an answer on the Hugo forum stating that this is not a Hugo issue. The suggestion is to fix the CSS. Any pointers?

Discussion:
section.k8s-birthday-override:has(div.k8s-birthday-override.revert-to-previous input:not(:checked)) + section { display: none; visibility: hidden; <ins> } /* Apply site-wide table styles for tables in alert callouts (note, caution, warning) */ .alert { &.alert-info, &.alert-caution, &.alert-danger { > table { @extend .table-striped; @extend .table-responsive; @extend .table; } } </ins> }  No newline at end of file

You can have multiple paragraphs and block-level elements inside an admonition. <del> | Or | a | table | </del> <ins> You can also add tables to organize and highlight key information. | Header 1 | Header 2 | Header 3 | | -------- | -------- | -------- | | Data 1   | Data A   | Info X   | | Data 2   | Data B   | Info Y   | </ins> {{< /note >}} {{< caution >}}
Change:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign

Discussion:
<ins> --- title: Istio id: istio date: 2018-04-12 full_link: https://istio.io/docs/concepts/what-is-istio/ short_description: > एक ओपन प्लैटफ़ॉर्म (कुबेरनेट्स-विशिष्ट नहीं) जो माइक्रोसर्विसेज को एकीकृत करने, ट्रैफ़िक प्रवाह को प्रबंधित करने, नीतियों को लागू करने और टेलीमेट्री डेटा को एकत्र करने का एक समान तरीका प्रदान करता हैं। aka: tags: - networking - architecture - extension --- एक ओपन प्लैटफ़ॉर्म (कुबेरनेट्स-विशिष्ट नहीं) जो माइक्रोसर्विसेज को एकीकृत करने, ट्रैफ़िक प्रवाह को प्रबंधित करने, नीतियों को लागू करने और टेलीमेट्री डेटा को एकत्र करने का एक समान तरीका प्रदान करता हैं। <!--more--> Istio को जोड़ने के लिए एप्लिकेशन कोड बदलने की आवश्यकता नहीं है। यह एक सर्विस और नेटवर्क के बीच बुनियादी ढांचे की एक परत है, जिसे जब सर्विस डिप्लॉयमेंट के साथ जोड़ा जाता है, तो इसे आमतौर पर सर्विस मैश (Service Mesh) के रूप में भी जाना जाता है। Istio का कंट्रोल प्लेन अंतर्निहित क्लस्टर प्रबंधन प्लैटफ़ॉर्म को अलग कर देता है, जो कुबेरनेट्स, Mesosphere आदि हो सकते हैं। </ins>
Change:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called content/hi/docs/reference/glossary/pod- Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
Hi , i can work on this issue. Please assign it to me.
/assign Thank you!

Discussion:
<ins> --- title: पॉड विघटन (Pod Disruption) id: pod-disruption date: 2021-05-12 full_link: /docs/concepts/workloads/pods/disruptions/ short_description: > पॉड विघटन वह प्रक्रिया है जिसके द्वारा नोड्स पर पॉड्स को स्वेच्छा से या अनैच्छिक रूप से समाप्त कर दिया जाता है। aka: related: - pod - container tags: - operation --- [पॉड विघटन](/docs/concepts/workloads/pods/disruptions/) वह प्रक्रिया है जिसके द्वारा नोड्स पर पॉड्स को स्वेच्छा से या अनैच्छिक रूप से समाप्त कर दिया जाता है। <!--more--> स्वैच्छिक विघटन एप्लीकेशन मालिक या फिर क्लस्टर प्रशासक अभिप्रायपूर्वक चालू करते है। अनैच्छिक विघटन अनजाने में होते है और वो अपरिहार्य वजह से उत्पन्न हो सकते हैं जैसे कि नोड्स के पास संसाधन ख़तम हो जाना या आकस्मिक विलोपन। </ins>
Change:
First line of the above section has a typo. This should be "manager" instead of "manger".
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign

Discussion:
### Changing the CPU Manager Policy <del> Since the CPU manger policy can only be applied when kubelet spawns new pods, simply changing from </del> <ins> Since the CPU manager policy can only be applied when kubelet spawns new pods, simply changing from </ins> "none" to "static" won't apply to existing pods. So in order to properly change the CPU manager policy on a node, perform the following steps:
Change:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /assign /language en 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
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

Discussion:
- The code is not generic enough for users to try out. As an example, you can embed the YAML file for creating a Pod which depends on a specific <del> [FlexVolume](/docs/concepts/storage/volumes#flexvolume) implementation. </del> <ins> [FlexVolume](/docs/concepts/storage/volumes/#flexvolume-deprecated) implementation. </ins> - The code is an incomplete example because its purpose is to highlight a portion of a larger file. For example, when describing ways to customize a [RoleBinding](/docs/reference/access-authn-authz/rbac/#role-binding-examples),
Change:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /assign /language en 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
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

Discussion:
* [`gcePersistentDisk`](#gcepersistentdisk) * [`vsphereVolume`](#vspherevolume) <del> ### flexVolume (deprecated) </del> <ins> ### flexVolume (deprecated)   {#flexvolume} </ins> {{< feature-state for_k8s_version="v1.23" state="deprecated" >}}

[plugin](/docs/concepts/storage/volumes/#types-of-volumes). The following broad classes of Kubernetes volume plugins are supported on Windows: <del> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume-deprecated) </del> <ins> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume) </ins> * Please note that FlexVolumes have been deprecated as of 1.23 * [`CSI Plugins`](/docs/concepts/storage/volumes/#csi)
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 document kubeadm- had a format error for section. you can find it More information regarding kubeadm can be . Proposed Solution: section should be in the right format like other documents for eg: Page to Update: /kind bug /language en /assign
/triage accepted /kind bug

Discussion:
A kubelet restart will be required after changing `/var/lib/kubelet/config.conf` or `/var/lib/kubelet/kubeadm-flags.env`. <del> {{% heading "whatsnext" %}} </del> <ins> ## {{% heading "whatsnext" %}} </ins> - [Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade) - [Customizing components with the kubeadm API](/docs/setup/production-environment/tools/kubeadm/control-plane-flags) - [Certificate management with kubeadm](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs) <ins> - [Find more about kubeadm set-up](/docs/reference/setup-tools/kubeadm/) </ins>
Change:
I propose adding one more best practice to “Encrypting Secret Data at Rest”: manually verify that the key used to encrypt secrets in etcd match the key that is saved to disk. Race conditions, bugs in the code, or user mistakes can overwrite with the wrong key. While the chances of this happening are small, it does happen and the consequences can be devastating. A best practice would be to verify that the keys match. Here are several such bugs: (Subscription required) As I said, these bugs are rare but will be devastating. We ran into this on a production cluster and very nearly lost the cluster. In our case, showed one key but we saw that was using a different, older key to encrypt secrets. The key in memory and the key on disk were different, and determining that required some very advanced troubleshooting. If all API servers are rebooted, the key will be lost and the secrets along with the key.
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
/label language/en
The label(s) cannot be applied. These labels are supported: . Is this label configured under or in ? <detailsIn response to : /label language/en 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
/sig security

Discussion:
``` 1. Verify the stored Secret is prefixed with `k8s:enc:aescbc:v1:` which indicates <del> the `aescbc` provider has encrypted the resulting data. </del> <ins> the `aescbc` provider has encrypted the resulting data. Confirm that the key name shown in `etcd` matches the key name specified in the `EncryptionConfiguration` mentioned above. In this example, you can see that the encryption key named `key1` is used in `etcd` and in `EncryptionConfiguration`. </ins> 1. Verify the Secret is correctly decrypted when retrieved via the API:
Change:
This is a Bug Report <!--Required Information--Problem: Below information is needed to mention in Kubernetes-objects Learn more about deployments Learn about kubectl and kubectl commands Proposed Solution: Add Below points under Kubernetes-objects Learn more about Learn about and Page to Update:
/language en /assign
/triage accepted Good idea
Fixed it here

Discussion:
## {{% heading "whatsnext" %}} <del> * Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/workloads/pods/). * Learn about [controllers](/docs/concepts/architecture/controller/) in Kubernetes. * [Using the Kubernetes API](/docs/reference/using-api/) explains some more API concepts. </del> <ins> Learn more about the following: * [Pods](https://kubernetes.io/docs/concepts/workloads/pods/) which are the most important basic Kubernetes objects. * [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) objects. * [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/) in Kubernetes. * [Kubernetes API overview](https://kubernetes.io/docs/reference/using-api/) which explains some more API concepts. * [kubectl](https://kubernetes.io/docs/reference/kubectl/) and [kubectl commands](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands). </ins>
Change:
The link is broken
Hey Could you provide the page in which you found this broken link!
/triage needs-infomation /language e
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage needs-infomation /language e 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 en /triage needs-information
The broken link is on the following page:
I think the correct link is :
/assign
the language is not , it's . /language fr
/remove-language en
/triage accepted /priority backlog
/retitle Stale link in French concept page “Secrets”

Discussion:
Les objets `secret` de Kubernetes vous permettent de stocker et de gérer des informations sensibles, telles que les mots de passe, les jetons OAuth et les clés ssh. Mettre ces informations dans un `secret` est plus sûr et plus flexible que de le mettre en dur dans la définition d'un {{< glossary_tooltip term_id="pod" >}} ou dans une {{< glossary_tooltip text="container image" term_id="image" >}}. <del> Voir [Document de conception des secrets](https://git.k8s.io/community/contributors/design-proposals/auth/secrets.md) pour plus d'informations. </del> <ins> Voir [Document de conception des secrets](https://github.com/kubernetes/design-proposals-archive/blob/main/auth/secrets.md) pour plus d'informations. </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. --We have two pages with similar aims: We should ensure that the advice in the two documents is aligned, and also make sure that the two documents link to each other. Why is this needed It's a bad idea to document multiple ways to make sure that your cluster is secure, unless those are well aligned. Comments /sig security /sig docs /language en
Relevant to
Regarding this: We can use a reference section/note/what's next section in the end of stating: -
/triage accepted
Hey I would like to work on this.
/assign

Discussion:
- [RBAC Good Practices](/docs/concepts/security/rbac-good-practices/) for further information on authorization. <ins> - [Securing a Cluster](/docs/tasks/administer-cluster/securing-a-cluster/) for information on protecting a cluster from accidental or malicious access. </ins> - [Cluster Multi-tenancy guide](/docs/concepts/security/multi-tenancy/) for configuration options recommendations and best practices on multi-tenancy. - [Blog post "A Closer Look at NSA/CISA Kubernetes Hardening Guidance"](/blog/2021/10/05/nsa-cisa-kubernetes-hardening-guidance/#building-secure-container-images)

use of that credential. Set short lifetimes on certificates and automate their rotation. Use an authentication provider that can control how long issued tokens are available and use short lifetimes where possible. If you use service-account tokens in external integrations, plan to <del> rotate those tokens frequently. For example, once the bootstrap phase is complete, a bootstrap </del> <ins> rotate those tokens frequently. For example, once the bootstrap phase is complete, a bootstrap </ins> token used for setting up nodes should be revoked or its authorization removed. ### Review third party integrations before enabling them

your backups using a well reviewed backup and encryption solution, and consider using full disk encryption where possible. <del> Kubernetes supports optional [encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) for information in the Kubernetes API. </del> <ins> Kubernetes supports optional [encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) for information in the Kubernetes API. </ins> This lets you ensure that when Kubernetes stores data for objects (for example, `Secret` or `ConfigMap` objects), the API server writes an encrypted representation of the object. That encryption means that even someone who has access to etcd backup data is unable

page for more on how to report vulnerabilities. <ins> ## What's next - [Security Checklist](/docs/concepts/security/security-checklist/) for additional information on Kubernetes security guidance. </ins>
Change:
Problem: The text on is not working, on the official website of weave, it has mentioned that the service has ended so; I believe it should point to this Check the page Installing Addons  for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text Weave Cloud account link to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, on the official website of weave, it has mentioned that the service has ended so; I believe it should point to this Check the page Installing Addons  for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text Weave Cloud account link to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I'd change: to
/triage accepted
/sig docs
/assign

Discussion:
* [Dashboard](https://github.com/kubernetes/dashboard#kubernetes-dashboard) is a dashboard web interface for Kubernetes. <del> * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s) is a tool for graphically visualizing your containers, pods, services etc. Use it in conjunction with a [Weave Cloud account](https://cloud.weave.works/) or host the UI yourself. </del> <ins> * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s) is a tool for visualizing your containers, Pods, Services and more. </ins> ## Infrastructure