{"_id":"doc-en-website-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb","title":"","text":"It is very difficult to find any links to the . This is a huge roadblock to new users trying to do anything custom with kubeadm. As a new user, I don't expect to have to read about to find information about configuring the tool. To someone who is unfamiliar with the project, that seems like more advanced documentation than I should need, and therefore not somewhere I would expect to find basic config file documentation. I also was able to find the long before I found the more user-friendly documentation, which made it seem like that was the only documentation that exists. I would expect a link to those docs to be available on the kubeadm-config page, as well as where config files are mentioned in the kubeadm-init and kubeadm-join pages.\n/language en\nit seems you have missed these two sections: and for these commands the kubeadm API is actually the most important for. linking the command line reference page to the API makes sense. but instead of linking to a particular version of the API we should link to: and let users navigate to a particular API version. this is done with the idea that can also migrate v1beta1 -v1beta2. PRs welcome. thanks /sig cluster-lifecycle /priority backlog /help wanted\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:"}
{"_id":"doc-en-website-7ed003f36ff037851e1ce066cfc8070e195e0a4b519adc19daf864395a404cf6","title":"","text":"This is a Feature Report Problem: misssing Chinese translation docs: content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX Proposed Solution: add Chinese translation docs in website Kubernetes Blog Comments /language zh /assign\nEnglish page:\n/triage accepted"}
{"_id":"doc-en-website-e57b7680d2e86886a7ad728991517aafbdee1fb54290590e43a6a80bfb87b18b","title":"","text":"The yaml file in \"Creating the Guestbook Frontend Deployment\" uses an image no more available ( ) I solved the issue by using Here is the working version I used!\nHey Can you share us a pic of the solved issue here?\n/kind bug\n/triage accepted\n/assign"}
{"_id":"doc-en-website-21e4b499f1dcceee878577892b0db6508f2070d9dba4dadf97992141af08ad83","title":"","text":"The image file download for the frontend- is currently failing. I fixed by changing it to: image: us-\nThis 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\nThis looks similar to issue(s) and I think it is a duplicate. /triage duplicate\nFixes are welcome; please visit to discuss and track that work.\nClosing this issue, resolved by PR\n/close\nClosing this issue. <detailsIn response to : /close 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"}
{"_id":"doc-en-website-94469e35708c1aae59532a41388e148ea2931abdb2f0efcc2cc194beffeffbc5","title":"","text":"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: is a missing page; however, is part of the for a localization. Proposed Solution: Localize “Hello Minikube” into Italian Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language it\n/kind bug\n/assign /lifecycle active"}
{"_id":"doc-en-website-b2649880e3cb9da273ab09ced2385f39950a405230caa5c4daefbf6f6280429c","title":"","text":"This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization\n/assign\n/unassign"}
{"_id":"doc-en-website-98e957b8dd86872fb0f88f8b1a1a5ec1759112ff76e4ccba045405e123520b42","title":"","text":"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 site '' does not list RHEL 8 or CentOS 8 as a supported os. Only RHEL 7 / CentOS 7 is listed. Both os versions released over a year ago and Google provides a lot of guides for how to install Kubernetes on CentOS 8. Please a) add RHEL 8 / CentOS 8 to the list of supported platforms or b) if there is a reason for this, explain it on the website. Why is this needed It is confusing when only an old os version ist supported without any further explanation. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\nit's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /sig cluster-lifecycle /help\nThis 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 : it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /help </details\n/triage accepted\n/kind feature /retitle Document kubeadm for RHEL 8\nI had a look at it and sent in a pull request for this. Add forward compatibility in RHEL / CentOS to the list of supported platforms.\n/assign"}
{"_id":"doc-en-website-d4fe701f4dba532aeeb3d806c7157cab718e70ea21b79afac6939020e66f1b85","title":"","text":"This is a Feature Request <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--What would you like to be The blog submission guidelines currently do not reflect the new format required for front matter, particularly the inclusion of author metadata. This discrepancy could lead to confusion and incorrect submissions from contributors who follow the outdated format. The existing guidelines need to be updated to reflect this change. Proposed Solution: Update the example front matter on the to demonstrate the correct format for including author metadata. Ensure that any related content, such as instructions or explanations surrounding the addition of author information, is also updated to reflect the new requirement. Reference of a published blog following the new format: Example of new format: Page to Update: Page URL: source: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /sig docs /area blog\n/triage accepted /help\nThis 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 : /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\n/priority backlog\n/assign"}
{"_id":"doc-en-website-418bae61b4c8db9d2545fb3261286fd392e45f1529f978dd7b9e12daa3f6d13b","title":"","text":"This is a Feature Request What would you like to be There are terms that can use the addition of a glossary tooltip to show the meaning of the said term. Some terms can add into What's next section like: ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers. Why is this needed This will enhance user experience and bring more clarity and less confusion. Comments Page to update:\n/sig docs /language en /assign\nThis issue is fixed here .\nIMO this is an acceptable change but I'd like another org member to chime in\n/triage accepted\nHi Thanks for sharing your feedback and triage accepted."}
{"_id":"doc-en-website-f95c305948d92a6a192a2a1e161abed53c1e12866b2d990979fd45331a54de7c","title":"","text":"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: Line 143, the backquote is placed at wrong position. The flag works with any operation that accepts the flag such as: Line 456~457, it needs to change hugo code for the consistency with other documents Proposed Solution: Line 143: The flag works with any operation that accepts the flag such as: etc. Line 456~457: Learn about . See . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en /assign"}
{"_id":"doc-en-website-4b301adbe566d8c6ca397149360665110e3bb31daff9b809296e535c8b83a12e","title":"","text":"Feature Gate ChecpointContainer is unrecognized by kubelet. I've tried to set up a new 1.25 cluster with kubeadm with kubelet config And it fails with I've also tried to set up another cluster without this feature gate and enable it after, and it goes the same. Kubelet is started and checkpoint api is accessible. To reproduce try to install a new cluster with kubeadm v1.25.0 and use next kubelet config Or try to enable this feature gate on already installed 1.25.0 cluster No response <details</details<detailsBare Metal </details<details</details<detailskubeadm 1.25.0 </details<detailscontainerd </details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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\nThe feature gate name is according to\n/sig node\n/kind documentation\ndoesn't list a feature gate for kubelets. has a feature gate named . I'm guessing that this is a docs bug and is incorrect (possibly other docs pages too).\nThank you Yep, using as feature gate name resolves the issue. So this is a doc bug.\n/retitle Feature gate misnamed in docs\n/transfer website\nThis issue is now and should fix it. /language en /triage accepted\n/sig docs\n/priority backlog"}
{"_id":"doc-en-website-8769fbaf5ac8ed1fcee300521f9dc6975f0ec1e4a0366a33d117a7bc15e7f9fd","title":"","text":"This is a Bug Report Problem: On the Kubernetes documentation page for Ephemeral Storage Consumption Management (), under the \"Filesystem project quota\" tab, HTML tags are being displayed incorrectly. This results in the raw HTML code being visible instead of the intended formatted content. Proposed Solution: The HTML tags should be removed from the displayed content, and the text should be properly rendered without the raw HTML markup. The content should be reviewed and corrected to ensure it is presented in a readable and user-friendly format. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--The issue affects the \"Ephemeral Storage Consumption Management\" section, specifically under \"Filesystem project quota.\" The incorrect display of HTML tags may impact user understanding and the overall readability of the documentation.\n/sig docs /assign I will raise a PR for this issue\n/language en\n/triage accepted Good to fix /help /priority backlog\nThis 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 : /triage accepted /help /priority backlog 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\nEven after removing the tags, the page is still showing raw HTML.\nThe fix here is either to revise how far things are indented (likely), or perhaps to swap between / and / shortcode markers (less likely)."}
{"_id":"doc-en-website-f2118c1b83bf7a78c158c67a3165acd3c2452aea2a25fcfac2be591e279e9c49","title":"","text":"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: Proposed Solution: Page to Update: /assign\nThis 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\nDuring my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.\n/area web-development\nI tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.\nI see, In that case I'll try to find anymore pages that might be having the same issue.\nSimilar issue is present in case study"}
{"_id":"doc-en-website-17f540fc6c21212c838b50eb4156f5964b95c89c18c753052da8688b288fe265","title":"","text":"This is a Clean Up 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 Change to call the control plane a “control plane”, not a “master”. Why is this needed Kubernetes terms have changed: &hellip;however has not yet got that memo. This work would be part of The term “master” is unhelpful when it has connotations of being paired with “slave”. Comments Note that the diagrams also need revising at the same time (if need be, this could be 2 separate PRs that merge together). /language en /wg naming /kind cleanup\n/assign\n/triage accepted"}
{"_id":"doc-en-website-ce76db007c0a91a66f52e17aec135a19b1fc010ece3748a48d11e33013c9a8b5","title":"","text":"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. --Update Japanese translation Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref. /language ja\nThis 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\nI want to work on this. Have you already started working on it? It seems that some pages linked from here are not translated yet: dockershim-removal template For now, I'm going to start working on dockershim related contents. Feel free to notify me if this conflicts with your work.\nI'll assign myself since you haven't assigned youself to this issue. Please tell me if this conflicts with you work. /assign"}
{"_id":"doc-en-website-a7d669695782b48e9880ca785375bff6d82509fd22b4de93798454f13ffb3d20","title":"","text":"This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs\n/assign\nGitHub didn't allow me to assign the following users: nilofe. Note that only with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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\nAssignment received work performed PR\n/assign"}
{"_id":"doc-en-website-6ece21b9b066d6d6b5617dce9d256853c6ea1cf4a2f9d94b34bfe9e55d29b5ab","title":"","text":"This is a Bug Report Problem: Regarding , I found the similar broken links on other pages. English pages have already been fixed. ref: pt pages also need to be fixed. Proposed Solution: Fixes broken links including {{< param \"githubbranch\" }} to master. In the case of link to , fixes to {{< param \"fullversion\" }}. ref:\nThis 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\n/assign"}
{"_id":"doc-en-website-516b27d4334505acafad63912c2292699a6dd2cf94c51042b28b88a309ded93a","title":"","text":"What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:\n/language pl\n/sig docs\n/triage accepted"}
{"_id":"doc-en-website-c39ee55ba0b4cece4bbf57571f6e8923268277ef57bdaa932a5ad6b299eb2e4f","title":"","text":"This is a Feature Request translate /docs/tasks/administer-cluster/enabling-topology-aware- into Chinese. What would you like to be /zh/docs/tasks/administer-cluster/enabling-topology-aware- /language zh /assign\nThis 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"}
{"_id":"doc-en-website-9469cd9dc186faaf8e0c82bdd9bb3057d622b1958edfc7e52fd6830186f72a18","title":"","text":"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 An announcement banner for KubeCon NA 2022 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed KubeCon NA 2022 is around the corner. It is important we start informing the community about this amazing event by displaying a banner on the Kubernetes website. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This change will need steering committee approval. I would set the banner to start on the 22nd of August and end on the 28th of October, 2022 at 18:00 CEST /priority important-soon\nThanks for filing this I think the banner should start on the 15th of October. How does that sound? /priority important-longterm /remove-priority important-soon\n15th sounds great!\n/triage accepted\n/assign"}
{"_id":"doc-en-website-d4a258f59ea8d7d5cb1391c6c0902dfdf989d3e459aae6ab5270a9cf8e2db4dd","title":"","text":"<brThere is no flag for , it seems to have already been removed from the code but not from the documentation.\n/language en /sig docs /sig security Let this be a good first issue if triaged.\n/assign\n/triage accepted"}
{"_id":"doc-en-website-133fdc21bc0c501abfff8e69eb5f14fd494c21770201ebfff4723b66b6ab21e1","title":"","text":"says: Pod's DNS Policy : The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details. “Related discussion” is a hyperlink to : Any DNS query that does not match the configured cluster domain suffix, such as \"\", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases. “Related discussion” is a hyperlink to Both hyper targets do not exist in the destination webpage (so that the browser scrolls to the right place). contains a hyperlink “See Inheriting DNS from the node” → , which as above does not exist.\nThis 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\n/assign\n/sig docs"}
{"_id":"doc-en-website-96b393461a43f397697c33a4873df7e43cc8fc9f163c1f594c785ec4b374c2ec","title":"","text":"Kindly note that you asked us to delete the service in the previous section. Please update the docs by asking to restore the service first before running this command.\nThis 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\nCould you please provide some details on the issue in the section? /triage needs-information\nPage related to the issue: /language en /sig autoscaling\n/kind bug\n/assign"}
{"_id":"doc-en-website-b5afe9625acd835bfb356724335541400d355ff53ffcc31c220548c4d068d851","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign"}
{"_id":"doc-en-website-b9b97b635b211fcadbcf336461efbdbe8ea320ad06426906ea27434f0027dd35","title":"","text":"This is a Feature Request translate content/docs/tasks/tools/install-kubectl- into Chinese What would you like to be content/zh/docs/tasks/tools/install-kubectl- /assign /language zh\n/triage accepted"}
{"_id":"doc-en-website-e289f12cb15adfa0293a068568f23c493a89351509b05ae38d842a04488feb5c","title":"","text":"This is a Feature Request Korean Localization for branch. What would you like to be Any localization contributions for Korean. Comments This issue is to notify the schedule of Korean localization to contributors. is the current work branch for Korean localization. Important dates A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch)  2~3 , main . PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /language ko /help\nThis 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 : ## In English is the current work branch for Korean localization.A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch) PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /help </details\n/milestone dev-1.26-ko.1\n/triage accepted\nOutdated Korean contents in the dev-1.26-ko.1"}
{"_id":"doc-en-website-78c363ef7795f1fa169a9476645678596b6a053c229ec3767851377cf2fae547","title":"","text":"This is a Feature Request This page blog/2022-05-20-non-graceful-node- has no Chinese version What would you like to be Translate Chinese version for blog/2022-05-20-non-graceful-node- Comments /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-811c037c136209d9690f80fd6d2f591c46daeaecb249412503292caf69b2e117","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update tasks/tools/install- to follow v1.17 of the original (Englist) text. Why is this needed content/ja/docs/tasks/tools/install- is outdated. Comments /language ja /good-first-issue File to update Original https://v1- diff between translated and v1.17 Note Currently, we use branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.\nThis request has been marked as suitable for new contributors. 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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update tasks/tools/install- to follow v1.17 of the original (Englist) text. content/ja/docs/tasks/tools/install- is outdated. /language ja /good-first-issue Currently, we use branch. Please open a PR targeting the branch. 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\n/assign\n/close\nClosing this issue. <detailsIn response to : /close 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"}
{"_id":"doc-en-website-873cbf18fce6f0ac711241a92dc449cff928b241c8763a1f00e7ded30fa9a883","title":"","text":"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 documentation recommends installing the repository signing key to . This is contrary to the recommendation in the Debian documentation : There is no keyring package in the k8s repository that would replace and (when necessary) update a keyring installed to , so the keyring should go to . Proposed Solution: Replace with in the instructions for setting up the apt package repository. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nThis is a reasonable change. We could also mention that and document how to make sure it exists. /language en /sig cluster-lifecycle /remove-kind bug It's not exactly a bug, and it's not a feature either. Let's not choose. /triage accepted /priority backlog /help\nThis 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 reasonable change. We could also mention that In releases older than Debian 12 and Ubuntu 22.04, does not exist by default. /sig cluster-lifecycle /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\nplease update the issue description to not mention updating the localized versions. Localization teams pick those changes up and will file their own issues if needed.\nI've removed the mention of localization.\nI will give a try on this. /assign\nThank you very much! :slightlysmilingface:"}
{"_id":"doc-en-website-bca665cc91ed1b12403f93d72c6bbae28e3192881674361221537e3c7066e4f0","title":"","text":"Please note: This issue is not suitable for new contributors since you need some familiarity with how Kubernetes works. The Kubernetes website currently lacks a guide on creating Windows/Linux nodes. See for more details. SIG Windows opted to remove the guide that did exist for creating Windows nodes, in PR Write a new task page about creating nodes for all operating systems. This could, potentially, be in a tabbed format as mentions in the issue referenced above. We would also need the entry reflected on the creates the Linux task page by moving / refactoring the existing \"join node\" contents from the \"create a cluster\" page: creates the Windows task page by taking the content from at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: adds tabs in the to choose between OS for joining nodes. /priority backlog /help\nThis 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 : Problem Statement: /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\n/triage accepted Thank you for filing this\n/sig cluster-lifecycle\nIf you know how to set up new nodes (with, at least, the tool): you can work on this issue. You don't need anyone's permission to open a pull request. All we ask is that you read our and that you abide by the project's code of conduct.\n/assign\nRelevant to\nAre you still working on this issue?\n/assign sending PR soon."}
{"_id":"doc-en-website-fde2c72d16cfae65992cfbd2a03512aefb2c38b934ae131fe128b569bc67ad68","title":"","text":"/priority important-longterm\nRelevant to\n/retitle Write new task pages about creating Kubernetes nodes\n/cc\nDone in PR /close\nClosing this issue. <detailsIn response to : Done in PR 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"}
{"_id":"doc-en-website-94aaf3dbfbc9855c72851da10ab4bb3ddd20fc3abec0826da275f5ae7812772c","title":"","text":"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 Kubernetes website generates a sitemap. Let's highlight specific pages using priority weighting: (and any localization that copies the priority weight) (and any localization that copies the priority weight) (and any localization that copies the priority weight) Why is this needed: Making this change helps search engines understand what pages the Kubernetes project sees as important. Comments /kind feature"}
{"_id":"doc-en-website-ceb0ec1059f0ccd568eb9a1a68aacd5f9f9282d785584e4aeb69b8cffb656ca8","title":"","text":"This is a Bug Report <!--Required Information--Problem: The page has a section. This section contains link to a Handler documentation. This link does not work: Proposed Solution: Update the link to the handler documentation on the page in the section of the page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/kind bug /language en\n/assign I'm going to fix the link to the correct one."}
{"_id":"doc-en-website-ec2c418e5483470f13f7331fec16edc13e1c7cc68dac9352edf54717a2942678","title":"","text":"Under the , this following statement is misleading because nothing about pod network plugin was discussed on that page: The text in parenthesis should be taken out to avoid confusion.\nI think it makes sense to remove the text. /help /sig cluster-lifecycle\nThis 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 : The text in parenthesis (see below) should be taken out to avoid confusion. /sig cluster-lifecycle </details\n/language en /kind bug /priority backlog Anyone is welcome to open a PR that omits the text “(see below)”.\n/triage accepted\nI'll open a PR for it."}
{"_id":"doc-en-website-ba038e9157e4feaa45266711cf3eedabe8e5585b425fd2c2da31bff0a034219d","title":"","text":"What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:\n/language zh-cn\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig-docs\n/language zh\n/triage accepted /assign"}
{"_id":"doc-en-website-eaa8bf0bfeed07bdd2b4831affb0ead19d8d687ec85a495f603a2d26df3db476","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:"}
{"_id":"doc-en-website-0e6e267395487083d8344a75b7842c2fe9c3f3fb92c9378aa8bee08fc2608a18","title":"","text":"As per title the following page contains a broken link to discovery document. See highlight here:\nPage reported in issue: /language en /kind bug\n/sig docs\nI want to work on that. /assign\nfixed this issue in PTAL!!"}
{"_id":"doc-en-website-05f33ff583b1c6f65d547cfc2a10dcebbe21f352f0aad8f30f177c5dac70f6f4","title":"","text":"Does not run under as defined in the docs. This is the fix: I think wanted me to do one work on the cheat anyways ... Just leaving this here for now."}
{"_id":"doc-en-website-312f6d8e48453f46f2962a305ce6b754e15a1bee53a3042e680100bd91e74c81","title":"","text":"I find this small bit in the scale-intro a bit confusing: and then directly under that paragraph, there is this highlighted \"Note\" section, that states: TL;DR; Paragraph instructs me to delete the \"NodePort\" service, because this sections expects a \"Loadbalancer\" service to be active. Highlighted Note instructs me to re-create the \"NodePort\" service after the \"Loadbalancer\" service was created.\nPage reported in issue (based on the issue title): /language en\n/retitle Conflicting guidance regarding Service creation in \"Scale Your App\" tutorial /kind bug\nRemoving this ambiguity will improve the tutorial's usability. /priority backlog /triage accepted\nI will try to help with this. /assign"}
{"_id":"doc-en-website-d25aca5c0dd975395d85285d7b9db9400d31923767ef7054fe5fbc0fca345fce","title":"","text":"“ DaemonSet spec.template.“ “”“”\nMind propose a fix?\n/triage accepted\n/language zh (I presume)\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh (I presume) 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\nyes,this is chinese languge,“”change to“”\n/assign"}
{"_id":"doc-en-website-01c8adc2ac16898bf48bf570538a1e170febc4ec51cd4cc37142eb861a2c928a","title":"","text":"Problem: The documentation references loading the overlay and brnetfilter kernel modules at both of these locations: Modules do not persist reboots Documentation states that they will persist across reboots. Cluster will fail pre-flight if modules are not loaded Proposed Solution: In installation prerequisites add: cat <<EOF | sudo tee /etc/modules- overlay brnetfilter EOF This is correct in the containerd installation prerequisites but appears missing from CRI-O. Modules do not appear to persist across reboots unless /etc/modules-load.d has a config reference to load at boot. In the example given at add: cat <<EOF | sudo tee /etc/modules- br_netfilter EOF\na PR with the fix is welcome. /sig node cluster-lifecycle /triage accepted\nThank you PRs submitted.\nplease close this once the PRs merge. or add in one of the PR descriptions."}
{"_id":"doc-en-website-04bf24d6c19c57a422e68873f4ae577678cca7ff3fe18bf4ae3f2e501a0fcc1f","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I want to add a hyperlink to the \"GitHub repo\". ! Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Link to be :\n/sig docs\n/language en /triage needs-information\nHi Could you please describe on which page of the documentation you are facing issue?\nThis is under the feedback section of too many pages. We have to change all of them.\nI think we need not change much here, A slight change in i18n markdown should do the trick\n/assign I'll do that\n/remove-triage needs-information\nThanks for raising the PR . Also, Please focus on those issues first which have label.\n/triage accepted /priority backlog"}
{"_id":"doc-en-website-b98ef4b4e6e3c9451b02ffea762360f84da7b4e675ab61fd8daff850a25f1326","title":"","text":"This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1\nI think this is an issue that needs to be fixed in socks shop.\nThis merged PR should resolve the issue"}
{"_id":"doc-en-website-a45cc5d20bcebe0d3bf47d7d8f4b3555277936c13286cc31a075536d193a820b","title":"","text":"Hi, apt-transport-https is a dummy package since apt 1.5, means it's not needed anymore as of Debian 10 and Ubuntu 18.04.\nThis 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\n/retitle Linux kubectl package install instructions recommend dummy package This issue is about /kind cleanup /language en The fix would be to omit mentioning , provided that we are confident that all readers are using at least Debian 10. I think the Ubuntu side of things we can take for granted. /priority awaiting-more-evidence\nWe can also rather add a piece of text, something like: sh sudo apt-get install -y apt-transport-https '``\n- would you be willing to update the issue description to incorporate the idea from ?\nI have this PR raised. I hope that helps.\n/assign\nSorry, didn't see this earlier. However, looks like already did exactly this in ."}
{"_id":"doc-en-website-33cce5a92dec257c02dfc1bfb0b4a4fa29d523caae31ec05bb23c297c9565bb1","title":"","text":"I'm not entirely sure if this is a bug, or if the documentation is just inaccurate/lacking some context, but it's at the very least a bit confusing. If you check the documentation for the well-known labels, etc., you can find the documentation for the annotation . ! However, when I try to reference a parent object with the option to without this annotation, it complains about the annotation missing: At this point my parent resource is declared as: It appears that I can set either one of the two ( or ) on the resource and will accept it; only in the latter case it appears to be copying the \"resources\" annotation to the add the \"kinds\" annotation. To phrase it another way: Setting the \"kinds\" annotation seems like the right way to go (but not what the documentation suggests), and setting the \"resources\" annotation works as well but you'll also end up with the \"kinds\" annotation afterwards. I expect the documentation and kubectl to align. Point at a resource that doesn't have the required annotations. No response <details</detailsnocloud No response No response No response No response\n/sig docs /sig cli\nThis was changed in the code by and it seems that document needs changes to reflect this. Thank you bringing this issue /triage accepted\nI think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite\nSomething went wrong or the destination repo kubernetes/wbsite does not exist. <detailsIn response to : I think this should be transferred to the k/website so that the right annotation is recorded. /transfer wbsite 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\nmy bad !! /transfer website\n/assign\nDue to an implementation error with , in k8s v1.29 release this annotation was deprecated and the same is replaced by annotation. made this changes.\nPR Raised ."}
{"_id":"doc-en-website-172f6ec4511c282b6ed7453d1e1f46ce4e38f71f6f38016e65f725797da5d596","title":"","text":"This is a Bug Report Problem: The current documentation is still referring to the non-official Kubernetes container image repository introduced starting from v1.25 () and referring to an outdated version. Proposed Solution: I can take care of the PR updating the content. Page to Update:\nThis 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"}
{"_id":"doc-en-website-b68eda4934111a88778cb92d99bdda5663d3716d629e24c68252b18141bf192c","title":"","text":"This is a Bug Report <!--Required Information--The FEATURE STATE for and is mentioned under which is wrong, As per mention in the the correct Feature state for is . Proposed Solution: Update the Feature State of Serving and Terminating from to . Page to Update: <!--Additional Information:--EndpointSliceTerminatingCondition: Enables EndpointSlice and condition fields.\n/assign\nFixed it here:\n/language en /triage accepted"}
{"_id":"doc-en-website-543dce49c6cc8577a079b662afca34ab8deb7b8443227c66d6a4c8ffc4bbe640","title":"","text":"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. --Translate into Japanese Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\nThis 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"}
{"_id":"doc-en-website-b1ea532711c3074cf1ae265c435c0b6a95ebcd3f2607b5c7873412e1dda826c4","title":"","text":"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: documents metrics for Kubernetes v1.26 but that's incorrect because at the time I'm filing this the live documentation is for Kubernetes v1.25 Proposed Solution: Revert whichever PR bumped the document too early or do a careful partial revert that only omits the v1.26 changes Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig instrumentation /language en If v1.26 gets released before we fix this, it's OK to close the issue. Consider a backport to the v1.25 docs, though.\n/assign\n/triage accepted\n/assign"}
{"_id":"doc-en-website-9a9209cce936d5073e8fb06fb3188ab120648c57dd7d6b1459c9ea881f3d085d","title":"","text":"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 StorageClass for GCE PD to and not to this . /kind document /assign /language en\nThe 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 StorageClass for GCE PD 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\nThis 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"}
{"_id":"doc-en-website-bf7923b5c22d4a3745aa368a1c99ab1f3817339fe0b7743c2f0ea88d156993cb","title":"","text":"I will localize this blog in days. To avoid possible conflicts with other contributors, this issue is opened. /assign /language zh /area blog\n/triage accepted thanks."}
{"_id":"doc-en-website-52ef25d99be0be715700ba7d7c06cd2fab825bd4620f9ea337758ad1de7bbda9","title":"","text":"This is a Feature Request What would you like to be We need to update /content/ja/docs/contribute/style/content- according to the English text, because it is outdated. Why is this needed /content/ja/docs/contribute/style/content- is outdated. In the English page, a note for localication was in . It needs to be to the Japanese page. Comments /language ja /assign\nThis 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\nRelated Issue : ,"}
{"_id":"doc-en-website-e137b3467942095722d53969564746ac8d1e05b2a4541b803909ce4bfa1bd149","title":"","text":"\" etcd \"client.cert \" etcd etcd \" \" etcd client.key etcd \"\n~ GitHub is not the right place for support requests.~ ~If you're looking for help, oyu could ask on .~ ~You can also post your question on the or the forum. There are other support venues with contributions from the wider community of Kubernetes users.~\n/triage accepted /kind bug\n/remove-kind support\nThanks\n/language zh\n/priority backlog"}
{"_id":"doc-en-website-8e046a5d937126ddf480ab6e6d32184fa95324a9857dc9ef5c2c2ff614ee417b","title":"","text":"This is a... [ ] Feature Request [x] Bug Report Problem: There is a link missing that was supposed to be in section Differences between alpha PetSets and beta StatefulSets under it in the second point StatefulSet guards against split brain which ends with following text TODO: Link to doc about fencing. Change it and add the link that is required. Proposed Solution: Add link which is missing Page to Update:\nPetSet has long been replaced by StatefuSet and StatefulSet has been GA'ed in 1.9. So we are going to remove this page to avoid further confusion."}
{"_id":"doc-en-website-9e9528247a4cdb81221b07c692cc414cd6fcc82432285f6c65747ee18510dc26","title":"","text":"apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow\nUse kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow\nprovide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information\nPage related to the issue :\n/language zh\n/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm\n/triage accepted /assign"}
{"_id":"doc-en-website-51b7f9222094a41cecffc923bd41bad811e829e4eb4da89890150c3210c660f9","title":"","text":"The basic tutorial starts at , which leads to , which leads to Since one does not know what is exactly meant with in the second site, one does also the deploy step. Because it's not clearly said \"\" or so. Then you go back to the second site, to read all through, only to do create/expose again (with little extras), only to go back to the first site and do create/expose again. Back to the first site on step 2, pretty much at the beginning it says: But I did it already 2 times in the current tutorial flow. Now I have 3 deployments, still in the basics deployment tutorial. Its like, there are 3 tutorials to do, which are the same, but also not the same. Instead of leading the user back and forth, I suggest to do one single sufficient tutorial.\nPage related to issue: /language en\n/retitle Consolidate and streamline Kubernetes basics tutorials to avoid redundancy and confusion\n/sig docs\nthe three tutorial have different purpose. What I understood the purpose of having these as three.: Yes, Its leading to back and forth of the users but I think First link showing the general functionality of the cluster's component. It Should have the link To and then link will be helpful for readers to traverse. This sequence is lacking in the page. Thats the reason why i thing its taking user back and forth several times .\nThere was a previous attempt at de-duplicating, but it probably has to be done again - after the removal of the Katacoda tutorials, which were using a hosted setup of to run through the tutorials \"inline\" with the docs\nI'll change the title to frame this as a bug. /retitle Multiple, similar Kubernetes basics tutorials that cause confusion /kind bug /triage accepted /priority important-longterm\n/lifecycle frozen\nYes You are right! +1\n/assign\nI will start working on this."}
{"_id":"doc-en-website-fd6b78a828e42fa7746594a00c3d0620f2a9e0adc0c8c892741911506d1cc7a6","title":"","text":"proxy --forward .\n/assign /language zh\npage: below yaml config comes from k8s 1.19"}
{"_id":"doc-en-website-7da1951823b8fce0969ca1050ff019147fda915dcc8b5612ee0df6730514ec72","title":"","text":"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: has a feature-state shortcode: this shortcode doesn't track when the feature went beta. Proposed Solution: Change that line to: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /help /language en /priority backlog /good-first-issue\nThis request has been marked as suitable for new contributors. 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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: has a feature-state shortcode: Change that line to: <!--Kubernetes Version:--/help /language en /priority backlog /good-first-issue </details\n/assign"}
{"_id":"doc-en-website-1bf1003a702d34addbf5e42338db731146090d1198b9e10d088f602b8b23a76f","title":"","text":"This is a clean up issue <!-- 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 changed Look at Make sure that all the version constraints in the page make sense and related to the list of Kubernetes versions that are for documentation. There is a shortcode in the page that expects a value in the page front matter. ~Replace that shortcode with English text that explains in words what versions the reader should have. (to save you having to check: you can only configure a startup probe if you have Kubernetes v1.16 or later and if you have enabled the )~ Remove that shortcode. Why is this needed doesn't clearly tell readers about the version of Kubernetes they need to be running and the feature gate(s) they might need to enable. Comments /help /kind cleanup If you're looking at this, you might also want to tackle issue\nThis 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 : This is a clean up issue <!-- See for guidance on writing an actionable issue description. --Look at (to save you having to check: you can only configure a startup probe if you have Kubernetes v1.16 or later and if you have enabled the ) doesn't clearly tell readers about the version of Kubernetes they need to be running and the feature gate(s) they might need to enable. /help /kind cleanup 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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\n/language en /lifecycle frozen\n/assign I'll probably be back with questions - where's better to post/ask, here on the issue, or in Slack?\nShould I just add the info for Startup probes?"}
{"_id":"doc-en-website-40ba88a1de3ec8b012287dcf4d5065f9b48091340455ed455411aa0ddee063e0","title":"","text":"I see that they came last with the feature gate in 1.16 onwards, checking now re: Liveness and Readiness but I guess they're earlier than the supported doc versions. Still would be nice to mention though - as a reader with maybe a bit less context I would get confused if the page title mentions 3 kinds of probes and the docs only talk about version requirements for one type of probe.\nAlso at this point for the feature flag since it went beta in 1.18 and GA in 1.20 the text would be something like: Kubernetes v1.16 and v1.17 require the to be set. Startup probes are enabled by default in Kubernetes v1.18 onwards.\nIMO it's OK to focus on documenting for v1.21, the current documentation version. If we want to backport the equivalent change to the older documentation, that's an option too. For example, if you want to revise https://v1- to explain the feature gate, that's OK (but also not a priority).\nhow do I go about editing the old version of the docs? Or is there a how-to/readme somewhere? I've submitted a PR for the current version/file with the text I suggested: Do you know btw when Liveness and Readiness probes went alpha/beta/GA? I found Liveness probes introduced but haven't found Readiness probes yet. Anyways given that it's all the way in 2014 I think it's safe to omit specific versions. I updated the text to read: lmk what you think\nSince I opened this issue, several Kubernetes releases have come out and I didn't update the issue text to clarify it. I have now.\nIf all PRs were this simple Actually it turns out some of them really are :)"}
{"_id":"doc-en-website-a3dd176f2ceffcd2f2094240c62f79dcb79daee83cfa3ef428c60ae93fd99272","title":"","text":"This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization\n/assign"}
{"_id":"doc-en-website-1929a9d1e69e84954e6108acbd3cdaaae8b37d3d7ab3ccb234964071476346b8","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\nThis 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"}
{"_id":"doc-en-website-61ab1a83c47aa3d17cd7ab97b629d6c8bd3b657be571ef7a687aa70db7cc9faf","title":"","text":"Ref: The page is centered around Docker examples and needs a rewrite in light of the Dockershim removal. /triage accepted /milestone 1.24\n/sig node\nHi, I would like to work on this but I may need a little help. When we say \"rewrite in light of the Dockershim removal\", does it just means removing the Docker references on the page ( i.e removing \"\" on this page) or something more is expected.\nThanks for taking this on. In my opinion, there are two issues to deal with here. The first is easy. Change \"Docker image\" to \"container image\". I believe the second instance refers to a legacy Docker feature called . I think it is safe to just remove that sentence.\nThankyou :) I'll make a PR by tomorrow /assign"}
{"_id":"doc-en-website-e010b0cd3dd69589f271d04d91a5f5a919058409194ce79b025b8056d76f33c3","title":"","text":"Hello team. Recently I noticed that this page: shows wrong command. Instead of it should be I believe the fix should go into this file Please review. Thank you\n/assign\n- -- -- -- -- -- -- -Also see this:\nshould this issue and its corresponding PR be closed?\nclosed his prior PR, and opened . IMO it would be good to keep this issue open until the error in K8s Docs has been resolved. /kind bug\nOkay\n/triage accepted\nThe 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]:\nShould the PR be opened in Kuberenetes/website?\n/remove-lifecycle stale"}
{"_id":"doc-en-website-d23414076776867b2ef84f4225ec2f2b7a73e43f226a0c82bf364e9b8234565d","title":"","text":"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. --In the document , it would be helpful to link to the . Why is this needed I was studying for the CKA exam, and was practicing only using the pages to search for info about CertificateSigningRequests. The doc came up readily, but the was not so easily discoverable via a search using only the search interface. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\n/triage accepted"}
{"_id":"doc-en-website-3fe28d3fe0159a80bd4bc084cd20522de06d6ed5856d6d70ebf1a58a8d15ad74","title":"","text":"As discussed in the sig-networking mailing list (), has not been fully updated since the introduction of egress filtering.\n/sig network /sig docs /kind bug (it's a bug because the doc should already have been updated) /language en /triage accepted\n/priority backlog"}
{"_id":"doc-en-website-270c364a08ab833749422b57f4a500d2a6ee56362ba70bc8a9a5f21ce043ad36","title":"","text":"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. --Currently, the documentation for starting a new localization instructs only to use the language code. However, some of the languages for which the website is currently localized also have the country code, due to Docsy specificities and because the language is written differently in the places where it is spoken. Document a general guideline of when and how a language should also contain the country code attached to it when localizing Kubernetes documentation, so new locales follow the country code standard when it makes sense to do so. Why is this needed To make sure that previous decisions made by localization teams are documented in in our page. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This is a follow-up issue to discussion on . /assign /cc\n/triage accepted"}
{"_id":"doc-en-website-b1054cdb8175638bf9b77811a7501037243009b46538c5e9657851dbd434cf38","title":"","text":"deployment does not exist\n/retitle [zh] Issue with\n/triage accepted /language zh\nIn English page, the links goes to\n/assign\nThe reason is that the Chinese version link is not synchronized with the English version. However, when I synchronized the pipeline page, I found that there was a problem with other content that needed to be synchronized , and I needed to wait for this issue to be solved before I could synchronize."}
{"_id":"doc-en-website-01b1fde9833d95cecdf46d9ee16aa96e1bcb5baccfc0b930125ea89f8a7eb229","title":"","text":"I was reading this page to learn about an addon that the installation page mentions as indispensable, i.e. the CNI addon. Strangely it isn't even mentioned on the page.\n/retitle Mention network plugins in “Kubernetes Components” It does make sense to mention network plugins as an example of an add-on. /triage accepted /language en /priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten\n/remove-lifecycle rotten\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close 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\n/reopen This is still a valid issue.\nReopened this issue. <detailsIn response to : /reopen This is still a valid issue."}
{"_id":"doc-en-website-d4d78e212460a8742b38d48669bf9b4c91ef7e135353dde62cfdb4aa00a26fda","title":"","text":"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\n/lifecycle frozen\nPage to be modified: What needs to be : A section about Network Plugins under Addons Where can you find more information about Network Plugins on our docs: Does that sound right? If yes, we can open this up for contributions as a good-first issue. I understand there are several other higher-priority issues, but I also think this is low-hanging fruit that can be completed easily.\n/assign"}
{"_id":"doc-en-website-52935f1fcecb5aa3943464fec8bd039a70dc18dee5acf0b72d3c9ea2b6e1c16b","title":"","text":"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: There is an error in the command to Install Docker CE for Ubuntu 16.04+ Proposed Solution: Update the command whicht tells to Install Docker CE for Ubuntu. The command sais: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0ubuntu-$(lsbrelease -cs) But it should be: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0~ubuntu-$(lsbrelease -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) so it should be only 1 character of ~ instead of 2 ~~ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en /assign"}
{"_id":"doc-en-website-14b16459f1d23b7c231475928a2eb387cfbc8db41aca9cf0dcfe0c7abc746d94","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: identified for Kubernetes Secrets should indicate that the secrets stored in YAML files must be protected. Proposed Solution: Add Risk Bullet: If a Base64 encoded secret is shared, it should be considered Compromised. For Example: Checking into source control, placing on a document share, or emailing All of these expose your secret to everyone who has access. Base64 is considered so secrets encoded as Base64 require additional controls to ensure only authorized users/systems can access them. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nAdd the bullet above under the following section:\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nissue solved."}
{"_id":"doc-en-website-a3758d16b7fa399d9f604841d1098660be284a4188f59a6d47f79850947f4f1b","title":"","text":"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 section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Following a series of acquisitions it looks like that article is no longer published. I couldn't find a current URL for it. Proposed Solution: Update the link to point at and mention in the text that this is archived from the original. Page to Update: Additional Information: To edit via GitHub web interface: /kind bug /priority backlog /language en /triage accepted /good-first-issue\nThis request has been marked as suitable for new contributors. 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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Update the link to point at and mention in the text that this is archived from the original. To edit via GitHub web interface: /priority backlog /language en /triage accepted /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\nI would like to take this one. This will be my first time contributing to repo, so I might take a while.\n/assign\nFixed in /close\nClosing this issue. <detailsIn response to : Fixed in /close 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"}
{"_id":"doc-en-website-938d4ebe6738dcdc068c129573edb441351cc8a60da15f38cd3c50384977bc5a","title":"","text":"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:\n/language en /sig docs /sig storage\nI would like to work on it. /assign\n/triage accepted A fixup/clarification is welcome.\n/assign\nThe issue is fixed here:"}
{"_id":"doc-en-website-1309f0fae404066cffc8f0a8c3bb5e33b429d62a46f011daeae544de5059fa0b","title":"","text":"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 Translate /docs/concepts/workloads/controllers/jobs-run-to-completion/ into Japanese. Why is this needed This page has not been translated. Comments /language ja\n/assign\n…\n8/3PR\nmasterPR\ndev-1.17-ja.3master\ndev-1.17-ja.3() dev-1.17-ja.2: dev-1.17-ja.3:"}
{"_id":"doc-en-website-7343cdc2dd805643c6047bb91f9d63cc5034f7944c9d961ba86d4b29bc3f0778","title":"","text":"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 , There are some redirection rules with wildcard(``). Expectation: Netlify redirects to Reality: gives Instead, Netlify redirects (literally) to (literally) Expectation: Netlify redirects to Reality: Netlify redirects to (with trailing slash) which is not a valid anchor URL (because of the trailing slash). Proposed Solution: File to Update:  <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nThis 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\nI would like to give this a try /assign\nhow can I test these redirect things after I made the changes? Do I have to make a PR to get the netlify link to test the things?\nAre you working on this issue?\nYa I was trying but couldn't figure out how can I test these redirects after making the changes\nThanks, I will unassign myself. Please consider commenting before. It helps others to know about the progress of issue. /unassign\n/assign\nIt was my bad.\nI think the problem is with the link itself. Here may be is the splat. Maybe that's why it's unable to redirect. If I change the redirect to something like below without the .md it works fine And for this link , the splat is get/ and hence it redirects to This can be resolve if we remove the trailing slash from this link So, where are all these links present if we want to modify the link itself?\nWhat a great research! I think so."}
{"_id":"doc-en-website-bb6fbaf53ee1be0ef0bd974e23eeb154290477ba2bf35befb144fca129cd759b","title":"","text":"To do tests, you should changes on  file, a PR, and the redirection rules on the deploy preview: https://deploy-preview-xxxxx--kubernetes-io-main- And regarding your research, I suggest to make changes like these: and test on the deploy preview of the PR you will post. I did some searching and found these: content/en/blog/posts/2016-08-00-Kubernetes-Namespaces-Use-Cases- content/en/blog/posts/2016-12-00-Statefulset-Run-Scale-Stateful-Applications-In-\nI have made the PR. Let me know if I have to do some more changes or anything"}
{"_id":"doc-en-website-bb9f2481f4e2128ee614bb281299877d3f1fb60413fe51e09c77cc6ce4cab7f7","title":"","text":"This is a Feature Request This page blog/2022/08/22/sig-storage- has no Chinese version What would you like to be Translate Chinese version for blog/2022/08/22/sig-storage-spotlight/ Comments /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-d2bee2301a81cf3027e32a7bf0c5bb12c0c352ed126afeccdb1350014635ea70","title":"","text":"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: No resource or content is getting showcased under 'Helpful Resources' heading in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--!\n/sig docs /priority backlog /language en\ncan I work on this issue? /assign\nWhat might we do to fix this issue? do you have an idea? (it's OK if you don't)\n3 kind of solutions are coming to my mind- 'Helpful resources' heading, if it's not adding any value here. some resources that are helpful to understand more about release process. Like- can also add things like this\nI think would be great fit , here we can find detailed information about the roles within the release team, processes, and other essential aspects of managing Kubernetes releases.\n/triage accepted It's definitely not right to keep the section empty does sound like an approach to me.\nUpon some inspection, We don't have a heading on any other page. Should we remove it for consistency?"}
{"_id":"doc-en-website-15814d63fd5cbb457592011a06f32b038e48eb872f096dff2b1a450e0a0a7a22","title":"","text":"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 Translate tasks/configure-pod-container/configure-pod-configmap/ into Japanese. Why is this needed This page has not been translated. Comments /language ja\n/assign\n/close\nClosing this issue. <detailsIn response to : /close 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"}
{"_id":"doc-en-website-0a806a15d038626401f262fe9716c9a66ffee5620e904178add902358f3c84d2","title":"","text":"This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments\nThis 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\n/language es /kind feature\nhey i want to work for it can you plz assign this to me!!\nThanks for participating into the Kubernetes Website project. The Spanish translation team would like to facilitate your contribution's journey, so please share your goals and/or skills in order to assist you better. We also encourage new contributors to participate in their native speaking language.\n/assign"}
{"_id":"doc-en-website-e91d11da95df52011868da5aaa31c0e31d0261d47435499f2e463b20d815cf55","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\n/triage accepted"}
{"_id":"doc-en-website-74f6221952092dbc4416e8ce292a5d837a6a656d695b7a16cdac6d0a0bc91226","title":"","text":"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. --Update some outdated descriptions in Why is this needed fix missing link to /releases update events Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\n/triage accepted"}
{"_id":"doc-en-website-8854adc3872c17951de3a22974d2e76d7ca60c090e9301bf09dd80e93ec442a3","title":"","text":"This is a Bug Report Problem: The following page writes: As discussed in issue , the use of \"privileged\" in the phrase \"create a privileged Pod\" is not standard usage and causes confusion because the pod is not created with the privileged flag (as ). This means that commands such as fail with and reading some process information may fail with . Proposed Solution: As far as what the actual clarification should be instead of the word \"privileged\", I'm not sure. I think a subject matter expert should opine on that. My guess is it should be something along the lines of: Page to Update: FYI\n/assign\n/sig cli /language en /triage accepted /remove-kind bug /priority backlog\n/unassign PR is an attempt to resolve this issue, but the PR has been closed and this issue is not resolved yet. Please take a look discussions and suggestions in the PR before self-assign. :)\n/good-first-issue /assign\nThis 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 /assign 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\nThe PR for this issue has already been raised earlier."}
{"_id":"doc-en-website-1295d136bd8ec3161f41985e9313a52f6c3fbf5336bda1cb167de4efe98fa28e","title":"","text":"\"Ander Installationsmethoden\" here should not be a link to github but to this link:\nThis 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\n/language de /kind cleanup /priority backlog Actually should either redirect to the (English) page, or it should be a stub that links there and explains that the documentation for Minikube is not localized.\n/assign"}
{"_id":"doc-en-website-89873c124323d0191b53e1c4c33b01cd8b3b0672b50709a80a3bdd2ffd9c227a","title":"","text":"In section it is said: The CRD can be either namespaced or cluster-scoped, as specified in the CRD's That text is wrong (a CRD object and the custom resource created from that CRD object are not the same). It should better say: The custom resource created from a CRD object can be either namespaced or cluster-scoped, as specified in the CRD's field\nThis 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\n/wg API expression /language en I like the new wording you suggested - would you be willing to open a pull request proposing that fix?\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /wg API expression /language en I like the new wording you suggested - would you be willing to open a pull request proposing that fix? </details\nThanks Yes, I am raising the PR. It is to be the first one I am creating against kubernetes documentation. Anything I should take care of? (thanks in advance ;-)\nI found all details in . I am then following it ;-)\n/wg api-expression\nyou've found the right guide. I hope it covers everything you need to know, but if it doesn't then please feel free to ask questions.\nI don't see any updates; so unassigning you. Please feel free to assign it, if you come back here again and are willing to work on it! Thank you /unassign /good-first-issue\nThis 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?"}
{"_id":"doc-en-website-894a3acc96d9edaedf1d9c033e3de05db54d43f333e8cab4c9aaf66da2652bca","title":"","text":"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 : I don't see any updates; so unassigning you. Please feel free to assign it, if you come back here again and are willing to work on it! Thank you /unassign 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\nSaw this good first issue with no one assigned, I could take it up /assign\nThanks a lot for putting hands on this ... and sorry a lot for not having done it myself as initially proposed (I was disconnected for some long time)."}
{"_id":"doc-en-website-b754501671935e51c3e92ac67ce3fae64a85f9bf2e5c6a04100b27ebf949c0a9","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: The port-forward command description is misleading. As a user I would expect the command to forward the complete traffic from port 6000 to 5000 locally, not only the data from both ports like the explanation in the detailed command page mentions. Proposed Solution: You could change the description to something like in the detail command description () or change the command to the version it describes. (kubectl port-forward my-pod 5000:6000 -with colon) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale"}
{"_id":"doc-en-website-81a43a8a463067b959ea1f2c8fdd7accf002b63b288f4f272aa44805eeca2c14","title":"","text":"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: After creating and scaling deployment using command kubectl create deployment cattle -- kubectl scale deployment cattle --replicas=5 When we execute below command to list pods with options -l kubectl get pods -l run=cattle O/P is No resources found in production namespace. Proposed Solution: kubectl get pods -l app=cattle Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign\ncan you / have you confirmed that this is a bug? If so, it's be good to record this issue as /kind bug\nYes, this is a bug. When was changed to , the label should have changed from to . This needs to be updated on a couple of other pages as well. /kind bug\n/priority backlog"}
{"_id":"doc-en-website-7c3c0fe8d3e20b3d4d603fc9260bf1af9682a2d1815ce891dd7df62ac627d96e","title":"","text":"In the table of of there are two descriptions missing of two tolerations kyes, one is another one is , their descriptions are missing.\nThis 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"}
{"_id":"doc-en-website-55eda147738bfa28de8c8c7f01435a14face8c304deac15e0c69d0315d277178","title":"","text":"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 description about emptyDir sizeLimit in page mentioned that: But the following code shows that if no size is specified, size limit defaults to node allocatable memory. Here is the information about my local environment and the result: Proposed Solution: Change this description to the following: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign /language en /sig storage\nCould I ask that why it says that if no size is specified, memory backed volumes are sized to 50% of the memory on a Linux host in the document? Why would memory backed volumes be sized 50% of the memory on a Linux host? Is it because the tmpfs default size=50% of physical RAM?\n/remove-sig storage /sig node\n/triage accepted\nThe memory-backed EmptyDir by default consumes a very large amount of memory (documented as , but actually ). I think it's too large for the default. In fact, one pod can occupy most of a node's memory. Is there any way to limits the size of memory-backed EmptyDir by cluster admin?\nI'm not aware of any existing mechanisms to automate the setting of for volumes. You may have to devise your own mutating webhook or wait for the mutating admission policy to land. -- my 2 cents.\nThank you for your advice! But it's problem that the whole of cluster can be down easily by few pods and the cluster admin can not control this, IMHO. I have a few idea for this problem: Set the default size of memory-backed EmptyDir fewer. e.g. 50Mi. Enable to be controlled the total size of memory-backed EmptyDir Add taint to node for that memory-backed EmptyDir can use WDYT?\nI'd like to discuss about this in . Thanks!!"}
{"_id":"doc-en-website-4992f715d2a6bc6349f396fb8c0a4ccffbb8a9a366c479abb2f0e9011d735e71","title":"","text":"Problem: Wasn't sure how to report this so selected bug as it seemed closest to what to report Running from the directory should return the diff and then close without output. But it shows the diff then outputs that the page is still in sync. Output Proposed Solution: Remove output from showing after the diff is shown when a page is not in sync. Page to Update: N/A Thanks for the script (for whoever wrote this). :]\n/triage accepted /assign"}
{"_id":"doc-en-website-1caa8836622c3c22791db12bbb5bf9ddad868b70fe84f0431f11fbf64f2553fd","title":"","text":"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. --Translate into Japanese Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign /triage accepted\n/close\nClosing this issue. <detailsIn response to : /close 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"}
{"_id":"doc-en-website-7873575eadbf9a137f215ae2f4cc9e6356299bc8b9a0640d878f7d096a059311","title":"","text":"Source IP for Services with Type=ClusterIP Packets sent to ClusterIP from within the cluster are never source NAT'd if you're running kube-proxy in iptables mode, (the default). You can query the kube-proxy mode by fetching http://localhost:/proxyMode on the node where kube-proxy is running. kubectl get nodes The output is similar to this: NAME STATUS ROLES AGE VERSION kubernetes-node-6jst Ready <none2h v1.13.0 kubernetes-node-cx31 Ready <none2h v1.13.0 kubernetes-node-jj1t Ready <none2h v1.13.0 When I use kubectl get nodes there is no nodes available except NAME STATUS ROLES AGE VERSION minikube Ready control-plane,master 38m v1.20.2\nLet's update to recommend running this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. /retitle Unclear requirements for “Using Source IP” tutorial\n/triage accepted\nThe tutorial uses a cluster as an example setup throughout the document. <sub(The text in the screenshot below is the exact section referred in the issue description)</sub! But as pointed in the description of this issue: the section doesn't clearly state that it requires a multi-node cluster to follow through the doc examples. also, it mentions to create a cluster using which usually is taken as a single node (common) control-plane/worker-node setup. As suggested by the fix/solution would be to update the section to mention that it is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. You could also update the part by linking to this article talking about .\n/help\nThis 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 : /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\n/assign"}
{"_id":"doc-en-website-8802ae96e2cad79e52a8c75260b3d7d20252cb0887c3668ec431075b9a6e3415","title":"","text":"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:--\nThis 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\nCan I work on this?\n/assign"}
{"_id":"doc-en-website-fe0215121e86683c6c44dcf5cd06fb4931ce1ecfb93de27dfdc3a40dc8cbe74f","title":"","text":"says the minimal supported CNI interface version is 0.4.0 and specification-version 1.0.0 is recommended. Neverthesless the same webpage contains two examples with .\n/assign\n/language en /triage accepted"}
{"_id":"doc-en-website-5944fabec0d2c454c2af24c5fcc78d9ea31a9ed1ba75285e7538b4e54dbd9292","title":"","text":"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: At 181 line: Link to OpenAPI v3.0 validation is broken. Yes. Most validation can be specified in the CRD using . Proposed Solution: Yes. Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation). Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en\n/assign"}
{"_id":"doc-en-website-65827779687dbe30610c6698951af880b878e745666085e00d7102564b60198a","title":"","text":"kubeadm init kubelet kubee-system kubelet-config ConfigMap kubelet kubelet kubelet API kube-system\nThis 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\nThanks for the feedback, a fix has been submitted. kube-system kubee-system"}
{"_id":"doc-en-website-12da5e83e4722a910d81545d16de448b4440d00de3ed1d95f0a8d7f5eb2b6f87","title":"","text":"This is a Bug Report Problem: Issue clarified privileges of kubectl debug node (through PR ) including \" will fail\" but in newer versions of Kubernetes 1.25 on EKS, works, although there may still be permissions issues as before. Proposed Solution: Change to \" may fail\" Page to Update:\nThis 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\nCreated PR"}
{"_id":"doc-en-website-b804243c060bd9734aa406a0e8d5a6e234ffd0b109546eb2a41c5ee081867cf8","title":"","text":"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 Minikube playground (pages such as ) launches Kubernetes v1.17 This is a shortcoming because there is drift between what we're documenting in pages like , and what actually works in the Katacoda environment. Proposed Solution: Update the Katacoda playground to use a newer version of Minikube and hence a newer Kubernetes cluster version. Page to Update: (and others that use the shortcode) Additional Information: /priority important-longterm\nThis causes:\n/triage accepted\nlike this:] [URL of the embedded terminal] view- [Content of ] I digged these pages but could not find where to update to change the minikube & K8s version:\ndo you know / can you recommend someone who can help explain where we might open a PR to update this?\nLet me find out for you. The person is away this week so expect a respond next week.\nWas there an update on this? Would be happy to help get this updated if needed.\nSorry for the delay. It was caught up with other conversations. I've raised a PR in It will now use K8s 1.20 which is the latest available in Katacoda. I haven't tested the build yet but will do once ready and will update accordingly. Update: Tested the preview build and looks to be working as expected.\nI was reffering to minkube version not kubernetes version. is it possible to re-open the this issue\nIt seems that you have already opened another PR that addresses the Minikube version of Katacoda issue."}
{"_id":"doc-en-website-fe29d03168fdbebd9f13a3305c2c5336921beff85629d6d4956dceafee405fd1","title":"","text":"found typo \"ontrolPlaneEndpoint\" in the below <img width=\"862\" alt=\"typo ontrolPlaneEndpoint\" src=\"\"There is a typo \"ontrolPlaneEndpoint\" in the localAPIEndpoint description it should be \"controlPlaneEndpoint\"\nThis 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\nPage related to issue: /language en\n/retitle Typo in auto-generated \"kubeadm Configuration (v1beta4)\" reference page\nThe mentioned reference page for \"kubeadm Configuration (v1beta4)\" is . The page is generated from the upstream source code . As the page is generated from the upstream source code, any fixes would need to be addressed there. For those interested in contributing to resolve this issue, please refer to the upstream contribution guidelines outlined at:\n/sig docs\nthis is not a typo in the code files and also in my browser it's shown as controlPlaneEndpoint, so maybe it's a rendering issue. ! cc\nbut again, there are no typos in the code / go docs. also NOTE that v1beta4 is WIP API that should not be used yet by users.\nthe in is also dropped in another place on that page, screenshot below. I'm not familiar with the autogeneration for these pages, is there some processing on the word that is dropping letters when converting from the original? Looks like in the source file its written with a capital and in the generated file its with a lower case. Not sure why it would only so it sometimes though. We should check to see if this is happening on other pages. /priority awaiting-more-evidence <img width=\"789\" alt=\"Screenshot 2024-03-27 at 9 44 26 AM\" src=\"\"\nAnother interesting observation looking at the - it appears to only happen on the v1beta4 version of the docs, not the previous versions. Looks like it was modified with .\nPut up a fix in . It looks like this wasn't from an autogeneration error and just a simple typo when the docs were updated for v1beta4."}
{"_id":"doc-en-website-3e311064a44ce9903865d9a6738f3b4320f40603b8a865930254cf5d330d3d43","title":"","text":"Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-c7057cde22f529a250aa4f00d0c1cfba0fa386a60fc44fb356256daf9634d170","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update to follow v1.19 of the original (English) text. Why is this needed is outdated. Comments /language ja /good-first-issue File to update Original diff between translated and v1.19 Note Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.\nThis request has been marked as suitable for new contributors. 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 : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update to follow v1.19 of the original (English) text. is outdated. /language ja /good-first-issue Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. 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\n/triage accepted\n/assign"}
{"_id":"doc-en-website-454b90606d414dabecdde16a9a580221c161bee000ee2237648f665f4c3206c5","title":"","text":"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 example Ingress contains rewrite annotation: But with new ingress 0.22 + capture groups must be explicit, see As result this example rewrites all paths with / - it does work for simple example, but it breaks any more complex web service! So if some body uses it as template and edits it for his own use case, can get into trouble, which are bit tricky to detect. Proposed Solution: Just delete rewrite-target annotation and ingress will work as expect by default. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nissue page: /language en\nStarting in Version 0.22.0, ingress definitions using the annotation are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group. As this is simple ingress example so no rewrite example is needed\n/triage accepted\n/assign"}
{"_id":"doc-en-website-093c2565644c4ae82e837608a8c99964afe823fe0c0626da8a5eeec3386d659c","title":"","text":"Page to be updated: What needs to be done? section needs to be updated per and For technical accuracy and/or reference, you may also check PR /sig network /help /good-first-issue cc:\nThis 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 : Page to be updated: For technical accuracy and/or reference, you may also check PR /help /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\nI am beginner and i want to contribute on this issue. Can you please guide me for this issue??\nSure, Please read and . After going through both of the resources, please could you let us know what more information would you need from our side to begin working on this issue?\ncan I work on this issue?\nHello everyone! Anyone looking at the issue - please note that you do not need my/anyone else's permission to work on an issue. If you are signing the and abide by the please feel free to pick up the issue. Additionally, please note that for every issue under sig docs it's always OK for anyone to open a pull request to work on it, including this one. If starting work, it's nevertheless polite to try to liaise with anyone who has already opened a PR or otherwise expressed an intention to work on the issue.\n/triage accepted /priority backlog\ni checked the both and . but i haven’t find any difference in actual documentation. it seems correct to me. would you like elaborate me.\nBoth those comments point to a change that is required in the Kubernetes Network Model section. The current phrasing is not technically accurate. For reference, you ALSO need to check the PR because it will give you the correct phrasing.\n/assign\n/assign\n/assign\n/assign"}
{"_id":"doc-en-website-f1ab4e5a47fe7db0d79a37fe98f69c61baebff818a52ac86265b0cfd6733b2e1","title":"","text":"This is a Feature Request What would you like to be As a PR reviewer, I'd like guidance on when to ask PR owners to squash their commits, when to do it for them, and when to never squash commits. Why is this needed Please see the following thread: Do we require PR owners to squash before merge, or do merge folk sometimes help them out by using the GitHub squash feature when we merge PRs? (edited) If there are lots of commits, maybe a history of edits towards getting the PR right: I strongly prefer a squash first if the author doesn't know how, a maintainer can offer to squash it for them and update their fork with the result if there is time pressure we could get GitHub to do a squash instead, via the label If there are two or three commits: I will ask for a squash first if I am confident the PR author knows how to if the author doesn't know how, it's fine to add the label and get Tide / GitHub to sort it out except that: if there are say three commits, and the middle commit does something obviously broken or unwise, and the last commit reverts it then this will create rebase / merge conflicts for other folks even though the “files” view in GitHub web looks OK, and the Netlify preview looks OK a maintainer should intervene as they see fit, to avoid that risk to other contributors If we're launching a localization or doing a release, and we're merging in a branch that's not from a fork: never squash Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\nFYI\nRelated topic:\nThanks. The wording doesn't have to be exactly what I suggested. /triage accepted /language en\nMaybe you can refer to this document. This document is the same for the reviewer. If the developer does not do all the suggestions of the document, the reviewer can intervene at this time.\n/assign\nis the public URL of that document\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs."}
{"_id":"doc-en-website-2606b4b16371c9f640dbb179dbc0cc060473f3ffb29876830762ea596affd34a","title":"","text":"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]:\n/remove-lifecycle stale\n/remove-lifecycle stale"}
{"_id":"doc-en-website-19c385c5c41ef805e5479cb8aed4494cb0432cc3d29ecaf52f0d9c62f79b24ba","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This doc refers to deprecated kubelet flag --api-servers Proposed Solution: Use what is preferred now (maybe kubeconfig?) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--1 <!--Additional Information:--\nyes, we do not use for kubelet start parameter, and use kubeconfig instead. do you find some outdated pages? you can list here, and we will fix it. Thanks.\nYes, page to update in the subject line Sorry I somehow missed the url field in bug report body.\n/assign"}
{"_id":"doc-en-website-6eedc0867e200d26e015dfc8e218f2d021c4f8fab44bb8a6c93517971fbdbbf6","title":"","text":"Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document:\n/area localization /language ja /good-first-issue\nThis 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 : /area localization /language ja /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\n/assign\n/unassign Shubhdeep02 PTAL , thank you\n/triage accepted\n/assign\nHi thank you for interesting in SIG-docs Japanese Localization project!! Localization requires native or equivalent Japanese language proficiency. It looks you live in Pune, India. Please confirm this before working on this issue. I believe the issues labeled with or (or those you created) are areas where you can contribute more effectively. issues labeled with : issues labeled with : Thank you\n/unassign PTAL\nHello, -san, this issue looks good as my first contribution. /assign"}
{"_id":"doc-en-website-1a1d20e97d5721bd79b1304d2e9cab4ce6148cb08f3fdb764664c3d6c46ad71b","title":"","text":"This issue is intended for contributor workshop as part of Cloud Native Day Indonesia on 7th Nov 2020. Please don't take it if you are not part of the workshop. There are several old translated pages that contain the english glossary \"file\", supposed to use Indonesian \"berkas\" as per KBBI. Please claim the task to fix them by giving comments on this Github issue. /language id Tasks to fix \"file\" -\"berkas\": [x] docs/tasks/manage-kubernetes-objects/imperative-[x] docs/tasks/manage-kubernetes-objects/declarative-[ ] docs/tasks/manage-kubernetes-objects/imperative-[ ] docs/tasks/configure-pod-container/configure-pod-[ ] docs/tasks/administer-cluster/sysctl-[ ] [x] [ ] docs/concepts/storage/storage-[ ] docs/concepts/services-networking/connect-applications-[ ] docs/concepts/services-[x] [x] docs/concepts/cluster-\n/triage accepted\n/assign\nI'm taking this page docs/tasks/manage-kubernetes-objects/imperative-\n/reopen\nReopened this issue. <detailsIn response to : /reopen 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\ni'm taking this page docs/tasks/manage-kubernetes-objects/declarative-\nmay i change this file:\nthanks feel free to raise the PR and link this issue\n/reopen\nReopened this issue. <detailsIn response to : /reopen 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\nI take this page :\nplease let me change another part. I will try to change this file\nsure just mention this issue number when you raise the pull request /reopen\nReopened this issue. <detailsIn response to : please let me change another part sure just mention this issue number when you raise the pull request 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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close."}
{"_id":"doc-en-website-e59816a103de55b89a0eb872a1448689d93039ff70b1b64a6ee71d97ccdb408a","title":"","text":"If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close 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"}
{"_id":"doc-en-website-8e53a75c4afc11fd69d4ffba3b2b0a62852ad7a6b77e4a5be50d7a197867e7e9","title":"","text":"Plan to localize recently. This issue is opened to avoid any probable conflicts. /assign /language zh\nThis 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\n/close\nClosing this issue. <detailsIn response to : /close </details"}
{"_id":"doc-en-website-7c210f1568fd95c03f05d606fceb3f8d2fc597346ae985b903b7437e29e00dc6","title":"","text":"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. --Why is this needed mentions: (it's also OK to change to the correct case) Comments /language en /kind cleanup\nThis 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\n/good-first-issue\nThis request has been marked as suitable for new contributors. 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 : /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\n/assign"}
{"_id":"doc-en-website-7b7a59f3c54d188fa9167839b39e581f978ccae7b91f9742e8f0bf7ff081ae1f","title":"","text":"Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue\nThis 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 : Note that this issue is for Japanese Speaker Original: /language ja /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\n/assign\n/triage accepted"}
{"_id":"doc-en-website-12c7bc967dae673f47483f58b1a8dae5ccc0102d6f96c095b03b957f89d43c94","title":"","text":"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 texts Code Contributor to and not to this . /kind document /assign /language en\nThe 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 It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the texts 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\nduplicate triage this issue will fix it\nHey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /triage accepted /good-first-issue /assign amolmote\nThis 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 : Hey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /good-first-issue /assign amolmote 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."}
{"_id":"doc-en-website-65805c3b4c46831aa12b6275abb82b068f920aaca77593ae96d96b27d51df95d","title":"","text":"</details\nOh, I just noticed that already assign themselves on this issue. Since it's been a bit more than two months, please tell amolmote if you are still working on this one or if it's okay that they take over."}
{"_id":"doc-en-website-9283ccf2811655d272768d0aad495b2dc1a7ca0a5470c21ab3bb03011fdc24f1","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: In the service type: LoadBalancer example configuration, having the field NodePort wouldn't work. Proposed Solution: To remove the NodePort configuration in the example config. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--"}
{"_id":"doc-en-website-db2e1de88c2eba421bca5d1846fba6b0511652c8d97eeee2eacb4e3762a96aa9","title":"","text":"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: After manually certificate renewal, , and need to be properly restarted. This should be described in (maybe) this section: , and currently not. Ref: Proposed Solution: Describe if , and need to be restarted, and also describe the proper way to restart them. Page to Update:\n/sig cluster-lifecycle /help PRs welcome /priority backlog given prints instructions that users must restart. etcd should be included in this list. there are multiple ways to restart the static pods: rename the folder for more than 20 seconds []. the containers using the container runtime CLI (setup specific). ... i'd prefer option 1. [] see\nThis 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 : /sig cluster-lifecycle /help PRs welcome given prints instructions that users must restart. temporary rename the folder for more than 20 seconds []. restart the containers using the container runtime CLI (setup specific). ... see </details\n/remove-kind bug\n/triage accepted /kind cleanup\nHi, I would like to help but I have a question first. How does changing the name of help? I mean the behavior of Kubelet is not clear for me regarding this fileFrequencyCheck and the corresponding docs do not help, too. I like to explain that in certificate renewal docs, too.\nThe better place to document details about the static pod refresh timeouts is the \"creating static pods page: If you remove a manifest file, the kubelet will find out about that every ~20sec and remove the pod from managent. If the file is then brought back the kubelet will recreate the pod acting like a restart."}
{"_id":"doc-en-website-3a8acd800bd1b27e0b78662109734a19ffafb8efd0d15ac9058ae6c1b4b7e352","title":"","text":"This is a Feature Request What would you like to be Add Hyperlink to under in concept page. Why is this needed Adding the hyperlink will helps the readers to know about RFC3339. Comments /sig docs /language en\nThis 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\n/assign /sig auth\nFixed it here:"}
{"_id":"doc-en-website-678a9d82c48ff2a40befb7e5f570170a7444aaa1a093e9468647507d2008fa6c","title":"","text":"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: There are a couple of issues with existing wording: “master” should be read “control plane” versions aren't current. Proposed Solution: Replace that text with: Page to Update: Additional Information: /language en /kind bug /wg naming\nThis 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\n/help If you're picking this up and want to be extra neat, replace those specific version numbers with shortcodes that automatically fill in based on the current release; for example:\nThis 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 : /help </details\n/assign"}
{"_id":"doc-en-website-cd4a774e70df9a9f4d39c32255bfa408507a55d16af4db4c03e7151e8d399f2d","title":"","text":"The below sentence is there towards the end of this page: (If you didn't already try creating a application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial). But the \"Hello Minkube\" tutorial link has nothing about creating any application or deploying it.\nThis is indeed a documentation bug. The v1.4 echoserver uses NGINX without Good spot, /kind bug /language en /triage accepted /priority backlog\n/assign"}
{"_id":"doc-en-website-d33bb2227a62e0443c993ee98d5c24ea84530f1d34f0eac86562f0c8984cf36d","title":"","text":"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 page has a broken link / anchor named \"Open Dashboard with URL\" in the Dashboard section. The markdown anchor named #open-dashboard-with-url cannot be resolved. Proposed Solution: This link / anchor needs to be fixed, however I am not able to understand what section it referred to in the first place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en /sig docs\nPage related to the issue:\nI think the URL should be replaced with\nLet's wait for the opinions of other members regarding the same.\nI would to like to work on this issue is the triage gets accepted.\nThanks. I checked further. Please check . Here you will find the section for the \"Open Dashboard with URL\". It seems this section was removed in later versions of this page, but the anchor/link was not removed.\nThe anchor for \"Open Dashboard with URL,\" , is now obsolete as we've integrated this content into tab layout (Launch a browser, URL copy and paste) on the.\nPull request has been submitted quite some time ago to handle this issue, and it's awaiting review and approval for merging.\nIndeed. Once is approved, it will address this issue. I do not see anyone actively working on this PR since many days. has volunteered to help. please take a look at There are some suggestions from in the PR already.\n/triage accepted"}
{"_id":"doc-en-website-de98dda00c9eb63bc8d87a618b60e63c40db9d99a24c57f2e40592265b140158","title":"","text":"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: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nThis 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\n/assign\nhi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign\n/assign\nHi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).\ni see Let me update it, thanks your work\nJust done, please review all of PRs\nThanks!\nAnd yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts."}
{"_id":"doc-en-website-3ae5ff8428957b2dba899cae924b0518a9b8537a974a667466639f6f7f6adf56","title":"","text":"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. --Translate into Japanese Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Estimated completion in a weekend. /language ja /assign\nThis 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\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues 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 as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\n/remove-lifecycle stale (PR is already under reviewing)"}
{"_id":"doc-en-website-0cdd74d1da643fec92f00dece20d870dbec66e699c2c3cf1cd341276385f0ea6","title":"","text":"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: There is typo in Following is the text with a typo. kubeadm Proposed Solution: fix \"\" to \"\" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nPage link for reported issue: Markdown of glossary entry reported to have issue: /language ja\n/area localization\n/assign\n/triage accepted"}
{"_id":"doc-en-website-fc28ab35d6ebecf83598905ffd8d07dd4c45c598bb125d0b98fdcedde608a862","title":"","text":"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 Within , add a new and brief page that has an overview of autoscaling. This means adding a new Markdown file. The new page should mention: (aim to make it clear that this is a thing that autoscales nodes, not Pods) (aim to make it clear that this is a thing that autoscales nodes, not Pods) Optionally, also mention: - marked as third party software as it's a separate project from Kubernetes - marked as third party software as it's a separate project from Kubernetes For this issue, all that's needed is a few words about each item. Later PRs could add more detail. Why is this needed our documentation on autoscaling is incomplete readers would like to have their workloads automatically sized to match demand. Comments This helps with /language en /kind feature PS. I didn't mark this as a good first issue. However, if you're looking for something to work on, and haven't already contributed to Kubernetes' docs, there may be some issues available marked as good first issues. See this . If you have already worked on an issue, please leave these for people who are new to contributing.\n/triage accepted /priority important-longterm /help\nThis 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 : /triage accepted /priority important-longterm /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\nI would like to work on this issue /assign\nShould I Make a new file inside Workloads!!"}
{"_id":"doc-en-website-4f1a166042420cb2769dc0a78753b905a19b983c6e03c569c363146a9b2cbb34","title":"","text":"In 1 PR I will be creating 2 topics like (HorizontalPodAutoscaler, VerticalPodAutoscaler) and will it be sufficient, because It will be taking 2-3 PR's!\nFor advice on how to contribute to the Kubernetes docs, please ask in #sig-docs on the Kubernetes Slack workspace. If you're not already a member of that workspace, you can visit for an invitation. Anyone is welcome to work on this issue. it's slightly unhelpful to assign an issue to yourself and also to ask questions about how to work on it; ideally, people only assign an issue once they are confident that they know how to resolve it.\nOur no cookie-licking policy means that anyone is welcome to open a PR that closes an open issue. It's still friendly to reach out to people who might already be working on the same thing. See for an explanation of the jargon.\nThanks I was just asking it. I can fix this issue!\nHey This has been pending for more than a month. So, May I go ahead and create a PR? I have a basic markdown structure for file is ready and I can add more details as needed after raising a PR.\nPRs are welcome, and because this project is open source, nobody needs permission.\nIn light of our policy on cookie licking: /unassign I think we'll make progress better without any assignee. If anyone wants to share that they have started work, feel free to open a draft pull request that mentions this issue."}
{"_id":"doc-en-website-9583575baa64d7bb27f123cbda234fb67e547bac6a663ec8f22cc69ff2e7b7af","title":"","text":"skipPhases Phases skipPhases Phases\n/triage accepted /kind bug PRs welcomed.\n/language zh\n/assign"}
{"_id":"doc-en-website-af0c6ecdcebfd8ac83a379c223c5140212f2ad09f90275631856ed43cc7e5715","title":"","text":"The concept of the has not been introduced at this point yet, but is used at multiple locations on this page. It would make sense to briefly explain what that is and link to a page that covers that topic.\n/triage accepted /language en /help I would use a here. We should also mention that StatefulSet is just an example. Related, the example manifest is incomplete. We should add a comment in YAML to make it clear that this is an excerpt.\nThis 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 : /triage accepted /language en /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\nI would like to fix this /assign\nI think is already defined .\nMy idea is to reference that definition into (see PR )"}
{"_id":"doc-en-website-c756b6ef273e9696d87b5f571280b1846d082f3d2347cb62e8775c5824c7de57","title":"","text":"This is a... [x] Bug Report Problem: There is no directory in the tar bundle. Example: Proposed Solution: Recommend people to execute in the bundle? Page to Update:"}
{"_id":"doc-en-website-c1b476c94fd37ae2e4d544472cb3a847ca57af7dca61721de133277ddb69f11e","title":"","text":"In the section, the annotation documentation gives possible values of //, but the description describes and . There's a more-detailed behaviour description in which might be useful to draw from.\nGood point, let me send a quick fix.\n/triage accepted\n/kind cleanup /language en"}
{"_id":"doc-en-website-e6fefee2f2066aacb39c18b7e4bbc2ee2fabfb8e893479273ab9851b7c526429","title":"","text":"This is a Bug Report Problem: An explanation in the Pod phase section is misleading. A pod doesn't have a state until it is configured not to be restarted. If the is not set, the pod will still be in the state. Proposed Solution: All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system, and will not be restarted. Page to Update: Kubernetes Version: v1.30.1 I'll be happy to work on it if it's accepted.\nThis 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\n/language en /sig docs\n/sig node\nso long as you're confident your understanding is correct, you don't need anyone to tell you it's OK to start work. Kubernetes is open source.\nThat’s true, thanks. /assign"}
{"_id":"doc-en-website-c2db0193d30b61bb3b2ab3e058104529ff427720129bb0d229d66b555810006d","title":"","text":"there is an useless \"\" character on\nThis 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\n/assign"}
{"_id":"doc-en-website-e02b5e261dade2f7eaeb7d43781b2d9c3987b4123eae91318eabf94fcdf51677","title":"","text":"Problem: 2021-04-16-volume-health-monitoring- does not have chinese version Proposed Solution: add chinese docs in website Comments /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-678a13a3b65e95bd91ea659eff148f84bdf02a26f57bda73bc993c22baf72c68","title":"","text":"Problem: is missing in Chinese version. See more: Proposed Solution: Add /docs/tasks/configmap-secret/ to zh version with three articles to be translated. [x] [x] Page to Update:\n/assign\n/language zh"}
{"_id":"doc-en-website-af4d70c31fbb2d60b0b95fca9ce2377cf369cc64c810dce9f7350bcf3092bed1","title":"","text":"Below command has a syntax error Add a single quotation or double quotation for the template part can make it work. PR will be sent later."}
{"_id":"doc-en-website-b9a179e0a83f9664effa81842c0881edbb0781dad2ac1e6814611a21f48d6100","title":"","text":"This is a Feature Request What would you like to be Translate docs/reference/kubernetes-api/service-resources/ingress-class- Comments Link: /language zh /kind feature /assign\n/triage accepted\n/close This is now tracked in\nClosing this issue. <detailsIn response to : /close 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"}
{"_id":"doc-en-website-c0cdb17b3904ad0e727962670e7032c5643086eb43314c8217b7d476bb25b67e","title":"","text":"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: Typo in \"Feature Gates\" page cf. Proposed Solution: In , replace with . Page to Update: ,alpha,-.%20This%20feature%20gate%20will%20never%20graduate%20to%20stable <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign\n/triage accepted\nHi could you provide an update on the progress of this issue? I'm particularly interested in knowing what the current status is and if I can carry on this issue.\n, I will submit a PR today .\n/close\nClosing this issue. <detailsIn response to : /close </details"}
{"_id":"doc-en-website-d96b5d4e5f728e99f2af0cb03daa67aa26b5bf079f7630589b1f123d22a49f94","title":"","text":"This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: I cannot find a list in the documentation of possible values for the API Server flag . Could this be provided, or instructions on how to generate the list documented? \"Full list of supported API groups can be seen in .\", but the top-level of all reference documentation does not clarify the list of possible strings. Proposed Solution: Document the available values in the Or in the Page to Update: Also here, although this is about the API, not the API Server.\nhave you been able to find the valid values for ? If you have an idea, I can help documenting it.\nthanks for the offer. I have not located current possible values and do not have knowledge of the doc generation to propose a solution that will survive versions :( My short-term need is identifying which, if any, values I need to use with versions 1.4, 1.5, 1.6 to enable features including init-containers. However, the Right Thing is to have all possible values documented for each version.\nPut me into the shame cube, I just ran into myself as well. Currently I'm trying to figure out why my 1.8 cluster doesn't have api . I think one of these values will work, I'll try these: - ( because ) -\nOK I found it. The syntax works. My understanding: api/legacy: not sure what it does api/all: option to enable disable all APIs but obviously this isn't working for maybe because it's alpha core api groups syntax: expected. named api groups syntax: unexpected, because there's no or  prefix. specifying it or enables it, disables it. the list is comma-separated I can help you incorporate these into the docs if you're interested.\nPer : : It sort of works if you treat as a placeholder (so, ). In your case: with and and no optional resource specified. This aligns with other docs, too: Certain resources and API groups are enabled by default. You can enable or disable them by setting on apiserver. accepts comma separated values. For example, to disable batch/v1, set , to enable batch/v2alpha1, set If this is the case, the flag help text and the paragraphs and the api groups pages could be clarified."}
{"_id":"doc-en-website-2f7b152238d7657a9808fe405bc984a6f856a45e9e98824d305884a786511106","title":"","text":"Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale A possible solution is to have the doc generator summarizes the API groups it identified. The generator can put that into a separate section in the API reference doc generated.\n/lifecycle frozen\nIt would be great to have it documented under which API resources lie within a specific version - something like\nIs there any default value in --runtime-config? for example,it is all work file when I config '--runtime-, ' or '--runtime-config=\"\" ' in kube-apiserver. so I was confused, how can I know which api support by default?\n/kind feature /priority backlog\nAnother gotcha with the current documentation: it mentions that takes a \"A set of key=value pairs\" - but what is the syntax for that set? Comma-separated? Space-separated? JSON map? I had to google, which led me to this issue here.\n/triage accepted\n/sig api-machinery I think"}
{"_id":"doc-en-website-526c7ae8a5989f0b4441532f28ef37c4493153e2b2e8ad6d6d8b8f3cfeb16f1c","title":"","text":"A on is broken and returning 404 page.\nThis 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"}
{"_id":"doc-en-website-7fe803de39920d6fbe6312f0ba60f33d7bd775437e01f4e514c451cddf52b8ec","title":"","text":"From the docs.. As of version 2.0, Kata Containers no longer provides an OCI compliant runtime.\nHey do you want the statement to be removed or modify?\n/sig security /kind bug\n/language en\nI'm not sure this issue is valid. For example, states: /priority awaiting-more-evidence /sig node\n/triage needs-information\n/cc\nI have investigated and found that kata version 2 did not support OCI commands or runtime , but from we can clearly see that it has again with the 3rd version of it.\nyou can look into this thread.\nI (still) don't think the website is wrong: Yep, true. As far as I know. Also true. That's fair too. With nothing to actually fix, I propose closing this issue. People who want to see that previous Kata Containers releases dropped OCI compliance should go and look on the Kata Containers website, per\nNote that the also states that \"Kata Containers 2.5.2 support the OCI Runtime Specification v1.0.0-rc5\", although releases prior to 2.5.2 did not. I am a little confused by this claim, as there have been so many issues related to kata =2.0 no longer providing an OCI compliant CLI, thus breaking docker and podman compatibility, so it seemed odd for any doc to claim \"Kata Containers is an OCI compliant runtime\", which is why I opened this issue. (side note: for a while it looked like kata may re-add the OCI CLI commands via , but a different path to providing an OCI CLI to kata is now being pursued in ) Here's my 2c: The states: So it is possible that kata implements that spec, yet does not implement the . However, according to the docs for : ... where the word \"compliance\" is a link to the spec that Kata claims to implement. That is saying that for a runtime to be tested for compliance with the runtime spec, it must implement that OCI CLI. It seems reasonable that a runtime can't claim to be OCI compliant, or even compliant with that v1.0.0-rc5 runtime spec, if it does not implement the OCI Command Line Interface which is required to test that very compliance."}
{"_id":"doc-en-website-f5924287fbdc11d1fafaac5022f9239b2e53b6e266bf4f0676482946ee424732","title":"","text":"I'm guessing that this is why Kata carefully worded their statement in the release notes: Note that it says kata \"support the\" spec, and it does not say \"is compliant with\" that spec. The k8s documentation, on the other hand, does state that \"Kata Containers is an OCI compliant runtime.\" That seems incorrect based on the reasoning above.\nThanks for the additional context. If Kata Containers doesn't comply with the OCI runtime command line interface, we can fix the wording. You are welcome to provide evidence of this I would focus on whether the latest version of Kata Containers does or doesn't implement the OCI runtime command line evidence; it's also OK to furnish any other evidence that makes it clear that the Kubernetes website is not worded correctly in this respect.\nI think the fact that is still open, for the sole purpose of re-enabling an OCI runtime command line interface for kata, is pretty solid evidence that even the latest version of Kata Containers does not implement the OCI runtime command line. It looks like that issue is actively being worked on, so hopefully an OCI interface will exist again at some point. It just doesn't right now.\n/triage accepted /remove-priority awaiting-more-evidence /remove-triage needs-information /retitle incorrectly lists Kata Containers as OCI compliant\nThe actual issue is I'm working on it. I proposed a solution that restored the command lines in the runtime, but that was rejected, so I'm now working on a wrapper that converts command line to shimv2.\nThat is correct. Part of the problem (at least in my understanding) is that many members of the team consider that supporting the shimv2 interface is sufficient to claim OCI compatibility.\nBottom line is if Kata does not support the OCI Command line then it is just available to CRI-O and Containerd since they run as daemons and implement the Kata Shim API. Podman, buildah and other tools which exec OCI Command line tools can not and will not work with Kata until kata supports an OCI Complient Command line.\nIn my ideal world someone would build a C Based library for the shim V2 which could link to crun like we have done for crun-wasm and crun-krun, along with standard support in crun.\n/assign"}
{"_id":"doc-en-website-080ab12f70035acfc3603125400ce9d8f83ce56758b6434b6de21851a07e8c94","title":"","text":"This is a Bug Report Problem: This post comes up in Chinese: This post shows with every character interspersed with \"\": Proposed Solution: Make the posts readable in English. Page to Update: I imagine this needs to be fixed in transformation; the source looks ok.\nAlso,\n/kind bug Thanks\n/priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nThe first one now seems fixed; second one is still bad.\n/remove-lifecycle stale\nseems to be working now, but is still corrupted. Note that seems to have been in a wonky state for about 2 years now This is actually a pretty good first issue, for someone patient.\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/good-first-issue\nThis request has been marked as suitable for new contributors. 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 : /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\n/assign"}
{"_id":"doc-en-website-943f86187522cc7588ca30b7db9fcea540d09545f57a5b897df9ff50a50ddd56","title":"","text":"link:\n/triage accepted\n/language zh-cn\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/language zh\n/assign"}
{"_id":"doc-en-website-780c24f3713e85779198da5fa45efee3c0691f56c4448aeabf19c26bfa587ad6","title":"","text":"This is a Bug Report Problem: The minimum and default values for were removed after solving . Proposed Solution: Put the information back: Page to Update:\n/sig docs\n/assign\n/triage accepted"}
{"_id":"doc-en-website-634ada7528254c7eac11010392fe33e0d3f37d44fc31f6dfbf79509f7b8baaa3","title":"","text":"This is a Bug Report <!--Required Information--Problem: The Feature state of is mentioned as under task, Which is not correct. In k8s v1.24.0 is graduated to . See the of k8s v1.24.0 and Also mention under the . Proposed Solution: Change the Feature State of from Kubernetes v1.20 [alpha] to Kubernetes v1.24 [beta]. Page to Update:\n/assign\nfixed it here:\nAs this is a bug report issue, I'm going to change the title to summarize what isn't right. /retitle Incorrect feature state data for kubelet credential provider Also: /language en /triage accepted /sig node\nthanks"}
{"_id":"doc-en-website-5a9931d6a5e97eac203af675d3d7638e8ea199ccaa8839d7dfe3e567caf1ce30","title":"","text":"(text removed; the credit program is long expired)\nHey John, I want to work on these diagrams in Illustrator, when I download a slide as svg and open it in Illustrator it turns out that the icons are just images. This means I can't edit them. Can you provide a complete icon set + the grid as ai, eps or svg?\nRef\nSome things we want diagrams for: All types of services: cluster, nodeport, loadbalancer, headless, imported Ingress Every controller: RC, RS, Deployment, DaemonSet, PetSet, Job, ScheduledJob Rolling update Canary deployment pattern with ConfigMap HPA ServiceAccount and Secret PVCs and PVs System architecture cc\nWould be useful to provide a way to use them. One would try to copy them but that's really \"using\" them. For example if the expected source is using Google Draw, having them in draw or something similar. May be having them in SVG for some other SVG editor. Currently there is an option, but it's rather limiting, make a copy of the slides and use Google Slides directly and finally export the current slide. It's an abuse of the tool but there isn't a lot of I/O between Slides and Draw.\nany progress on getting the SVGs publicly available somewhere? /\nThe svgs at the top of the slide deck are all that we have been able to locate. Both and I have done some digging, but haven't been able to find svg's for other assets. We are unsure of the origin of the assets, and I don't know what the original format was. Assuming the svg's do not exist what are the next steps. What are your thoughts on a visual language for our docs and diagrams?\nOK, well thank you for satisfying the due diligence of making sure there wasn't a set we should be working from. I like fresh starts! \"Symbols / Icons\" seems more appropriate than \"diagrams\" here, since really we're looking for the building blocks of a visual language we can create diagrams with, correct? Microsoft's seems like it could be at least good inspiration for this. Here's a process I could see being effective: an issue capturing what we need to include; seems like it would make sense to start with. do you want to create this? there different possible representations for concepts & post sketches."}
{"_id":"doc-en-website-1f4a95c2e57e928ee5171986ce27cb9056042620caae578d335986461e688300","title":"","text":"basic visual guidelines for designs of different icons to adhere to as we expand the library. The Slides of the Google Cloud Platform visual language seem like a reasonable starting point here. there, I have bandwidth to start designing visually consistent vectors, and anyone else that would like to is of course welcome to contribute. Thoughts?\nThanks for leading this. Your proposal sounds good to me. WDYT? In addition to the MS icon set, pointed me at the . One thing that is been on my mind is that we will be creating diagrams at several different abstraction levels, and our language will need to be consistent across them: Diagraming Concepts themselves (e.g. How do Pods, Services, Ingresses work?) Will need icons to represents the sub-atomic pieces of the Concepts e.g. for Pod: multiple containers, environment variables, ip address, volumes May also want icons to represent processes or configurations of the Concept e.g. for Pod: container restart (and restartPolicy?), liveness / readiness (and livenessChecks?), cpu limits, etc Diagraming Interactions+Relationships between Concepts e.g. for Deployment: Create, Delete Pods Will need icons to represent the actual Concepts themselves Should use imagery consistent with how we diagramed the Concepts themselves Iterations between Concepts and Tools/People/Machines Resources What are your thoughts on using color as part of the visual language? Is this generally discouraged or something useful?\nyes! Material icons design principles definitely make sense to incorporate. We may need to increase the 24dp grid size they're based on to accommodate more complex forms, but I think the basic guidance there is great. I'll try to do some research into systems that have to visually represent constituent elements as well as concepts those elements roll up to (e.g. containers / pods / clusters). Anyone have any recommendations around that? It would be nice if they somehow related to each other. Where are the above mentioned diagrams? Interspersed throughout docs? Are they centralized anywhere? as far as color: I think we should intentionally incorporate it, but look to craft visual representations that also stand alone independent from color.\nI would also like to be able to get Google UX researchers to review and give us feedback as early as possible. Does this make sense to do as part of step 2, or once we have a few icons post step 2?"}
{"_id":"doc-en-website-a8882a2e2705a43b5b64f3307022c90140883a58bef5ce7810416fe4784269d5","title":"","text":"I'd see that as valuable in the conceptualization of step 2. Once we figure out solid vizualizations for concepts with some quick accompanying sketches, creating effective symbols / icons is mostly a matter of applying sound visual design. As far as getting that conversation started, how would you recommend going about that? I can just create a new issue with of concepts needing diagrams and give people a chance to chime in?\nCreating a new issue sounds good. As part of the issue, we probably want to figure out what things we will need symbols / icons to represent, and what things will need diagrams composed of multiple symbols. What sort of things do we still need / want folks to give feedback on? The list of digram topics? How the concepts are represented in diagrams? Main concepts we want to convey? Diagrams for processes vs concepts?\nI found this issue looking for kubernetes diagram symbols and tried following through to other linked to issues to find if there was ever a set of diagram symbols bundled together for kubernetes components but could not find them. Has this happened? If so, where can they be found? Thanks!\nunfortunately there is no standardized set of symbols. This specific issue's effort sort of fizzled out and no one's yet initiated another attempt. If you have any ideas of a good approach please share! I'd love to enable more visualization of concepts.\nsee kubernetes/kubernetes.\nOutcome of kubernetes/kubernetes"}
{"_id":"doc-en-website-f711f88ebcadc5ddde319b9097b37083f296b307282d2d5e4546fe66b9432509","title":"","text":"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: describes the API List Chunking feature. However, this is a beta feature. Proposed Solution: Warn readers that this feature is not yet stable, using a Hugo shortcode. You can look up when the feature went beta from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 /sig api-machinery\n/assign"}
{"_id":"doc-en-website-b2e2d462049ee8351e625ceb7f62baff5f71ebaa27f99d4a63c78fd85b5c850e","title":"","text":"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: Document the EndpointSlice controller ignores nodes with the following labels or Proposed Solution: Document labels Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind cleanup /language en\n/assign\n/sig network /triage accepted"}
{"_id":"doc-en-website-bfad54ccef557e38bd0aaaab53cba5d0083d999a3b0f96db7fd0d5766db7ef63","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: ref. Japanese Localization document: /area localization /language ja /assign\nThis 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"}
{"_id":"doc-en-website-d2510bdf342d079c3a9f781fdb4c8578dd1af6882580fa7344e3854b1d1d8231","title":"","text":"This is a Bug Report Problem: Using as an example, Note blocks that start with a bullet appear malformed, same outcome in both Chrome and Safari, note the dot over the e characters and incorrect indentation - <img width=\"723\" alt=\"image\" src=\"\"Proposed Solution: Let's discuss further, possibly, maybe this can be fixed via hugo, otherwise we could investigate an update to all affected pages. Page to Update: We should update all notes that meet this criteria, investigate after a proposed solution is agreed.\n/area web-development\nIt seems that our recent update to align with Docsy-style callouts in may have unintentionally caused this issue. There's definitely room for improvement here, and we should address this to ensure the content is displayed properly. /priority backlog /triage accepted\nOops. I think we can address this with a CSS fix; for example, not making the “note” text an inline block when the parent contains either or (using and selectors). For a simple fix, make the “Note:” text never be an inline block.\ni would like to try\n/assign"}
{"_id":"doc-en-website-3265b4ebe9712745dd88948a1a64426c60451272226100f635d07334e54dc6ed","title":"","text":"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 , under redirects to a topic that has been removed in release 1.30 by this PR Therefore, the hyperlink no longer exists. was replaced with Proposed Solution: Replace this line in with this line and adding a hyperlink for Specifying Apparmor Confinement: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--If the suggested solution is okay. I can raise a PR for it.\n/assign /sig node /language en /sig docs\n/triage accepted /priority backlog"}
{"_id":"doc-en-website-170f2c6397af29df24c6ac37c67e211b59f329e6aafc98b28b3069f632e11855","title":"","text":"This is a Feature Request webpage /zh/docs/tasks/debug-application-cluster/debug-running-pod/ is not available in Chinese version, add it. What would you like to be add file /content/zh/docs/tasks/debug-application-cluster/debug-running-, and translate the file from its English version to Chinese Why is this needed synchronize Chinese with English version\n/language zh /assign"}
{"_id":"doc-en-website-2aa75a8d54954ef53b5b273f48a2bf3b6ed929f3e02621824fd2da1f5a9615ce","title":"","text":"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: Using chrome (120.0.6099.129 (Official Build) (x86_64)) on macOS (12.7.1 (21G920)) and hitting the link from the , I hit the documentation for Kubernetes 1.29 and I can only see the navigation with the list of objects. <img width=\"1595\" alt=\"image\" src=\"\"I have observed the same problem on safari ( 17.1.2 (.2.9.11.12, )): <img width=\"1587\" alt=\"image\" src=\"\"And Firefox (121.0 (64-bit)): <img width=\"1266\" alt=\"image\" src=\"\"Proposed Solution: Get the content back as in the : <img width=\"1585\" alt=\"image\" src=\"\"Page to Update:\n/retitle One-page API reference missing for Kubernetes v1.29\nThe API reference for v1.29 was successfully generated in PR , as evidenced by the verified information in the . It appears that we're encountering a rendering glitch.\nUpon further investigation, it seems that the page data isn't rendering correctly in dark mode (sort of). I switched my device/browser theme to light mode, and the page info became visible (Refer below screenshot). It seems like there might be some missing CSS and scripts causing this issue. <img width=\"1278\" alt=\"api-refence-light-mode\" src=\"\"\nThis is definitely something we should address. (cc: /triage accepted\n/retitle Content of 'One-page API Reference for v1.29' not rendering properly in dark mode\n/assign\nThe original description of the issue is proper and correct, I don't know why you are so akin to change these issue descriptions. I'm raising this question because when an issue title is changed, my email client won't treat the issues as the same one. The \"conversation\" mode no longer works. I'm receiving emails for every comment as a separate email. It is not a big deal but it is really annoying."}
{"_id":"doc-en-website-18227530cc41075fccb29cff1b218ee62f6b3ef0ff3660f7f4b8aa042406c575","title":"","text":"Ah, does the API reference have special support for dark mode, separate from Assuming that this is the case: /kind bug /area web-development A short-term fix would be to drop the dark mode support, pending an implementation that works right. Let's see if sorts it out.\nFor what it's worth, I agree with the title change in The bug was about dark mode rendering and not that the reference was completely missing."}
{"_id":"doc-en-website-b5d18cb4df53aeede3d6c93bdbc2a1539791d063651785d9a7c8a7bb7f2cef7c","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This reads a little unclear: kube-scheduler kube-scheduler watches newly created pods that have no node assigned, and selects a node for them to run on. Proposed Solution: kube-scheduler kube-scheduler watches for newly created pods that are not assigned to any node, and selects a node for them to run on. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign"}