{"_id":"q-en-website-9b25ceb573fb997558055c51543fb012d5cbc487c3dd99fed9b58187754376d1","text":"When creating your cluster: \"Leave all the options default, and you should get a Kubernetes cluster with three nodes, ready to receive your container image.\" ..should read: \"Set the name to 'hello-world', leaving all other options default. You should get a Kubernetes cluster with three nodes, ready to receive your container image.\"\nPR submitted:\ncc\nshould be closed now"}
{"_id":"q-en-website-b5606244a07922ceff881835939a803b2477a69d85d0c85200e0583f683d2499","text":"NodeJS 0.10 is going into security-only release mode very soon. The first version of 0.10 was released in March 2013, so it's over 3 years old. It would be great if we could update the tutorial/dockerfile to list the latest (or at least a newer) nodejs version.\nResolved by, thanks to"}
{"_id":"q-en-website-fb434cfff9f10c632cd4e9d8ca66f0e52a2edeed826c1908a3288710b8be5a58","text":"I wish /docs/user-guide/horizontal-pod-autoscaling/walkthrough/ actually contained the information, or at least a link to autoscaling by custom application logic (as referred to by the first sentence in the article - . The second half of this article seems like the correct target link -\nFixed. Thanks."}
{"_id":"q-en-website-ff47120f5ef0aa098e4e7382085205bde4f0c0f768f8ae73a601cd727875b707","text":"I wish /docs/admin/dns/ linked correctly to the federation guide, at"}
{"_id":"q-en-website-b6299c808f7540f36b98546e3f1177b482f420d0a7f5c2094815bfc11e3d63f1","text":"This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: Section \"Cron Job Limitations\" in is confusing to users. It says: The about is confusing to users. Proposed Solution: A more specific description would be as follows: If startingDeadlineSeconds is set to a large value or unset (the default) and if concurrencyPolicy is AllowConcurrent, then your jobs will always run at least once. Jobs may fail to run if the Cron Controller (part of the kubernetes master) is not running or broken for a span of time from before the start time of the job to start time plus , or if the span covers multiple start times and does not allow concurrency. For example, if you say that your cron job has to start at exactly 08:30:00 and startingDeadlineSeconds is 10, and the , and your cron controller happens to be down from 08:29:00 to 08:42:00, then the job will not start. Set a longer if starting later is better than not starting at all. Page to Update:\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":"q-en-website-02e53d4b80a7667a87625b24f106fc9d01f42ae8e77816ddd3c1d2e613c072e4","text":"It's a nice description of what hooks are and options the user has. But where to configure it? How about an example?\nyou can find examples of container lifecycle hooks here: I am afraid it is currently a bit hard to find. Thanks for reporting. We should add a link to this /task from the /concept.\nThat's awesome, thanks a lot!"}
{"_id":"q-en-website-353c953f5ebf00be78ea8f37c6341fa7495b3c951b29340896345ca2b0720b08","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: There is a warning during the Netlify preview build process: Looks like liquid is trying to parse in the line: Proposed Solution: Find out how to escape in a code block for Liquid. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Kubernetes 1.6 <!--Additional Information:--"}
{"_id":"q-en-website-0952314ffbea8d6c97a0f73466967c0bbc6e10292ae0028b537642fce6b1daad","text":"This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This link: redirects to this page: The link is found here: Proposed Solution: Fix the redirect for /docs/user-guide/working-with-resources Page to Update: Redirect for\nYeah, it's confusing. Why it's P3? How hard to fix it? How I can help?\nI know what the problem is and will submit a PR shortly. None of the pages in the /cn directory should have the directive at the top of the page. For example, currently, /cn/docs/tutorials/object-management-kubectl/object- has this set at the top of the page:\nWow! Thank you!!\nOk, nothing should be redirected to the /cn pages anymore. Cheers"}
{"_id":"q-en-website-4d6464ba67830c72bd13ff5e9a358dfdd6e926542d515b56f50ab23e017e00b2","text":"<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The above wiki and mentions an invalid URL Browsing to results in URL 404 Error Proposed Solution: Update url on the wiki and in output Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nthanks Looks like we need a redirect for that gets to the right end destintation (which I think is has moved to )"}
{"_id":"q-en-website-c0222cc6fed2377be52cfdc95aa0a1475e6a398000cfd314e6d148fb0f8cbe55","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: kubectl get nodes seems to show the master is NotReady when a node is with the same hostname Proposed Solution: Make a unique hostname a requirement for every node just like MAC address and product_uuid. Possible the code should reflect that too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.8.1 <!--Additional Information:--\nThanks for the report If you think the code should be doing something different, please open a bug report for that code - either at , or in this case perhaps at I'll keep this report open to reflect the need in the documentation."}
{"_id":"q-en-website-a5644fc9eaf6e5ad289e7bfe909107057dcacba083dd3351ec20ce250784d5da","text":"[ ] Feature Request [x] Bug Report /kind bug Flex volume docs still stay the feature is Alpha. We made it GA in Kube 1.8 time frame. We have to update the docs to reflect it. /sig storage Kubernetes version: 1.9 or master\nCreate new docs issue\nFixed in"}
{"_id":"q-en-website-0f1f4ec5eda92259bf9133ce0875e3c7ed8ad0a011ee82d9e610a288270ce38c","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 Move to be in the same section as the content that currently exists within (that section is titled “Extend Kubernetes”). Consider moving to as well. Redirects will be helpful too. Why is this needed is showing the reader how to extend Kubernetes (by implementing a custom scheduler) more than it is explaining how to administer a cluster. Comments\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\n/remove-lifecycle stale\n/sig scheduling\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-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/assign\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /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":"q-en-website-748841542fe8c4c6d5305864e4281254dbcd1418e0047c3d47a9bba081d123a2","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--Reference: The spec.containers[] is converted to its millicore value and multiplied by 100. The resulting value is the total amount of CPU time that a container can use every 100ms. A container cannot use more than its share of CPU time during this interval. Problem: I'm a little confused about the description about 'millicore value'. If the is configured as ‘100m’, how long can it use every 100ms? According to the referenced text, it should be 'its millicore value', that is 100, multiplied by 100 to get a value of 10000ms. This is much longer than 100ms. Page to Update:\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\nThis is not fixed yet.\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-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /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\nYou can't reopen an issue/PR unless you authored it or you are a collaborator. <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"}
{"_id":"q-en-website-8724338b1f99e40bc801f3b510216454a2b1f5b03f8eeb6e39aa9f3ba97abe84","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 extra . ! Proposed Solution: remove and regenerate document. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--"}
{"_id":"q-en-website-e04d2c87575b68bef837611913cd48be11cbc55221e7e290c75432988a071a1c","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: lists the EndpointSlice concept before Service. Although the , the current page about Service should come before the page about EndpointSlice, which is still beta and only partly activated by default. Proposed Solution: Revise the EndpointSlice page to have a that is higher than the Service page. See for the line that needs tweaking. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 Additional Information: /language en\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: lists the EndpointSlice concept before Service. Revise the EndpointSlice page to have a that is higher than the Service page. See for the line that needs tweaking. Kubernetes Version: v1.17 /language en /good-first-issue </details\nThis is a good first issue; if you've already had a pull request or two merged, I recommend leaving this one so that it's saved for a new contributor.\nThanks for triaging with an eye for new contributors!\nI'd like to work on this issue, as a new contributor.\nit'll be great to have your input Have you already seen\nYes, I've read the docs and signed CLA already.\nRetract my application as it seem I haven't meet some of requirements described in\nIf it is okay, I would like to take this up. Thanks.\n/assign\nThis also looks like maybe it affects the rendering of the main Kubernetes web page at also, actually -- under Features, EndpointSlices is listed before Service Topology (in fact EndpointSlices is the very first feature listed).\nThanks for pointing that out I will put that list in the same sequence as documentation. I am planning to work on it this weekend.\nare you working on this issue? if not I would like to take this. Please let me know\nI planned to work on it during my break but couldn't find much time to tend to it. Please feel free to take this up. I will circle back to this issue on March 1 when I have some capacity to spare. Thanks.\n/assign\nHi, I am back from my holidays. Are you still working on this issue or would you like me to take it forward? Thanks.\nYou please take it, Sent from my iPhone\n/priority important-longterm\nI noticed you were just working in this area - would you like to pick this issue up as well?\nSure. :) Tim Bannister <:\n/assign Prasad Katti <: working in this area - would you like to pick this issue up as well? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or unsubscribe"}
{"_id":"q-en-website-514fa23898dc5091c3e6e9db45fee3707e2ef55a0c97255eb12dcff048fd6e45","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: Wrong output for LoadBalancer service type exemple. Proposed Solution: This is the given output from the doc. type is wrong for this service. It should be . An appropriate output would be: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nI am working on this issue.\n/assign\nFixed. /close\nClosing this issue. <detailsIn response to : Fixed. /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":"q-en-website-39cc93b9468f7cae1c6f03d70144707d1a203fe4014312b39214177f82861a6a","text":"reference docs render with (single UTF8 8211) instead of (ANSI 45) even if a generated reference page contains the regular double dash . see vs this makes users copy-pasting command line flags insert bogus flags in their setup. request: please make the website render the double dash . /kind bug /sig docs /cc\nreported here on slack:\n/priority important-longterm (or higher)\nThanks for filing the issue\nEmm. Hugo is again doing some conversion behind the scene. If you check the reference page we generated: you can see that the is in the source. Hugo converted into , for unknown reason.\nI suspect we will find pages that have relied on the smart dashes behavior. For a different, lasting fix, maybe we change the docs generation to write HTML/Markdown that looks like: or maybe we switch to a newer Hugo that implements more of CommonMark and that lets us re-enable smart dashes without breaking reference docs?\nWow thanks for implementing the change so quickly after the report <3 you guys rock!!"}
{"_id":"q-en-website-7c686c6c7e9e52d9e2a1fa8203151d2bb124d7e31251a8975e1295f5404ee32d","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\nI've already translated this page, but currently, the branch is not created so I haven't created the PR yet. I'm going to create a new PR for this page after a new branch is created. The commit I've translated is here: Japanese: PRPR\nmasterPR\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":"q-en-website-f7421623b1fce974e530bdc7792ba0cac498891dde15e3c34a20124c390cf216","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 Spanish Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language es /kind bug\n/assign"}
{"_id":"q-en-website-811c037c136209d9690f80fd6d2f591c46daeaecb249412503292caf69b2e117","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":"q-en-website-4c8755930b90be102893ee2b1b36b5b3d888ef40d211cca4bc9c6ffa7970d70c","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: section () contains an outdated claim ( in 2016 in commit ) that compromise of a node/kubelet gives an attacker access to all secrets in the cluster. Specifically: My understanding is that modern clusters by default are configured to provide node/kubelet access only to secrets for Pods scheduled on that node/kubelet. . Tested on Amazon EKS 1.15. Proposed Solution: Edit to either entirely remove the above quote, or, if the security improvement is not enabled by default, provide information about how to enable it. Page to Update:\n/kind bug /priority important-longterm Working on this also addresses from the style guide.\n/language en\nThanks for reporting this\nThe outdated statement appears to be there in as well. I suspect it might be there in more languages.\nThat's OK - the localization teams have their own processes for picking up changes that are fixed in the upstream English localization.\n/assign\nI notice also that says: (my emphasis)\n/sig auth\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-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle rotten\nAnyone who'd like to, please feel free to open a pull request with an update.\n/kind documentation\n/sig security\n/triage accepted"}
{"_id":"q-en-website-69dd19060a8fcdbb148c3217193b9a7b9fb47722f9f95d64c928e6c229babd9e","text":"This is a Feature Request What would you like to be Translate docs/reference/glossary/secret into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign"}
{"_id":"q-en-website-c17b01e72e68b9853de4796f8ba797c75ae168fcd0674d552f5b182bf79b9cc2","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 used to verify the relationship between the version of kube-proxy and kube-apiserver is problematic Proposed Solution: The version of kube-proxy must be less than or euqual to the version of kube-apiserver, so if the version of kube-proxy is 1.18, the version of kube-apiserver can be 1.18, 1.19 and 1.20. The setence should be \"kube-apiserver version must be between 1.18 and 1.20, inclusive\". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind bug /language en\nthanks for finding this problem. PRs welcome! /help /good-first-issue /sig docs architecture /priority important-longterm\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 : thanks for finding this problem. PRs welcome! /good-first-issue /sig docs architecture /priority important-longterm </details\n/assign"}
{"_id":"q-en-website-f82937476a2414ef947398f969ab3b39c305c5994219e4147bf0268f7778d5c6","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'd like to sort \"\", common words alphabetically in Japanese localization guide. Why is this needed It'll be easier to find a word in the list. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign"}
{"_id":"q-en-website-6e25462f15ff8676a0e1e7dbfc8057901029b5e6bebc601a1b2337a35882b66f","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 a typo in filename of roles-and- file. Proposed Solution: Rename roles-and- instead of roles-and- Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko\n/assign"}
{"_id":"q-en-website-9d629a994da68479c36435326cf35f4ec25e6dc8c039286ac4866164faabcae6","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: Mismatch between descriptive node names ! Proposed Solution: Change node name from 'noee2' to 'node2' Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language ko /assign"}
{"_id":"q-en-website-c6a12598b6c0783de570b6c6cac7badfebe0aa199e6a0be83eef260de551b077","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: Content references \"GKE\" which is a Google product. Proposed Solution: Rewrite the sentence to pertain to Kubernetes, not Google. Page to Update:\n/kind bug /priority important-longterm /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 : /kind bug /priority important-longterm /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\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /kind bug /priority important-longterm /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\nAlso if this is the I think it is... hi! long time no see! :)\n/assign\nHi I think you're talking about the following sentence: Should we change it to \"On a Kubernetes deployment, the client credentials provided to the kubelet are in the form of a client certificate.\" ? Any better suggestions to rephrase it? Thank you.\n- As long as that statement is technically accurate for Kubernetes."}
{"_id":"q-en-website-fd4be5dd8b868f5fbd4a1561e9e859e0c487d87faebb810d87cc3f76e83f65ae","text":"This is a cleanup 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 Remove the page Why is this needed The site map at does not work as expected. There are no dropdowns. This page is not linked from other pages. Also: since the the navigation provided by the theme seems good enough. There is also a to help crawlers. Comments /kind cleanup /language en /priority backlog\nHey , I want to work on this issue. Can you tell me how do I have to delete this page?\nshould help you to get going If you're working in the web interface, there's a delete icon top-right of the main page content in Feel free to ask more questions! /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 : should help you to get going /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 have forked the project. Do I have to run the project to get that delete icon?\nif you look at I suspect you'll see that icon; here's a screenshot: !\noh yeah, i saw that. I thought maybe I have to delete it from a running project. Let me open a pull request.\nkindly check my PR"}
{"_id":"q-en-website-9c64e1a40343bcedcb15f00f273d6339852e65ee6e4ce3d24e924bce91da1cbd","text":"At the bottom of the page, in the section, the following links lead to a 404 page not found: RuntimeClass Design, link RuntimeClass Scheduling Design, link"}
{"_id":"q-en-website-ff1ee7c909de67651603085bc9ace5b18366a68437082df83eb56242a67967d5","text":"Clicking the \"Containers\" hyperlink leads to the \"What is Kubernetes?\" page. I'm not sure if this was intended. There is some explanation of containerized deployments (after a scroll) but I wonder if it makes more sense to direct them to the \"Containers\" term page. As a user learning in the docs, it was a bit confusing. Pods hyperlink re-direction shown below, from this <img width=\"901\" alt=\"Screen Shot 2020-10-09 at 1 58 28 PM\" src=\"https://user-\"Leads to the below <img width=\"843\" alt=\"Screen Shot 2020-10-09 at 1 58 54 PM\" src=\"https://user-\"Perhaps redirecting to the page defining containers in the concepts may be better, though I believe more definition could be there.\n/triage accepted\n/kind bug /language en /priority backlog /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 : /kind bug /language en /priority backlog /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nHi I'd like to work on this\nAwesome! I think you can assign it yourself by running the \"assign\" command. Context here: and example here:\n/assign"}
{"_id":"q-en-website-7fa2d81aaa2a7da2c3670e629d1d5c9aa27e4e399c5bfddc3438051de5904297","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: Clicking the \"\" hyperlink leads to the 404 page. <img width=\"876\" alt=\"WeChatc2b6a16c89afc8d1086c8c92a0a7f437\" src=\"https://user-\"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--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\n/language zh"}
{"_id":"q-en-website-99753022dfebf9d2675bda906258b2c03fed778eac641e22ae206044b9243163","text":"This is a Bug Report Problem: is mis-configured for markdown files, and is stripping white space at the end of lines. Markdown uses these spaces for formatting in some casees. Currently, if the .editorconfig file is being used (via plugin or whatnot), then these formatting cues can be removed on save. Proposed Solution: add the following after the section in the file. dotfile to Update: .editorconfig Test environment MacOS 10.14.6 Both of: VS Code using neovim using\nGood spot /kind bug /triage accepted /priority backlog\n/assign"}
{"_id":"q-en-website-b474e13ee38ad8ea4cc913c234937a42c750b8c27774c67ffdb114ac3af9f2f2","text":"Translate \"Server-Side Apply\" into chinese. /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/assign"}
{"_id":"q-en-website-48e6ee45bb31890ccc47750b8c3f8446f02307146924c8342b2b8eec439f1c5c","text":"Translate tutorials/configuration/configure-java-microservice/ into Chinese /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":"q-en-website-2ff56e343081f5fe03379f8bb7270fe86f6bc1243b7a130f5e125a53b2856840","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 Update the to use the  shortcode that is built in to Hugo. Why is this needed Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. Comments /kind cleanup /help /language en If you make this change, and check that the videos still render. Related to\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 request <!-- See for guidance on writing an actionable issue description. --Update the to use the  shortcode that is built in to Hugo. Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. /kind cleanup /help /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\n/assign\nThanks"}
{"_id":"q-en-website-e2c02c57260836e42ba79813059f27ea0428bb656297408b5674454e4e76341b","text":"<!-- 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: [zh] Need trans for <!--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/language zh\n/assign"}
{"_id":"q-en-website-34f37d6f94778872134c41bb68d6f0e64cdcef7bb83ab0ce96f15af4f7727d36","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: 1 file changed, 1656 insertions(+), 2119 deletions(-) for Korean is outdated. Proposed Solution: Update according to 1 file changed, 1656 insertions(+), 2119 deletions(-) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko\n/assign\nParent issue :\n/milestone dev-1.20-ko.1\n/triage accepted"}
{"_id":"q-en-website-f4cff827425640ce2fae3875dfdd19e2f84a38a6cef201e9b8038bea3e4444aa","text":"the file labels and annotations should be in the directory /etc/podinfo not /etc !\nHi What's the URL of the web page that isn't right? /triage needs-information\n/triage accepted\n/assign"}
{"_id":"q-en-website-4698dee2d4869bac745d526a4c1aa704b229878b41d710bd549713fbc4bc0acc","text":"The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.\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 zh\nthis is fixed here"}
{"_id":"q-en-website-5c19e406eac1a567fe6299411b6ec0da2f295b0850ac886a861ed1dd95e0a56c","text":"This is a Bug Report The issue is outlined in:\n/triage accepted\n/kind cleanup\nHi Thanks for opening a PR to fix this issue! /assign"}
{"_id":"q-en-website-edbf70a539c82a04bc1142e9836b65c4afedc27613330a63c617df30bcea53ff","text":"This is a Bug Report It's not a bug, just an outdated doc thing. Problem: The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to in . But the docs still show that they are in beta state at and . Proposed Solution: the description from the two plug-ins. the descriptions of the two plug-ins if they need an update too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nI'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it. /assign\n/triage accepted"}
{"_id":"q-en-website-7c3c0fe8d3e20b3d4d603fc9260bf1af9682a2d1815ce891dd7df62ac627d96e","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":"q-en-website-9c4c2e88564e2730d29d23ac0e608268825236d661b061693a40ea33e86b7fc8","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 For the pages: the part before is sometimes a plural and sometimes not. We should make this consistent. Why is this needed When we use language inconsistently, that language becomes harder for (some) localization teams to translate well. Additionally, readers might see the different pluralization and wonder (perhaps even believe) that it is significant, given the authority attached to the website where it appears. Comments /language en /kind cleanup\n/triage accepted\nyou might want to know about this issue - I am sure you would have some tips for a person picking it up\nThis change needs to happen in the generator, ? The idea is to make the resource type or category singular?\nThat's the approach I'd take."}
{"_id":"q-en-website-430c4150e04b1ae80753dabcae75d833f84f0b8906ee0b9aa61154d3aeb5be54","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: \"FrameworkHandle\" link is broken. Proposed Solution: The link should be ( ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /triage accepted\n/assign"}
{"_id":"q-en-website-3fbc7d9f4910fcf12b7613f0b105c7475fa612fbb9a22d2d491dfb434fd85f6d","text":"Link broken or pointing to a wrong link. Under section: Programmatic access to the API. The link provided in the below line seems to be broken to wrong.\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 think this report is about the page can you paste in the text (or HTML source) of the broken hyperlink /triage needs-information"}
{"_id":"q-en-website-5e0f9e73e0d61245e6ab87949aae61fd8a9c30941c950655ea067da0029d4587","text":"По ссылке получаю страницу \"404\"\n/language ru /kind bug\nСтраница на текущий момент не вся актуальна. Используйте английскую версию.\n/triage accepted"}
{"_id":"q-en-website-0db9979c6fcc22782a878360b6115cc1724e6cd915a1af63f8ee319bc5ea3c8b","text":"Problem: Google search for \"kubernetes secrets v2\" returns: ! (notice the URL subdomains) Proposed Solution: I need to do some more research but a few things come to mind: is in and set in the couple repos I checked. is set in . I believe this is for non-prod sites that are running, however I believe even the old released sites are considered \"production\" That is assuming robots tag is the culprit. What's also strange is that the above robot config is set in but doesn't appear in the search results I also think looking at might help. It's possible this problem has been solved and phased out with future releases. /priority important-soon /triage accepted /help /cc\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 : Problem: is in and set in the couple repos I checked. is set in . I believe this is for non-prod sites that are running, however I believe even the old released sites are considered \"production\" /triage accepted /help /cc </details\nhttps://v1- does look wrong. We could override this file explicitly for the older releases (perhaps just as an interim measure?)\nIn the v1.19 docs, appears in the page head. That's wrong.\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\n/lifecycle frozen\n/retitle Search engines indexing old releases Also, the upcoming release is also being indexed and we don't actually want that. Same cause I think.\nHi and I would like to work on this issue. I can see the proposed solution has already been implemented. May I know, what new things we need to work on for this issue? Now, Google search for \"kubernetes secrets v2\" returns: ! /assign\nI've proposed a PR to fix this. :crossed_fingers:\n/reopen We also need to merge 4 backport PRs.\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\n[Backport PRs]\nIt's fixed. I checked. /close\nClosing this issue. <detailsIn response to : It's fixed. I checked. /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":"q-en-website-894188247b2b90c80f9d13856d2f520ffebe5b12e02228dd598ade6f9a9c6426","text":"includes the deadlink:\n/kind bug /triage accepted /language en\n/sig cluster-lifecycle node i've LGTM on the pending PR.\n/retitle container-runtime: migration guide points to a 404\nthis PR did not fix the problem: because it lacks a leading i will send a new one.\nnew fix is here:"}
{"_id":"q-en-website-1929a9d1e69e84954e6108acbd3cdaaae8b37d3d7ab3ccb234964071476346b8","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":"q-en-website-e91d11da95df52011868da5aaa31c0e31d0261d47435499f2e463b20d815cf55","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":"q-en-website-bb22f5b7c25ac4c252fc99b94d95b04b4bc492d01ab010469782961210f71e5f","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 at shows in the being used without . Because (by default?) sets up the scheduler to run inside a pod, it is necessary to use to mount the config file into the pod. Using the example as given will cause the scheduler to fail to start, even if the referenced config file exists on the host. It is also not mentioned here that providing a config file (now?) causes the scheduler to ignore several of the flags (like and ) that kubeadm sets the scheduler up with, so any config file passed needs to duplicate those settings if the scheduler is to work as kubeadm intends. In particular, without setting a , the scheduler will not come up. This documentation is especially important because doesn't necessarily work before the scheduler can schedule enough Kubernetes components to start up TLS, so it can be nearly impossible to debug what is wrong with a non-working scheduler pod without a lot of documentation. Proposed Solution: A working example that lets the scheduler come up with a nontrivial configuration change seems to be: Scheduler config file on host in e.g. : Config file for to point to and mount it: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.19.3 <!--Additional Information:--\nno other ways are supported, by kubeadm. i can see how the kubeadm example may be bogus in that regard. if scheduler config overrides flags that is an artifact of the kube-scheduler. normally flags should override config, or the mixture should just error out. if some kube-scheduler specifics are not documented they should go here: or here: kubeadm just allows you to configure it and i don't think we should special case the component a lot here: having the following minimal example makes sense to me: ^ this sentence can also be extended to link to /sig cluster-lifecycle scheduling /triage accepted PRs are welcome.\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\nperhaps pages like: should start linking to the respective component config pages too:\n/assign"}
{"_id":"q-en-website-abd586a38057194b51a27b7b6ab46ac5e582b21ffbffbca67ffa05acba679cec","text":"No navigation panel says anything about bound service account tokens. describes service accounts and their non-bound tokens. mentions them in a 4-th level subsection under automation in the admission controller (which omits the fact that the kubelet is also involved in automating bound tokens, see ), but that subsection is omitted from the TOC because it is 4th level. Apparently that 3rd-level branch is only taking responsibility for describing service account automation in the admission controller. Bound service account tokens are an aspect of the authentication functionality that should be described on their own right, in the page on authentication.\n/triage accepted\n/sig auth\nThere isn't really a concept page on ServiceAccount. If there were, we could migrate the content to that concept page, and then hyperlink to that new section from its previous home.\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]:\n/remove-lifecycle stale\nIn fact: /lifecycle frozen\n/priority backlog\n/sig security\nis somewhat relevant\n&hellip;until now:\nI reckon will close this issue."}
{"_id":"q-en-website-eb374f50a5934d6c6cf42433078b94dab633680d41a4a181f8f8441503596135","text":"! w sudo systemctl enable crio --now\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 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 zh/docs/setup/production-environment/container-runtimes Proposed Solution: -Page to Update: zh: (en: ) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/retitle [zh] Typo in docs/setup/production-environment/container-runtimes /kind bug /language zh\nPage is a little bit lagging behind. Will fix. /assign"}
{"_id":"q-en-website-fd34d57519d8023188e32208bbca98fda2e45d80eeaf8cecbd764daa997b5358","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: doesn't list ControllerManagerLeaderMigration although there is a page that mentions it. Proposed Solution: Update / write the documentation for the feature, including a mention of in Page to Update: Additional Information: /sig cloud-provider\nI think there's a plan to graduate this to beta; if so, we should definitely look at getting it properly documented.\nyup, agreed. I think we can address it once they open a doc for their enhancement /cc /triage accepted\n/assign"}
{"_id":"q-en-website-e6f779f505f0c5132cb7fa46b594c8747f79b535b83be73ae04fe79cdcb86e45","text":"It would be nice to have a bit of text about what a cluster is, cuz I don't know what it does in kubernetes.\nSomeone might add a link to in .\nThe let you automatically include the existing explanation of what a cluster is. That ought to help too.\n/language en /help /triage accepted\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 : /language en /help /triage accepted 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\nWe could also link to and\n/sig cluster-lifecycle\n/assign\n/unassign Unassign myself since is already working on this issue. Thanks.\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]:\nThe Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:\n/remove-lifecycle rotten\n/sig docs\nyou may have a look at . I think it will help you to understand, what the cluster is! Thank you."}
{"_id":"q-en-website-18ece2c5b51af03f9f7920c2ec964f3394879b1c05070a9bc944669081cf1d87","text":"According to the can get a parameter with a value of \"background\", \"orphan\", or \"foreground\". proposes to use .\nHello Related PRs/issues: So, the page should be updated. /kind bug /language en /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 : Hello is now deprecated in favor of warning: is deprecated (boolean value) and can be replaced with Cascade=false is deprecated in kubectl 1.21, according to Bug /language en /help </details\n/triage accepted\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 </details\n/assign\n/assign\nTo : has already assigned himself/herself, and posted a PR ()."}
{"_id":"q-en-website-2f3c6011dc53b8f10576e711d7e0130f1dc46811ef5fb22c0a2e1939d12f7d35","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: lists Helm as being built-in to Kubernetes. (it isn't; it's a separate project that depends on Kubernetes in order to be useful) Proposed Solution: Reword the page to be a list of both built-in tools and external tools that are so commonly used or relevant that they may as well be seen as required for Kubernetes to function. (for context: see ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en\n/assign\n/triage accepted"}
{"_id":"q-en-website-6cfa9617a010f884aabeb2b57315938614f1c968453d45e6f10dc3c220fe3fa2","text":"\"\" is a wrong expression, \"\" is right.\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":"q-en-website-3215ccaea873f89eed5621369fc8d32ed26f948c695f4e5b4ed444837be4955a","text":"Page to Update: Kubernetes is deprecating as mentioned . But in the page linked there is not even a mention of PSP being deprecated. Either that section should be removed or a deprecation notice needs to be so that the users wouldn't end following those steps if they are on higher versions.\nFor anyone's information: In PodSecurityPolicy is being replaced by a new, simplified admission controller. For more details on this change, see . Follow these guidelines to simplify migration from PodSecurityPolicy to the new admission controller: /triage accepted /language en\n/assign I would like to work on this.\nfixed it here:"}
{"_id":"q-en-website-8b707bef27480af5a67fba002adfaeb138c283f26a671b36bd87eee701cf3989","text":"This is a Bug Report <!--Required Information--Problem: In docs, link give 404 error. Proposed Solution: should be linked to 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\n/assign I can work on this.\nFixed it here:\nref\nHi I think we don't change in file as it is used as configuration when building the website. It was changed in this , as for website repo master branch renamed to main in k8s v1.22."}
{"_id":"q-en-website-59b9a5c9d470dfece5c1be4cad9b59099425cae2c87de323ed3b4936c82a9b2d","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: to to to to Page 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\nClosest issue I could find related to this\nIs the issue open? I would be happy to work on it. Thank you.\nDo you mind testing it on your local environment. I think the documentation is correct.\n/triage needs-information\n/kind support\nPerhaps the words \"Pod\" and \"Job\" may have been misleading. I think \"Job\" refers to a container that complete in a certain period. In other words, this explanation means the following. The activeDeadlineSeconds is recommended to be use for containers (Pod) that complete after a certain period. It should not be used for containers (Pod) that will run forever.\nI would suggest the following. How about it? before: after:\n/close Please re-open if you believe this clarification (\"only if\" instead of \"if\") is important\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":"q-en-website-4c222c518e745b7b8c746c32ffda971c5ae5ae14a1716100b2ef064cc4f9d261","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 link \" API \" is broken. Proposed Solution: Page to Update: -- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko\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 </details\n/assign"}
{"_id":"q-en-website-b4442e9c03f716d0992f669fcade549c60175f21adadd85008c49268f5ba48e7","text":"Look into evaluating how we can make building the site take less memory / cpu. As has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build). This is all good though, it means we are adding content and localizations. Look into ways to reduce build time. A few options come to mind: Can we remove a large chunk of unused content? Can we build only a small subset of docs (easily and portable to the various localizations)? Are there any optimizations in hugo itself? There should be a way to reduce the amount of resources required to build . Considering there isn't a clear solution, I won't mark as good-first-issue. /sig docs /triage accepted\nIdea: run the build localization-by-localization. I don't know if Hugo supports this but if it might let us run 14 shorter builds (potentially in parallel) rather than 1 long one. Idea: look for image resize options at build time. If reasonable to do so, replace the source image with what it gets resized to.\nThis might be an area where we could look for resources from CNCF to help with it - especially if the fix is applicable across multiple CNCF projects."}
{"_id":"q-en-website-9c58f06adf2248e957c8380faf1560062ae033b6132cf493c4252446e552e981","text":"In k8s document page: Second paragraph below Rule b says: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 3 months (4 per year). It should say: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 4 months (3 per year).\n/kind bug /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /triage accepted Thanks for the report.\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 : /kind bug /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /triage accepted 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 pick this up /assign"}
{"_id":"q-en-website-c5d94eea3001a9b1e317d2ad3e3a1af73ee491ef5b3dcb7d22112e828841134c","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: Except for the [EN] version, the unnecessary 'Tools Include' item is displayed in translated versions. Check the left side navigation menu in , However, the translated versions(, , , , , , ) have 'Tools Included' item. Why 'Tools Included' item is shown only in translated versions? This item is an intended headless page(, ) and should not be rendered. Proposed Solution: The item should not appear in translated versions. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/triage accepted\n/assign"}
{"_id":"q-en-website-45ec5fa72d63429b470878eb7d6bc58a62e714c34465cace117da1f37fcc1d4a","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 link for \"admission webhook server leaves the ClientAuth field \" mention under the in the redirect to the code of k8s version v1.13.0 i.e. , The webhook folder doesn't exist under images folder but now the folder is under () folder. Also, the code in the master is modified as compared to the code in v1.13.0. It should be redirected to the recent release i.e. v1.22.0 as linking to master isn't stable Proposed Solution: The link should be redirected to instead of Page 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\n/sig auth\n/assign\nFixed it here:"}
{"_id":"q-en-website-336ecbdb788b4993d1cb2532969e4e97a4ba3823898e0dc48dbde07807944a98","text":"!\n/language zh /triage accepted\n/kind bug\n/assign\n/retitle [zh] typo in kubeadm API"}
{"_id":"q-en-website-a81bef158f228961a470ef152ac4ced03cbb6dac867e200b8797b4cacd0add74","text":"the is broken\nHello where did you find the link? And could you provide more details around where you intend to replace it?\nHi The link to the page is mentioned as the title of this issue. and the broken link (all Kubernetes bug reports) is under Correct link:\nThank you for providing the information.\n/triage accepted\n/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 : /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: Could you amend the body if the issue to reflect the above & confirm if you'll be working on the PR? If not, I'll have other contributors chip in\nHi I can't amend the body of the issue as I didn't create the issue. For the PR I'm up for it and will soon create a PR.\nHello could you please amend the body of the issue properly?\n/assign\nFixed it here:"}
{"_id":"q-en-website-d7079a40153f60a3b990ccf00537d0dbb9343a7dc0b290e4609e47062cb88dab","text":"Translate into Japanese. This page has not been translated. /language ja /assign\n/triage accepted"}
{"_id":"q-en-website-5824891f24dc143bf5fafcdf0005eb8dfdca043847f271a5f6bcb0c8571cce2e","text":"This is a Feature Request Port this: to the migration guide documentation: as a known issue. Note, CRI-O behavior may be different.\n/sig node\n/language en\nIs the ask here to port the Google doc into the Kubernetes docs or just link to the Google documentation (which isn't necessarily allowed)?\nWe can't really do either, unless Google licenses to the CNCF. We could write new docs to highlight the same known issue (what's the issue? - I deliberated haven't looked).\nHere is the GH issue: These metrics are missing in endpoint with Containerd (they were present with Dockershim): Also the format of container name dimension of many metrics was with dockershim, but the format on the containerd node is . This is coming from this file: that even has an internesting note that this is implementaiton details, but changing it will likely break somethings (btw, maybe this may be noted as well in the list of known issues). So workaround for both issues (missing metrics and the name of metric dimension) is to use a standalone cAdvisor, and use one of the releases with the suffix \"-containerd-cri\"\nThat sounds quite involved - should we open a related issue to track explaining how folks would do that?\nDo we have a document that can be followed for using a standalone cadvisor? I checked the tags in cadvisor and turns out 2 versions have containerd as suffix but none have the \"-containerd-cri\" suffix. Ex: v0.41.0-containerd-fix-rc.2 Does the latest version v0.44.0 contain the fix?\ncan you please help here?\nThe fix was in I think but not sure which releases contain it\nSo what do we need to do next, Align versions?\n/assign\nYeah I'm not sure how to tell which version has the changes. It's for sure in 0.43.x but the current \"Latest\" tag is 0.39.x and doesn't seem to have the fix. I think we should wait for or to verify.\nIt looks like updates the page's docker-specific information related to cAdvisor to be more generic to container runtimes. Would that be enough to address this issue or does more runtime-specific information need to be ?\nwhat's your opinion in respect of ?\nIt's due to it being reverted in which is a real bummer for those of us using GKE and the default for new node pools is containerd.\n/triage accepted\nWhat should the next steps on this issue look like?\nmy thoughts: This doesn't belong on the suggested page because it's specific to containerd. I'd say let's update as follows: In Before you begin, add a line to \"Read the known issues section\" Add a section at the end, before What's Next, called \"Known issues after migrating\" Add \"Versions of containerd prior to 0.45.0 didn't collect some metrics in the endpoint. For a list of missing metrics, refer to . To collect these metrics, install a containerd package that is version 0.45.0 or later that has the suffix.\" In , mention \"To avoid the missing metrics in [Known issues after migrating](#known-issues-after-migrating), install a containerd package that is version 0.45.0 or later that has the suffix.\"\nAccording to the comment at the only current work-around for containerd users is to deploy and scrape a standalone cadvisor daemonset, built from the branch. The stats exposed by the kubelet will be broken until 1.25 or 1.26 when is complete. Since it is the kubelet's cadvisor that is broken (and I would argue that it is broken/regressed by this issue), it should be covered in the kubernetes docs.\nIs there a more involved process then than just installing the package?\nit's not a package, it's a branch of the cadvisor project: I'm not sure if they're publishing binaries or images from that branch. A sample DaemonSet is available, which could be modified to use :\nCould we say: \"To collect these metrics, . Set the $VERSION variable to any cAdvisor version that has the suffix, such as \" ?\nI think that needs more work, for example the default DaemonSet only mounts the docker socket path; it does not mount the containerd socket, and even when I modify it to do so the metrics appear to be missing most of the important labels. Perhaps has some suggestions.\nThis feels like it would need to be its own task page, possibly linked from our existing Metrics doc as well\nI've put a ready to run temporary solution here\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]:\n/remove-lifecycle stale"}
{"_id":"q-en-website-3fe28d3fe0159a80bd4bc084cd20522de06d6ed5856d6d70ebf1a58a8d15ad74","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":"q-en-website-c0d57aec86df1376d3ec04424329d82067ef5e5d6e3d0dd7db443b1baef8569d","text":"Ref: needs a rewrite. It mentions Docker (and Podman!) all over the place, which is a good indication that the docs are old enough to need a rewrite. At a minimum, remove mentions of Docker in these topics: /triage accepted /milestone 1.24\n/assign\n/assign\nReasked folks in Slack for correct disposition\nAsked in the SIG Node slack channel:\nTo summarize the consensus from talking with folks about this issue, specifically the examples in Using a Private Registry section: The steps in the Using a Private Registry section are still valid. However, as written, it makes it sound like Docker is the only/recommended way to do this-which we dont want. We should be able to remove the docker examples and point folks to this page , which covers most of the same content with third party disclaimers already written into the examples. I plan to open a PR later this week with these changes!\nHas anyone opened a PR for this issue? It seems to be referring to"}
{"_id":"q-en-website-1eaa797c254ca8401a413bccd7ee02da3b7f261e357f842667273c2ad44c6964","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: When I was reading this , I felt very confused. The meaning of this sentence is to explain that the node, volume, pod and container level information cannot be obtained from the summary API? But I read and code implementation: My understanding is: The node, volume, pod and container level information can be obtained from the summary API. So is an expression error? Proposed Solution: Enhanced description to avoid ambiguity or misrepresentation. Suggested modification: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--The English version of the original PR: /assign\nHi agree it needs fixing per I have a bunch of notes, please add your thoughts so we can clarify this matter. It is confusing.\n/language en The best place to add more notes is issue\nThanks for the reminder, I've comment to\nit sounds like the original author intended instead. Outputs definitely works too.\nUse as the word makes sense, thanks for the reply!\n/triage accepted"}
{"_id":"q-en-website-21b57d982c55124e2062d64d0567be4ff93a72cf44340c0fecabbbee6a7b4994","text":"deployment 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"}
{"_id":"q-en-website-d869749a0dd91de1f1ccdc103795316681a87e1163ee6707b1c64a662779649a","text":"On line - Its better to clarify where node object is created. My assumption is on control panel (api server).\nWe could use a for “object”, so that you can click on that and confirm that objects are created in the API server. /kind feature /triage accepted /priority backlog\n/retitle Explain meaning of “object” in Nodes concept /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 : /retitle Explain meaning of “object” in Nodes concept /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\nHi, I would like to work on this issue. /assign"}
{"_id":"q-en-website-108c07e66f663ff3247ec46fb1ef93c5c7f0a54f90fca2a66cce42fc27ea490e","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: (Despite the PR has been merged, it seems that the error still exists. So opening an issue here. ) From the PR : [As-is] ! ! [To-be] ! ! Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--CC /area web-development\n/triage accepted\nHello Thanks for reporting this issue. May i kindly know some more details to reproduce the issue. 1) Browser & Version ? 2) Resolution of your display ? I'm trying to reproduce it on wide viewport !\nHello Here is the info of my env: Windows 10 Enterprise 20H2 Google Chrome 97.0.4692.99 (64bit) Monitor resolution: 3840 1600 Chrome window size: [1868 1592] ! [1868 1592] [3767 1600] ! [3767 * 1600]\nI can replicate this with Chromium and with Firefox.\n/priority backlog\nThanks for the information. Please can you assign this issue to me.\ntry this Prow command: /assign ravikiranr26 (reply in a comment with that command on a line by itself)\n/assign ravikiranr26"}
{"_id":"q-en-website-4fb6c389b3996451aa91b1848bf78b86f645e05170661d74c10348717f83264e","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\n/triage accepted"}
{"_id":"q-en-website-62f2f27b522585ce62982dc29a1f12a055d8690cf1de08842fda4352a7a9cea0","text":"This is a Bug Report Problem: The of is mentioned in . which is wrong, As per mention in the the correct Feature state for is . Proposed Solution: Change the Feature State of from to . 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\n/sig network /assign\nFixed it here:"}
{"_id":"q-en-website-1e25d2b32c8db1621655f086b8d40d3cdd719508bb116061a1207137b6c64a89","text":"This is a Bug Report This page contribute/style/diagram-guide/ has no Chinese version Problem: This page contribute/style/diagram-guide/ has no Chinese version Proposed Solution: Translate Chinese version for contribute/style/diagram-guide/ Page to Update: <!--Kubernetes Version:--v1.23 <!--Additional Information:--NA Comments /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\nIt is being worked on.\nok"}
{"_id":"q-en-website-e284c42b57e0a3db2d1a43df834a5b853c988b66caf3fa3d54e6701c1a2f202b","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 on readiness probes is unclear. It describes how to configure readiness for a single container, but when it comes to the restart behavior, it's not exactly clear, if just the container or the complete pod is restarted: the documentation says: but then command is used to show that the restart counter of the pod has been increased. It is not clear in the documentation, if this restart counter relates to all containers in the pod (meaning that all containers in that pod have been restarted due to failed readiness checks of a single container in that pod) or just a single container in the pod. In the example it does not matter because the pod consists of just a single container. Proposed Solution: Please clarify if a single failing container causes a restart of the whole pod or just of the affected container, and how it relates to the RESTARTS field of the output of the command. Page to Update:\n/remove-kind bug This is a request to improve docs; the existing docs are unclear, not wrong. /language en /sig node /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]:\n/remove-lifecycle stale\nI would like to work on it.\n/assign"}
{"_id":"q-en-website-2ac5ef3772a0c117740b3a8c9285ec0d731ed960435e6f12b7026bd4a2a0da13","text":"On: But I get: Sorry, I can't provide a PR at this moment.\n/kind bug /sig node /language en /priority important-longterm Static pods are on the syllabus for the CKA qualification, so we should especially avoid recommending a deprecated approach.\nMaybe it makes sense to change to docs from to , too, since that what kubeadm creates.\nThis has been previously discussed within the SIG; migrating off of command line flags is a backlog item. Other components have a similar problem. For the foreseeable future, the command line flags will definitely work and continue to be supported. We are ensuring any new command line flags are as config options and attempting to migrate over any flags that are not currently supported in the config API. So, while technically deprecated, I think this is still okay. It would be great to have docs for both.\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]:\n/remove-lifecycle stale\nI think this is still worth tracking, but isn't a short term priority. /reopen /lifecycle frozen\nReopened this issue. <detailsIn response to : I think this is still worth tracking, but isn't a short term priority. /lifecycle frozen 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/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 : /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/retitle Create static Pods: has been deprecated\n/assign I will try to work on a PR for this issue."}
{"_id":"q-en-website-9cd8a2b36afef188b5bd5caa32ccd84defb985f8cb274623d49b16dfc1e84519","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 file might be outdated. en: Under \"Networking and Network Policy\" section, the entry \"Contiv\" exists. ja: The entry \"Contiv\" does not exist. Proposed Solution: Update . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ja\n/triage accepted\n/assign\nI'd like to create a PR for this issue. Please comment if you are working on this issue.\nsorry, I have not started to work this issue. please do that.\nThanks for your reply. I'll do it. /assign"}
{"_id":"q-en-website-50c7e7c8bd431e5d15f4a77e54c000572c815338203297dcec4a002920c75d94","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? 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":"q-en-website-52eb0fb8392b634441fbd6dda074e307a37d3fbb6e280f9f025c099cf2090a0b","text":"originalFactors that need to be taken into account for scheduling decisions include individual and collective resource requirements, hardware / software / policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference, and so on. translation// \"data locality\" should translate to \"\", not \"\".\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 zh\ntranslates it as \"\". Generally speaking, in computer terminology, we translate this as \"\". Does this page need to be changed Request for advice\n“”“”“”“”\nPR"}
{"_id":"q-en-website-b0d96459fe356ea713f1d8d8f427c2c928b40fcedadf2efd81caea69a19595f2","text":"As part of \"Remove Docker Engine\", this page should probably also tell the user that may want to clean up space was consumed by docker, e.g. . Otherwise, potentially much space is left used but unmanaged on the node.\nSounds good. We could link to and similar page fragments; if we do, we should caution people that Docker's advice has a risk of trampling on containerd. Ideally, we provide just links to third party docs here. However, neither Docker Engine nor containerd has docs for migrating from one thing to the other (let alone any Kubernetes-specific considerations). I'm happy to treat that as a valid exception from the usual .\n/sig node /triage accepted /language en /priority backlog\n/assign"}
{"_id":"q-en-website-fcf5322ac40b75a8657387f18eb8803bbcfe685ff9d7e092c16437d89da8ede3","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 so that early in the page there is a link to You should decide on some suitable text for the hyperlink. Read to get ideas about what to write, if you're not sure. :information_source: Don't remove any of the existing links; this is an addition. Why is this needed This change will help signpost readers to the CNCF contributor site. Comments /kind feature /language en /triage accepted /priority backlog Exceptionally, due to a previous issue where different folks claimed to work on this, I will assign this to myself and work on it.\n(please don't assign this issue to yourself unless your GitHub username is /assign"}
{"_id":"q-en-website-02c0229eae490cfb1073027bd05532c3cee70f73fc837165bd21a6518af17ed7","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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue\nwe could remove the banner and wait till June 15. If a new update came then we can update it?\nI'm OK with removing the banner.\n/assign\n/triage accepted"}
{"_id":"q-en-website-de068a278fd73e76ee65612d5737d8edaf63b784df6c4c320cbbb4cc10df566b","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: Links are broken in page. It gives a 404 error. Proposed Solution: We might need to link them with , , and . Confirm once with channel. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/good-first-issue /area blog /triage accepted\n/assign\nWe typically don't apply fixes to blog articles more than 1 year old. Until there's more blog editorial resource, I'm happy to continue that policy. /remove-good-first-issue /remove-help /priority awaiting-more-evidence\n/remove-triage accepted should we make an exception here?\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\nYes, we can consider this as an exception because those are a few initial important terms in the Gateway API project. If a user isn't able to understand it clearly, it wouldn't be good to continue to read further. Those links are directed to more brief information about Gateway API concepts. Also, in the header of the Kubernetes Blog section, it says \"This article is more than one year old. Older articles may contain outdated content. Check that the information in the page has not become incorrect since its publication.\" Thus, we can consider correcting it Thank you!"}
{"_id":"q-en-website-72bc10ff7ec6079fb2fc25556ff0be86e351e3643f2ebee7a4fc7b42746a59fb","text":"The and link in the section are broken.\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 don't know if the issue is open or not, but I would like to work in it.\nLooks like installation of cosign has moved from to\n/assign\nWhat about Configuration link?\nHi Instead of Configuration we can add Detailed usage of cosign there -"}
{"_id":"q-en-website-9302364979d3e974057e9252d381d5f83fa681108cd397776ef0903b7a981ac2","text":"This is a Bug Report Problem: Following below hyperlinks are not working under task: and The reason for it is it both redirects to but the is changed to in this PR: Proposed Solution: Changed to for both dedicated CA and custom CA. Page to Update:\nAlso, the hyperlinks for both dedicated CA and custom CA were in this PR:\n/assign /sig auth\nFixed it here:\n/language en /triage accepted Thanks for spotting this\nyou're welcome!"}
{"_id":"q-en-website-72a1ea76d38621729b764bdb9c2eb5c95868102d5ea3feac39af413419e94822","text":"This is a Feature Request Will handle the localization of this topic. Open an issue to avoid a duplicated job that may occur, thanks.\n/triage accepted"}
{"_id":"q-en-website-01c6025495fcdd8af6422695962574390ccae4dd0aec8818c05ed2215e5773a4","text":"pods/pod-with-node-affinity.yaml\nPage: /language zh\n/triage accepted The YAML file was not sync'ed with English version.\n/assign"}
{"_id":"q-en-website-df5186f90374f670868ecfe208055187bcadeb0211b7636ea644fd8c5eebfa0c","text":"Cloning is only supported within the same Storage Class. Cloning has supported different storage class\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\nHello It sounds like you might want to report that a web page is wrong. If that's right, what's the URL of the webpage? Also, could you quote or point out the text in that page that isn't right? /language en /triage needs-information\n/sig storage\nHi i would like to explain this issue if i am not wrong wants to update this . As is merged so now users will be able to clone a volume with a different Storage Class. The destination volume no longer has to be the same storage class as the source. But in current documentation we have the behaviour as. Cloning is only supported within the same Storage Class. Destination volume must be the same storage class as the source\nI would like to work on this. /assign\nSorry my bad.. Thanks for pointing it.\n/remove-triage needs-information"}
{"_id":"q-en-website-ba462ff73b9fc9dc15a17381e81916222f16face26474cb36f5fdd5d8d1255bd","text":"This is a Feature Report Problem: misssing Chinese translation docs: content/en/blog/_posts/2021-12-17-security-profiles-operator- URL Proposed Solution: add Chinese translation docs in website Kubernetes Blog Comments /language zh /assign\nURL is :\n/triage accepted"}
{"_id":"q-en-website-c45e37ff3ff25b5eeb48c271db53d7170058fc6c5a4fd90a9d3db6c1bcf119fc","text":"/kind documentation /sig docs Bash Auto Completion has a missing step to enable autocompletion in current shell session If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. If you have an alias for kubectl, you can extend shell completion to work with that alias: Note: bash-completion sources all completion scripts in /etc/bashcompletion.d. Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. To enable autocompletion in current session of shell, source the file:\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/triage accepted\nThe label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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/assign"}
{"_id":"q-en-website-67a8e7436e93386f47604615c0a59de4596cc0bd37e2561f501831f725d0c5e1","text":"I will submit the PR as well Problem: Steps to reproduce this will result in the following error: Proposed Solution: Remove the 1st key which was used for doing repogpgkey check however since the repogpgcheck option got removed so this 1st key is no longer used/needed. So this would be the fix: Page to Update:\n/assign\n/triage accepted"}
{"_id":"q-en-website-090f10ee587a9f64764606770bc318b9c53d4ed797a039c823f3bb2db3d86b4b","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: states that kind requires Docker. This isn't right as I understand it; you can actually use with Podman, even if you don't have Docker installed at all. Proposed Solution: check what's right update the docs to match the truth Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en\n/assign\naccording to my knowledge we can use Buildah for managing container images and Podman for managing containers if someone is looking for an alternative to docker. But these can be used only on Linux, so for windows or mac a Linux VM will be used to run these and I am thinking to put this in a note. Your suggestions?\n(yes) Also see Kubernetes itself doesn't require any of the listed tools (Podman, Docker, Buildah); for example, you might use CRI-O and runsc and the kubelet, but no Docker Engine.\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]:\n/remove-lifecycle stale\n/triage accepted\nI don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign\nPodman now has documentation on how to work with the and plug-ins: https://podman-\n/assign"}
{"_id":"q-en-website-73c7090439e247f69db601d488d4f74d8ccf4786ff4d493d39f2237a4f977fd0","text":"Problem: The text on redirects to the correct link should be For the problem, check the page . Proposed Solution: It should resolve this issue by removing the context link and editing the text to enhance the document line. Page to Update: Update the link on text vSphereVolume CSI migration as and not 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 redirects to the correct link should be It should resolve this issue by removing the context link and editing the text to enhance the document line. /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":"q-en-website-e3ae386fd4db0893367e9b8fda7048b845d258ad98a92fb460957a5b9252f6ce","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: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.\n/triage accepted\n/assign"}
{"_id":"q-en-website-feb5d4f2b566d7d8b6687f14ebac8cc533db8ef376723d1897a8d64924e118d1","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 main branch after we complete around 3~4 weeks job. PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) 3~4 , main . PR : 10/03 ( PR , PR ) : 10/06 (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 This is a Feature Request is the current work branch for Korean localization.PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) PR : 10/03 ( PR , PR ) : 10/06 (main , k8s.io ) /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\nThanks :) /triage accepted\n/milestone dev-1.25-ko.1"}
{"_id":"q-en-website-2093b2f474b428b024e759dd84d1d242e37e6ecd7ccbb56dac49f364a69dcc1b","text":"This is a Bug Report I have fixed the same issue in English docs, same issue is followed by the other localization team. has one broken issue which needs to fix. ! Refer my merged PR of english docs. /assign\n/triage accepted"}
{"_id":"q-en-website-a315e8fad385d62ef032108d9373ede1f46d7d91b82e9e2e1f456288c6b7ea8d","text":"This is a Feature Request What would you like to be Translate content/ja/docs/tasks/debug/debug- into Japanese. Why is this needed This file is only translated the title, not translated the description and the body text. Comments /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\n/assign"}
{"_id":"q-en-website-0b0d6d11b950c8d8e90fd64d62a4b98320dcdacdd1f4fc525446352bf4b577a7","text":"If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted\n/assign Thank you"}
{"_id":"q-en-website-2c496f4a797e1f01f1983b2b9fb30fe90b994fd61584108302275bf3a61381b1","text":"If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted\n/assign\nAhan! A great approach to helping new contributors. Sorry I missed that point. /unassign\nHello Team, This is my first issue on kubernetes/website. I would like to work on it /assign\nKeep working on this issue. Feel free to raise a PR"}
{"_id":"q-en-website-771850e25fdc4c90b2de5d91386a36acaff5740c46dd0bdc71f12e0ff1109f8d","text":"This is a Bug Report Objective should be replace by उद्देश्य in content/hi/docs/tutorials/kubernetes-basics/create-cluster/cluster- <!--Required Information--Problem: Objective is english word in hindi content Proposed Solution: Replace with उद्देश्य Page 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\n/kind documentation\n/assign"}
{"_id":"q-en-website-5c3efcfb3f462a538aa7bd2ae47e1a1fec6f96d9cb5b50d5f28e3496ef958b08","text":"Umbrella issue: contains multiple \"use cases\" for Secrets. However, many of these are mini-tasks. In this issue, I'd like to discuss each of these use cases at a high level to see which we can remove, which we can trim, and which we can move to a new or existing task page. That way, the \"Use cases section could even be a bulleted list with links to relevant tasks. Use case: As container environment variables Recommendation: Delete Justification: the goal is achieved in . This also isn't a use case, it's a way to use a secret. Use case: Pod with SSH keys Recommendation: Delete content, keep use case as bullet Justification: the steps add no value beyond the existing task to . Use case: Pods with prod / test credentials Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page. Use case: dotfiles in a secret volume Recommendation: Remove steps and keep as bullet point with additional info about why it would be useful. Use case: Secret visible to one container in a Pod Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page with actual steps to achieve more than just \"secret visible to one container\". Perhaps including RBAC steps. If you're interested, review each use case and leave a comment for each agreeing, disagreeing, or providing a different approach to each use case. After we've discussed and settled on an action for these use cases, we can start the actual work! /sig docs /cc\n/assign\nI think the \"Use case: As container environment variables\" can be removed as the goal is achieved in too.\nYeah agreed, although I'm separately removing that section and linking it to our existing task page as part of\nLet's shift \"Use case: Pods with prod/test credentials\" and \"Use case: secret visible to one container in a Pod\" to and attach the link in the use case section as bullet notes.\n/triage accepted\nImo the prod/test thing might not even need to move - it can live as an example in the concept but the task steps seem quite basic now that I think about it. Just referencing two Secrets in two different Pods..."}
{"_id":"q-en-website-34833f4815db502d89494ba7ab93106fcd1f6e9f7ef9e487ce16bb0a31bafd4a","text":"This is a Bug Report <!--Required Information--From k8s v1.24 the and are no longer available as a feature gate in k8s. From v1.25 there is a separate document that contains information on feature gates that have been removed i.e. . In the and feature gate link to the page which is incorrect, instead of that, it should be page. The information for both feature gates is on the Feature Gates (removed) page not on the Feature Gates page. Proposed Solution: SupportNodePidsLimit and SupportPodPidsLimit feature gates should be linked to instead of 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\n/kind documentation /assign\nFor GA'ed feature or deprecated feature, if the gate is removed, we may want to remove the linking texts altogether rather than having existing text pointing to the outdate gate names.\nHi Just want to confirm it: So for this, you want to remove the whole note section for both feature gates, because both feature gates are removed. Am I understanding right?\nis it seems good to you?\nI meant this: move the \"removed\" feature to the dedicated page, if this is not done yet. The \"removed\" features will stay there for the sole purpose of reference. For all texts (including notes) that reference these gates, remove those references. If a feature is deprecated and removed, those texts may well become invalid. If a feature is GA'ed and removed, those texts may be still valid, but the reference to the gate should disappear.\nThanks, for your response.\nand both feature gates were graduated in v1.20 and removed in v1.23. Both are present on the dedicated page i.e. . So I will remove the reference to these gates.\nI will create PR for it soon.\nFixed it here:"}
{"_id":"q-en-website-f44947ceba21508dd95e172e6601e82240a206eb1fb6b2f65096692ef5c9afb6","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. --Add description that startupProbe successThreshold must be 1. Why is this needed The limitation has already been mentioned in the English page. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I checked startupProbe successThreshold must be 1. /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"}
{"_id":"q-en-website-3dfaebdcb381ddb62f5487c677278cde1b80d980fcbc413e095105cea5f8721f","text":"I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # \"-\" is missing before ports protocol: TCP port: 5978\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 Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this\n/triage accepted /assign"}
{"_id":"q-en-website-543dce49c6cc8577a079b662afca34ab8deb7b8443227c66d6a4c8ffc4bbe640","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":"q-en-website-2eb8761d86dcc2c59d3973b16170e9926589627182b30c711679235d25fda47d","text":"This is a Bug Report Problem: Links for API compatibility and Kubelet Device Manager API Versions under in task are Invalid. It gives a 404 Page not found error. Proposed Solution: For API compatibility the link should be: For Kubelet Device Manager API Versions the link should be: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign /sig docs\nFixed it here\n/triage accepted"}
{"_id":"q-en-website-f74a41a488724e00dfcd2a061df04abf0286e11dce9280a17f1b3b68346e9e45","text":"The content of the file version showed in section is wrong. Previous versions where showing the right content, e.g. .\nThe one in the dev-1.26 branch is not a valid Deployment manifest. The API server will reject this YAML since it is missing some required fields.\nAh, the problem might be that we don't want a YAML file that is a valid Deployment manifest, since this is actually being used to generate a special document used for a with custom Kubernetes semantics. /kind bug I didn't actually know that would accept a thing that's not a valid manifest for ; that's going to be hard to teach / document. Is that even a supported / recommended way to do the change? (I can see that it works; whether it works is very different from whether we endorse it). I think this is a valid report. Maybe we should use an inline example rather than an external file; maybe we need a way to exempt this one YAML file from validation. If we use an inline example, that would mean changing we can keep would need to change.\nIf this YAML has to be an \"invalid\" Deployment manifest, using an inline example is more appropriate IMO.\nI'll also ask SIG Architecture if this use of is one we endorse.\nExactly, this is one of the \"tricks\" behind SSA: you only provide (to the you indicate). Providing a fully compliant (from an schema pov) Deployment manifest would actually be a mistake if you only want to modify the field using SSA. Kubernetes client-go was updated to support these non-fully-conformant-from-an-schema-pov manifests: defining the new types for this to be possible as described in this .\n/triage accepted /assign\nOK, so the input to is no longer defined to be a manifest: it's actually an apply configuration, and all valid manifests are also valid apply configurations. However, defaults to validating that the supplied apply configuration is a valid manifest. You can then turn off that validation by using . Have I got that right? If so, I think we missed a key docs update when we made that change to / client-go. is the only mention of the term apply configuration on the Kubernetes site; the docs don't describe this at all. The rest of this comment assumes that the apply configuration concept does need documenting. I think we should clearly document which subcommands work with manifests and which with apply configurations. For example, I'd have to turn to the source code to answer which kind the subcommand expects, and that's not something an end user should need to be doing. A few subcommands and plugins to consider: - -\nI also think we should track a new issue for to document the apply configuration concept, and leave this issue to cover the specific bug that reported.\nis solving the reported fault (so properly closing this issue), thanks for it. I think there is still room for improvement in the \"Transferring Ownership\" example this issue is targeting (maybe to consider it in a future update of these pages?): For the \"more advanced\" case (the one targeted by this issue) it is proposed to use a partial manifest; used term here should be \"fully specified intent\" as it is the introduced term at the beginning of this same SSA doc. page to name these \"shorter\" yamls we can use with SSA. In the final is not needed, better to remove it to not confuse the reader."}
{"_id":"q-en-website-6be0a7fefff21a91459b5060ac89e99dbe8109aeb3ecb7804ed911c1dea78575","text":"This is a Feature Request What would you like to be Translate tasks/administer-cluster/use-cascading-deletion/ 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":"q-en-website-ac3d85d4938f9dc23d6a7c3540f11deb9d9e4d8f20f119a6f9167a211fcfeff9","text":"I was doing the step-by-step installation for v1.26.3 and found this as the final step for installing on Windows: installing the plugin, clean up the installation files: del Please correct me if I am wrong, but isn't the kube controller that I just installed? It isn't an installer, it's the product. Your instruction should not be to delete it. If I delete then I won't have kubectl installed anymore. Make sense?\n/kind bug /language en /triage accepted For Windows, we don't provide our own installable package and the instructions don't explain putting the kubectl binary anywhere special. Until that changes, let's not advise readers to delete .\ndo we have to comment down or delete the 5th instruction there ?\n/assign"}
{"_id":"q-en-website-c3c56cdb88f42c98c3bdd38402698852dd3aa0844fa746b84b5c52faa6c35b8b","text":"In the third sentence on the second paragraph it reads: | operations, such as containerd or Docker. It is not clear if is a typo or a new term.\nI believe writing \"such as containerd or Docker\" was not necessary because it was not very accurate , only writing till operations is fine enough . But still it is not an issue there .\nis a container runtime that manages the lifecycle of a container.\n/retitle \"Using Minikube to Create a Cluster\" unclear on meaning of containerd /language en Page to Update: For additional info, adding a hyperlink pointing to the corresponding official doc of the container runtime would be useful here.\nI think the sentence is referring to the container tools and containerd manage the lifecycle of container on VMs.\nYeah, I get that. For someone new not familiar that this is a tool, might be confused. I originally thought it ws a typo and later realized it was referring to a dameon process. Not sure if there could be a link to docs of containerd so the reader won't get confused.\nyes i also think adding link to docs of containerd would be useful for the reader to get clear understanding.\n/assign\n/kind documentation /triage accepted Improvements are welcome!\nWe could add a reference to our glossary entry:\n/language en /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 : /language en /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\nIt is not the only problem on that page, the description of minikube is not very accurate (anymore) either... But it will soon need to change anyway, when the online tutorials disappear, so probably time for a rewrite ?\n/assign"}
{"_id":"q-en-website-12da5e83e4722a910d81545d16de448b4440d00de3ed1d95f0a8d7f5eb2b6f87","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":"q-en-website-b265bf0fad0514d0ab89ed077ad3bcdcc64bbed832d933ecc22dc21027987e88","text":"This blog has not zh version yet. I will localize it. Open the issue to avoid possible dup. /assign /language zh\n/triage accepted"}
{"_id":"q-en-website-48d2a5188089a3851445649cdbb23ff1d3ae191f1567258131b35b5bee6e7318","text":"Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is\nWould you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information\nReference:\n/remove-triage needs-information\n/retitle Include in glossary and add tooltip for it on \"Kubernetes Components\" page /language en\nCan I work on it now?\n/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog\n/assign"}
{"_id":"q-en-website-686b8602d5beaa1a2490fb166313bec9e80323cca5889eb24894c327778d2c8e","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 translation /ja/docs/home/supported-doc-versions to current English version Tue May 31 06:54:51 2022 +0600 Why is this needed fix outdated doc 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":"q-en-website-808cafbf55eb7b4debbe3b40475d0b24491d21f56f2be7419a5570e15cc416a0","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 Bold isn't effect in \"Auditing\", as shown below: ! Proposed Solution: Modify the format to make the bold effective. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nIf this issue been triage/accepted, I think I can fix this. /assign\n/sig docs /language zh\n/triage accepted\nThanks for the catch! You can fix it if you want.\nSure, let me fix it."}
{"_id":"q-en-website-f64bb7098b77ebddffa3ed77979435f0a43beec87d78e0d5d79104ccd30b10b3","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. -- page has some problems. -page link isn't working. resource metrics pipeline full metrics pipeline the Japanese page exists, some links jump to the English page. Pod Service Why is this needed it is inconvenient for the user. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\n/triage accepted"}
{"_id":"q-en-website-de96689cf66b8ae14fec527ff247baec5761a9cbfab02b555bdafa1c130cdd72","text":"Hello there, I would like to suggest adding a link to the CEL Playground in the Kubernetes documentation. CEL (Common Expression Language) is used in Kubernetes APIs, such as the , and the CEL Playground can help users easily test expressions. The playground also includes a set of examples and the . I believe the link would be useful on the following pages: The CEL Playground is available at and the source code can be found at I also invite you to test and contribute to the project. Thank you.\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\n/sig docs\n/transfer website The repo is not quite the right place to track this.\n/language en /kind feature\nIf we add a link, I would add it to: (and I wouldn't add it to the reference page ; instead, we can have link to the three pages I listed above)\n/wg api-expression\n@ Hey which particular points on these links would you want the CEL playground. I will be glad for more clarification on this?\nIMHO, a mention similar to the mention of on the would help: but saying that users can quickly test CEL expressions in the playground.\nHi I've opened a PR () with some suggestions for adding the CEL Playground link. Please take a look and let me know your thoughts. Inviting to share their thoughts as well.\nI'm supportive of this. It's a wonderful tool and the community will benefit from being more aware of it.\n/triage accepted"}
{"_id":"q-en-website-009222e4b48f7a543a9ff49592c9e5d808568458f5efbf2fa86c496795819038","text":"It is unclear what is meant by The statement appears directly under the heading \"Creating a Deployment.\" It is confusing, and it is unclear what relevance defining an \"environment variable\" has to do with a deployment. Could it be that the author intended to present an action item of defining a pod, and linked to another article that coincidentally contained markup to do so? Suggestion is to clean up the paragraph, and link it to an appropriate article on defining pods, if so.\n/sig apps\n/retitle Unclear text in “Creating a Deployment” section of Deployment concept\n/language en /help /triage accepted\nI recommend removing from the page. That's a small fix that doesn't need us to work on the rest of\n/assign\npage to be updated:\nLooks similar (possibly duplicate) of issue we already have\nTrue. /triage duplicate\n/remove-triage 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/remove-help Oops"}
{"_id":"q-en-website-2461f712f06e2fbfc14fd8d3d72b50baac3d2c55acb6df981507df2529dafbe5","text":"It is quite unclear from that the feature \"GenericEphemeralVolume\" is a feature gate because its design does not follow the guideline. The following steps should be done: write the feature gate name as inline code, e.g. change the wording from \"feature\" to \"feature gate\" Also there is no information about the components on which this feature gate can be enabled. But! This feature gate is only in . Looks like it's not a feature gate now. Consider removing it from the 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\nPage related to issue: /language en\n/retitle \"Ephemeral Volumes\" page references the usage of a deprecated feature gate\n/sig storage\nfeature gate has been removed in , the text needs to be updated.\n/assign"}
{"_id":"q-en-website-e341681a44ba2e9345f104e6bd15f892dc8ef892490de9f911ac35d01a5b63f2","text":"This is a Feature Request What would you like to be Add a comparison between the CRDs and API aggregation layer. should explain this - but doesn't! Why is this needed It's needed so users can understand the difference between CRDs and API aggregation layers.\n/sig docs /sig api-machinery\n/trick-or-treat\n! <detailsIn response to : /trick-or-treat 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\nWe can take some reference from this to understand the difference between and .\n/triage accepted /wg api-expression\nThis issue looks interesting. I would like to raise a PR for more explanation. /assign"}
{"_id":"q-en-website-b6a45cd113522f65dd4ae073c027f7646635a1491c1e82415c4f76c3c02d4624","text":"This page should probably link to resources for defining standard annotations. Especially the thinks mentioned as examples. That would unify it a bit (for example contact address). Maybe link to\nPage related to issue: /language en\n/retitle Signpost from \"Annotations\" to \"Well-Known Labels, Annotations and Taints\" reference page\nWe can enhance the section by including a link to the reference page, as well as any other relevant pages. This will be beneficial in guiding readers to explore those additional pages.\n/kind feature /triage accepted /priority backlog\nplease i will want to work in this! /assign\ni have riased pull request please review."}
{"_id":"q-en-website-11b4f2119bef05dee4d2001f3aaed41a61157aed8e3146e006d843db9d690182","text":"In page , the first part describes that an online interative tutorial is included. But in fact, this tutorial was shutdown a few months ago. I think that may confuse some readers. !\n/language en\nSome replacement of words can fix this paragraph, but why katacoda/killercoda playgrounds are not used in these tutorial pages to make it interactive? /sig docs /kind feature\n/assign\nSeems like it's katacoda related.\nHi you don't need to translate anything. Just create a PR for english. (Optionally you can translate this if your know some other languages too. If you try to do so, raise a single PR per language.)\n/assign\n/kind bug /language en /remove-kind feature /triage accepted /priority important-longterm To discuss potential replacements for Katacoda (which has shut down), visit If anyone would like to support the Kubernetes project to set up or make use of a free replacement for Katacoda, you can: send financial to the Linux Foundation (very indirect support)\n/assign"}
{"_id":"q-en-website-2b115ae8313dc46e1a4bb0d96b618d5f9874381441d5f743e9e0311a56215ecc","text":"Config API needs to be localized into zh-cn.\n/sig docs /language zh /area localization\n/triage accepted\n/assign"}
{"_id":"q-en-website-af18aafc02840f35325308f558decc25865418c16eb2b002a309e4fa8c9d3d5f","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: [Install and Set Up kubectl on Linux] page layout is collapsed. Right side layout is displaced to down. Proposed Solution: Right side layout should be in place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: !\n/language en /area web-development\nI will try to help with this. /assign\n(or any maintainers) Can i get some hint and go ahead to work on this please?\nIt appears that the changes in have inadvertently resulted in the layout of page broken. Potentially addressing could solve it.\nWe should fix the layout of the page. /triage accepted /priority backlog\n/retitle Page layout for \"Install and Set Up kubectl on Linux\" is broken\n/remove-area web-development This is more of a content fix."}
{"_id":"q-en-website-7477f4bb69cf82301d3401a85a3db7a36d8b649681254ac49d1c5b299e865da7","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\nThis issue was created to be assigned to Could you add a comment here to assign this issue to you Edith, please?\nHi I would love to work on this translation.\n/assign"}
{"_id":"q-en-website-4b2e874f7ece2ea0fb0a404123d23ad8b1ad2aefe1da21261c12e9049bf44caf","text":"This is a Bug Report While the left hand side navigation menu in Hindi and English is not fully matching and can create some issues for a native hindi reader . <!-- 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 option in English has been changed to in Hindi which can be an issue while navigating for a native Hindi reader. Proposed Solution: I have 2 options, I can change it to or . Suggestions required Page to Update: Screenshot(can be easily compared up) Hindi ! English <img width=\"960\" alt=\"image\" src=\"\"<!--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/language hi\n/retitle [hi] Navigation menu displays 'Home' instead of 'Documentation'\nIt appears that there is already an existing (umbrella) issue , addressing this request for all the different langauges. Additionally, there is already a PR raised specifically for the fix in Hindi language.\nMarking this as a duplicate. /triage duplicate\nif possible assign it to me i can work on it\nYou don't need an assignment to work on issues, Anybody is welcome to propose a fix Being said that, If someone will/has already proposed a PR, It's polite to co-author with them (but not mandatory)\nThis issue although addresses same type of issue as in , but in different place. is addressing specifically for footer across all localizations. And in this issue it is for Navigation menu and that too for specifically Hindi localized page. So, i think its better not to consider it a duplicate. For those, who want to work on it. Changing this key-value pair with value can probably fix it. !\nCan I plz solve this issue? I want try do some localization cjhange to deepen my udnerstanding and help languages team where i can :)\n/remove-triage duplicate Based on info provided in\nAnyone is free to propose a fix by submitting a pull request; you don't require anybody's permission as we operate in the spirit of open source collaboration. Just a friendly reminder, these changes pertain to Hindi localization, so having familiarity with the Hindi language would be advantageous, although it's not mandatory.\nOkay got it. Thanks! I will assign to myself in that case. /assign\nI have riased plz review and let me know if its okay. Thanks in advance."}
{"_id":"q-en-website-f767ef14d562d18a015033f6d5904663a673724b1e32490f90e2206f57eb6eb4","text":"Problem: There are broken link in page. Proposed Solution: --Page to Update:\n/triage accepted\n/assign\nIs the issue still open, anyone working?\nYes, I'm working on it!!\n/area localization\nI think has already raised a PR!\nPR working on this issue"}
{"_id":"q-en-website-2dfdea9987d19889723c42f231625a4be7eb4e2718a2f4c4d05c3320cb3c8129","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.\nAh, 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":"q-en-website-b2649880e3cb9da273ab09ced2385f39950a405230caa5c4daefbf6f6280429c","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":"q-en-website-9e9528247a4cdb81221b07c692cc414cd6fcc82432285f6c65747ee18510dc26","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":"q-en-website-a9593810b1e8af225b359b92a1f71c6207026dec44d0b1b441090f174b990deb","text":"The following links for Weave Net are no longer viable, and should either be updated (e.g. pointing to the GitHub repo where it is now maintained, , which again, admittedly needs to be updated, but puts the onus on the project itself), or the page should be completely removed: Google link-to-highlight: ,by%20the%20policies. This issue resembles\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\nSubmitted PR with fix for review and merge. Can also remove page and associated links if this is regarded as a type of technical debt.\nPage mentioned in the issue: /language en /kind bug"}
{"_id":"q-en-website-3ed5af6a12e621b371afdeb744293562e88152c8c052af7f225aab471a545d15","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 Document (and register) the legacy annotation The page to change is: Why is this needed We try to document all of our annotations, even the ones we ask people to stop using. Comments /language en /lifecycle frozen /sig network cloud-provider\nCould be useful, let's consider doing this. /triage accepted /priority backlog\nI'd like to work on it /assign I'll share the findings here so the content is confirmed first.\nHow's this :\nI got reference from cloud-provider-azure and Microsoft docs.\nFrom it looks like we need a pile of other issues about unregistered annotations for this cloud provider.\nYes, you can find the other annotations here: https://cloud-provider-"}
{"_id":"q-en-website-a3dd176f2ceffcd2f2094240c62f79dcb79daee83cfa3ef428c60ae93fd99272","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":"q-en-website-de5da431097851c372e56a750b8394e4e28d6f93482c8948a1b480409c82d072","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 \"\" Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\n/language ja /assign\n/area localization /triage accepted"}
{"_id":"q-en-website-0d78ef1906dd1bc2e088499c1132d3c3a92b9f54c80f13180a6be95c584f315f","text":"FEATURE STATE for feature says According to page it is still alpha, being first introduced in 1.22. Should not the FEATURE STATE line then say ?\nPage related to issue: /language en\n/retitle Empty feature state tag for \"Memory QoS with cgroup v2\" in \"Pod Quality of Service Classes\" page /kind bug\nWe should fix so that the correct feature state is reflected. /priority backlog /triage accepted\nIt appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /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 : It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /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 will want help with this. /assign"}
{"_id":"q-en-website-e7b983eb35536bfd1205679e803f64228826495115c155a9f4f48df2849b1bb0","text":"The section of the \"Set Kubelet Parameters Via A Configuration File\" concept contains a broken link that needs to be updated to point to the correct documentation page. The link labeled \"reference document\" in the following line is broken: Update the link in the markdown file to remove the extension, correcting it to the following format: Where to fix: File to change To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /priority backlog /language en /triage accepted /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 : ## This is a Bug Report Learn more about kubelet configuration merging in the . ### Additional Information: To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /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\nIf you've already worked on Kubernetes docs before, please consider leaving this issue for someone new to contribute.\nI would like to work on this /assign\n- Would you be willing to leave this issue for a new first time contributor to work on?\nyes sure! I was confused about taking it on. I'll unassign myself\nI would like to work on this as a first time contributor! /assign\nif you'd like any advice, join our Slack workspace - - and head to #sig-docs\nThank you appreciate the info. Will reach out if I need!\nare you still working on this issue. I would like to work on this issue as my first contribution.\nsince yesterday? We're OK with people offering to step in, but: this is typically after weeks of not hearing from someone, not hours. Anyone is welcome to work on this issue and we do have a “no cookie licking” policy to support that. However the best way to make a new contribution would be to look for a different issue. I think a PR to work on would be useful.\nAnother issue to consider working on (for anyone who's looking for a Good First Issue):\nI thank you for the information you provided. I was unaware of that because I am new to open source. I would look for other issues to work on as my first contribution.\nHi Yes, I am still working on this :) Please bare with me folks, will hopefully get this done by mid next week latest but will update here on progress. Thank you!\nHi Team, I have created the PR with solution. Feel free to review and merge :)\nFixed as part of /close\nClosing this issue. <detailsIn response to : Fixed as part of 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":"q-en-website-4e1a66add725ae639fa433de207bd9a63baf788f2307f19042bff7c9c459db7f","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 Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\n/area localization /triage accepted"}
{"_id":"q-en-website-4ab6b794beb5e57c187c3375fd92af50d22e3ef51713aa52e50165f455b9164a","text":"This is a Bug Report The link provided for [Node Lease objects] is wrong <!--Required Information--Problem: The provided link is navigating to top of the page not to corresponding sub section. Proposed Solution: URL link should be Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en\n/assign\n/triage accepted"}
{"_id":"q-en-website-ac720335fdfc1e41d807ff44e34bdc2f1bb9f7d62243b8e49d0312bc238c169f","text":"This is a Bug Report The glossary tooltip for is referencing section, instead it should reference to page.\n/sig docs /language en\n/assign\nfixed\n/retitle Incorrect glossary tooltip link for 'Container runtime interface' /priority backlog /triage accepted"}
{"_id":"q-en-website-134a8fce333c23da758fd925f5738f67553c003e0ed0e793d8c0460325b064e1","text":"Hi, In k8s v1.30 documentation page , in the top FEATURE STATE line, the indicated Kubernetes version where this feature reached \"stable/GA\" is said to be 1.30; if you check which it is in k8s v1.29 doc page: it says 1.29 .... for 1.28 doc it says GA/stable was reached in 1.28 ... and so for the previous releases ... It looks there is a wrong moving version for this, pointing to the current one \"owning\" the doc page. According to it should say: FEATURE STATE: Kubernetes v1.14 [stable]\nPage reported in issue: /language en /kind bug\nWe should correct this discrepancy in the feature state. /priority backlog /triage accepted\nI try to help with this. /assign"}
{"_id":"q-en-website-18cdb06c5b8e31859d5002c4951c4fb27330f30f24b4e93574182b46717882de","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/triage accepted\n/assign\nsan, can you please review the PR"}
{"_id":"q-en-website-91b7687e0a28864e16407b9b77426bffe21b2ce4ff1d898f0432c634afad108c","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 \"\" Why is this needed There is no Japanese translation for this page Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/area localization /language ja /assign\nthank you!! /triage accepted"}
{"_id":"q-en-website-80d1c56609a0d48e0fc82fc628383ca6b394f8079f489da89ea33c1026568385","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 annotation is unregistered, but used in Kubernetes code. The says: However, we don't have a mechanism to register annotations that are not also documented. So, it needs registering. Proposed Solution: Register the annotation, by mentioning it in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node Required for\n/assign\n/priority backlog /triage accepted\n/lifecycle frozen\n/assign\n/unassign Unassigning my self as PR is already raised by PR raised for this issue"}
{"_id":"q-en-website-d23414076776867b2ef84f4225ec2f2b7a73e43f226a0c82bf364e9b8234565d","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":"q-en-website-00c360976ca87c4fa00de1ad3f7a337a0d9bd51b3b40bd27d3b29eb9ae4b9baf","text":"There's million users which have no direct internet access from the workplace other than downloading from HTTP/HTTPS websites for security reasons. Others do not have chocolatey installed or cannot copy/paste curl commands from an external website to their local workstation, also for security reasons. Currently the HTTP link to download kubectl is inside a curl command. It could be possible to provide a more explicit HTML link, for clarity.\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\nWe could have the kubectl install pages link to Historically, we had this guide to installing kubectl before existed. Now that is a thing, we can link to it. would that suit you? /retitle Task page for installing kubectl should explain how to find direct download link /kind feature /language en\nThis was originally filed about\nI did read that page and I can see that there's already a direct download link for This is under a slightly misleading heading; the text is headed: so maybe we'd like to change the heading as well? I still recommend linking to the list of binaries you can download. The existing link does assume amd64 architecture; on the other hand, AMD processors (and Intel clones) are the market leader. /priority awaiting-more-evidence\nThank you yes the misleading text is probably the main problem - but the list of binaries can also be very useful as the organizations who prevent direct internet access are often the ones who don't run the latest version of any tool :) The idea is to make it as clearer as possible as it's gonna be the first option for many as opposite to run curs or package managers which aren't so common on Windows.\nOK, so: which fix do you advocate ? We should recommend one so that someone picking up this work knows what approach to take.\nHey I'd like to work on this. Based on the discussion, here are my suggestions: Let's update the header title to specify a direct download or curl option. We should add new paragraphs describing a direct download option for all supported architectures. /assign"}
{"_id":"q-en-website-3434e1fe81aaf9618df311fd93e2b0430660f7827947dd677148d0d7c53abd1e","text":"The CNCF on cloud native security defines security controls and practices that are appropriate to different lifecycle phases 404 link\n/language en\n/assign\n/retitle Broken link to CNCF white paper in \"Cloud Native Security\" page /kind bug Page reported in issue (based on initial title):\n/priority backlog /triage accepted"}
{"_id":"q-en-website-dbcb2645f58fe13f0b7a60a8e26dd4f7373ba408640c9b9903d423465fa17254","text":"The indentation of the example configuration is messy. !\n/kind bug /language en page:\nAlso Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.\n/retitle Messy indentation on kubeadm config reference page\n/priority backlog We'd prioritize other improvements over this one. /triage accepted\n/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.\nPR sent for website. PR sent for the generator."}