{"_id":"q-en-website-6c9793323877074c1ab8bed498d978e7b8c770cbf71894447380fade48ea2ce8","text":"I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).\nUbuntu is getting a big rewrite as well."}
{"_id":"q-en-website-7c3bfb760b0f32dbb78080eee4e9d6eaa1c0d612259f5fd19aad6cdea5095731","text":"I wish /docs/getting-started-guides/docker/ I wish this page existed"}
{"_id":"q-en-website-704711b8d85ea90b2f7cb8a2c7c182243d082f6c0e8af556022569a6264b69f4","text":"Cites looking at a cephfs example, that promptly 404's once clicked\nIt appears this should actually point to: not"}
{"_id":"q-en-website-21bb091eede30dbf5ec9bec1da9c5d739e9b28caf374946bbe4f712557051894","text":"A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?\nThank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:"}
{"_id":"q-en-website-b754501671935e51c3e92ac67ce3fae64a85f9bf2e5c6a04100b27ebf949c0a9","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: The port-forward command description is misleading. As a user I would expect the command to forward the complete traffic from port 6000 to 5000 locally, not only the data from both ports like the explanation in the detailed command page mentions. Proposed Solution: You could change the description to something like in the detail command description () or change the command to the version it describes. (kubectl port-forward my-pod 5000:6000 -with colon) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale"}
{"_id":"q-en-website-b98ef4b4e6e3c9451b02ffea762360f84da7b4e675ab61fd8daff850a25f1326","text":"This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1\nI think this is an issue that needs to be fixed in socks shop.\nThis merged PR should resolve the issue"}
{"_id":"q-en-website-b96037892c0b64c97fedb2b9014eae73b97a80d987d7b604fd792e3dcfc47f2b","text":"Problem: this page should mention concept as a way to create an external LB to an application. Page to Update:\nThere are some offhanded mentions of Ingress in samples, but they're likely to be more confusing than not. Agreed: more/better docs needed.\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\n/remove-lifecycle stale /assign"}
{"_id":"q-en-website-be24ef64f751f66aab832ef415496fc1e0d5405e3084bc0bc7be156db3671b43","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This page has extra spaces before the commands: I am not sure it's a more systemic problem, but this causes commands to not to show up on the bash history (undesirable). Proposed Solution: Page to Update: /assign\nA cursory look through the rest of the docs under Configure Pods and Containers showed that one out of four docs also had this issue. I'll make this change as I update the callouts."}
{"_id":"q-en-website-51038e62ec692514644fb5a5ee80edb5938a1ae998dd622e421a4616a3629d32","text":"This is a... [x] Bug Report Problem: The documentation mentions \"optional\" in the restrictions for configmap, but doesn't explain how to use it anywhere else in the documentation. You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as “optional”). If you reference a ConfigMap that doesn’t exist, the Pod won’t start. Likewise, references to keys that don’t exist in the ConfigMap will prevent the pod from starting. Please see for the feature. It appears it got lost in the 1.5-1.6 upgrade. Proposed Solution: Restore the copy from that wrote. Page to Update:\nFor clarity, the copy from got removed here:\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\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/language en /remove-lifecycle stale /assign\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/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\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 stale\n/remove-lifecycle rotten\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nRelevant to /remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nThis awesome feature is still missing in the documentation, Can someone please add it ?\nwere you thinking of opening a pull request? We'd be happy to help you with that.\n/remove-lifecycle stale\n/lifecycle frozen\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 it. Thank you! /unassign\n/assign"}
{"_id":"q-en-website-4afba6044ff3696b96a39858ca2f9b851d298aea89ca34755cae692a2d9246db","text":"This is a Bug Report This issue appeared recently within kubernetes/website. Links in follow the next pattern , see a square bracket inside of the . I tried to follow in order to find a source of the issue, but wasn't able to do so. my best guesses: Source for generation for 1_17 branch was corrupted. Backend was replaced by something else but not commited (i don't believe in this). This can be temporary content (on ein PR) as toolset for kubernetes-sigs/reference-docs .\n/kind bug /priority backlog\nping\nI am looking now\n, you are referring to a link problem in the reference? I don't immediately see a problem. Can you provide an example of a command that has a link issue? Thanks! I see a link that appears incorrectly formatted, such as the flag in the command, Though, the link does work for me.\nI plan on updating the build instructions and README.\nany link that follow pattern . If we ware talking about from the root of the kubernetes-sigs/reference-docs, it would be any link in usage block. Almost all of them are anchor links, so problem isn't visible at first. search for or , last symbol of the link is clearly not suppose to be a link (at least its not a link in source yaml) P.S. Is it worth time to update build instructions now? Isn't going to change generator backend to htmlwriter?\n, I have a feeling there is a miscommunication. I am not sure what you are referring to. I thought you are logging an issue specifically to the kubectl reference. Please provide a specific example.\nok. for on link to for on link yourself why is in link. diff for kubernetes/website (kubectl-) and see how links are formed. -become right bracket in the href attribute. P.S. just updated one of the search links as i forgot to copy/paste last element of the link (). P.P.S. looks like regular expression issue.\nI see. I think we are referring to the same problem -- the right bracket.\nShould I close issue or you prefer to have it opened untill kubernetes-sigs/reference-docs is opened?\n, I would leave this issue open as a reminder for next release. Thanks! NOTE: The links were manually fixed for the 1.17 release (search/replace).\ngot it!"}
{"_id":"q-en-website-7d3321bca9e7ebeb2f06ae54cd8f3fdd46cb18668a0bde460a9209f94135ca27","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 out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue\nI'll work on that! /remove-help /assign"}
{"_id":"q-en-website-2f3fd470287390ca4daf7fc8552bc81c59d253d1849029abbf7223f282e6082f","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 Revise to signpost new contributors to Why is this needed If someone arrives at (possible from ) and has not already contributed to the website, then it's good to let them know that there is a whole section of documentation aimed at exactly that target audience. Comments /language en /good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Revise to signpost new contributors to If someone arrives at (possible from ) and has not already contributed to the website, then it's good to let them know that there is a whole section of documentation aimed at exactly that target audience. /language en /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign\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"}
{"_id":"q-en-website-b03af1288239a27554e225d663d297caca72d26d6865e441ffc74a97aab45763","text":"This is a Bug Report Problem: The text unclearly says: \"Deprecated metric signal that the metric will eventually be deleted; to find which version, you need to check annotation, which includes from which kubernetes version that metric will be considered deprecated.\" (Note the problems, such as \"Deprecated metric signal ...,\" \"to check annotation,\" unclear references to versions (when metric will be gone, when declared deprecated, other?), etc.) Proposed Solution: Have a fluent English speaker (who knows Kubernetes) edit that. Page to Update:\n/language en /sig instrumentation\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/triage accepted\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\nI'd like to try a pass at this. /assign\nNot sure if I'm able to do this, but let's try: /remove-lifecycle rotten"}
{"_id":"q-en-website-e6f17f164eb2dc746e8cdbeb691b986404561b26de65c6273b27af551abc6a80","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: At Line 398, The link for \"Planning your cluster and worker node setup\" might seems to be changed from Proposed Solution: The link has to be changed as \"\". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en /assign"}
{"_id":"q-en-website-4a1ef23b76b1fa8a2dda1b77f1c7157c3a69759c3668216a92e3024627c5dddf","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: Glossary tooltip code for \"node\" shouldn't be in the short_description section. It doesn't display it correctly. Proposed Solution: Change it like original document. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Page to check:\n/language ko /assign"}
{"_id":"q-en-website-c61567fff240682de3bd42a6f74f485487c27753e007c77eedf8cf355cf49008","text":"This is a Bug Report Problem: missing double quote (\") after the word services in the last table Proposed Solution: Add the missing double quote (\") Page to Update:"}
{"_id":"q-en-website-f2bec3e57dc4a28e15acf85ac2963210cda2b8ac0476c09ffaf22a80b161833b","text":"I would like to have the \"Container Lifecycle Hooks\" page to be translated into Italian page /language it /priority important-soon\n/remove-priority important-soon /priority important-longterm\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\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\nHi I am taking this issue! :smile: /assign /lifecycle active\nthis can help (you can find specific instructions for the web-site) Ping me if you need help\nHi I have finished my issue! PR ! Let me know!"}
{"_id":"q-en-website-14ccad1c3859430e7cb0dd7e8f4e13280e4f08b474f28bdc82254ad431c9e596","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: This line includes glossary. However, the displayed content is glossary. ! Proposed Solution: The contents should be glossary, but I don't know how. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language ja\n/kind bug /priority backlog\n/assign"}
{"_id":"q-en-website-08364171f7d27265349cf00636a08885bc0c4712daa2d5e9e38400c31a966164","text":"At the quarterly planning meeting we agreed that we should update the PR wrangler document to be more relaxed about contributed PRs that are solid content but don't exactly meet to the style guide requirements. This was requested to help keep contributions flowing in since we are short staffed. I plan on making this update to the document.\n/assign\n/cc\n/kind cleanup /priority important-soon"}
{"_id":"q-en-website-5e2b0562e6c7d4d270937fe8ae84fccf84d87342c55540811cf24dbb3bbc2395","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: line 35~39, there are extra spaces(more than 4 spaces) in front of shell box. line 427~430, it should be a shell box. So, we need shell code. line 445~451, it should be a shell box. So, we need shell code. Proposed Solution: [1] : Specifies the . Resource types are case-insensitive and you can specify the singular, plural, or abbreviated forms. For example, the following commands produce the same output: [2] [3] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en\n/assign"}
{"_id":"q-en-website-b87f388b1ed154a6bf7fd69e904ee6761fd7bb4e232c1edc4bc29f886490c452","text":"Umbrella issue: Remove the following from L6-8:\n/assign inductor\n/kind cleanup\nOn it!\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-76b43ec3128db4e03509c83c7e0f74b4f0688d6accebfb2bd3973dc4d482ca7a","text":"Umbrella issue: Remove the following from L6-8:\n/kind cleanup\n/language ko\n/assign\nThis issue is included in also."}
{"_id":"q-en-website-2f51e4e40b518df89753cc3085d3a1db0a73b9a200f5549dd13700efb8a8fbc5","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--On the page: Under the section: Forward a local port to a port on the Pod This page suggests using kubectl port-forward to forward ports to your pod. However, kubectl port-forward does not return, it is not daemonized by default. The page does not note this fact Proposed Solution: Either: modify the page to indicate that kubectl port-forward will not return, and that the user needs to open another terminal window to continue with the exercises; OR modify the kubectl port-forward commands to include a & (ampersand) at the end of the line, so that the job will run in the background and return to the terminal prompt. 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\nMaybe adding a flag to is a better way to solve this problem, such as ?\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\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"}
{"_id":"q-en-website-8d02645812c9142efb3a93d45fff426d4fca45ccc56cab1290a540544f3e9043","text":"Problem: The 5 fields of the cronJob schedule format are not described on the page - there is only a link to some external documetation (). This documentation however is for a 6 field format which include an extra seconds field at the start. Also the use of in the examples isn't required because `` already means every minute. Proposed Solution: Linking to a page which describes the 5 field version of the cron format e.g. the Wikipedia page: Page to Update:\n/kind bug /priority important-longterm /language en"}
{"_id":"q-en-website-19fc1330b797d0e35b379d295daa29fcc534e9129b8451e00edc06684c2a0353","text":"This is a Bug Report Problem: The link (/docs/home/contribute/style/page-content-types/#concept) from the Concept page is not correct. Proposed Solution: Page to Update:\nThanks for spotting this. /kind bug /priority backlog /language en"}
{"_id":"q-en-website-e4336aaceecb10bff28e7e4901aba31385a97a4c620e9471b41cd71a66b089d4","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update to document that namespaces starting are reserved. Why is this needed According to all namespaces with names that start with are reserved. Comments /kind feature /language en /sig architecture /good-first-issue\nThis request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update to document that namespaces starting are reserved. According to all namespaces with names that start with are reserved. /kind feature /language en /sig architecture /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign me\nGitHub didn't allow me to assign the following users: me. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign me </details\n/assign"}
{"_id":"q-en-website-f718835a04443215e92db8ecc56ce7a84d6876e98dd9d9a1056e9adc9b68423d","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 Add a facility to search the website to the main page, Why is this needed Let's say someone arrives at and wants to find the download page. Well, the top 3 results on look pretty relevant. The trouble is there's no form on to do that search, and it's not obvious that navigating round the site will reveal that search. Comments Consider both desktop and mobile browser use cases. The main page is some readers' first impression of Kubernetes, so it's important to make a good one. Most people known how to use Google (other search products exist) so fixing this need not be a priority.\nI think this dovetails with as well. From an implementation perspective (from what I can tell) the site uses a custom google search engine. First step would be identifying who the admin(s) of that are. Second step would be identifying what directories are scanned Third step would be including the pages we now want to include. Fourth step is fairly easy – add to the layout template you want to see a search box on. The third step requires some thought, however. If we put a search box on the homepage, is the expectation that it searches the entire_ site or just the docs+blog? From a UX perspective, if I see a search box on the homepage I kind of expect it to search everything.\nThe site search already covers the whole site, so this is really about adding a form to the front page.\nFor an example of where to put a site search on the main page, see (I'm not proposing to move the search UI there across for the whole site; that would be a separate issue).\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\nAlso relevant: issue\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\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\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/remove-lifecycle rotten /lifecycle frozen\n/triage accepted\n/area web-development (ish)\n/priority backlog\nI'm more than happy to work on it and get this moving forward. /assign\n/assign"}
{"_id":"q-en-website-c71a8f405f5293cc7a583f0da67b4603d51c0636ad459431eef31cebe4bb403e","text":"Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.\n/assign /kind cleanup\n/language en"}
{"_id":"q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e","text":"This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /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-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb","text":"It is very difficult to find any links to the . This is a huge roadblock to new users trying to do anything custom with kubeadm. As a new user, I don't expect to have to read about to find information about configuring the tool. To someone who is unfamiliar with the project, that seems like more advanced documentation than I should need, and therefore not somewhere I would expect to find basic config file documentation. I also was able to find the long before I found the more user-friendly documentation, which made it seem like that was the only documentation that exists. I would expect a link to those docs to be available on the kubeadm-config page, as well as where config files are mentioned in the kubeadm-init and kubeadm-join pages.\n/language en\nit seems you have missed these two sections: and for these commands the kubeadm API is actually the most important for. linking the command line reference page to the API makes sense. but instead of linking to a particular version of the API we should link to: and let users navigate to a particular API version. this is done with the idea that can also migrate v1beta1 -v1beta2. PRs welcome. thanks /sig cluster-lifecycle /priority backlog /help wanted\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:"}
{"_id":"q-en-website-5a9a940eec7ec3e6b61c02ff80b216559252e70cfa652952117cc031dcc8d3aa","text":"/language zh\n/sig auth\n/remove-sig auth /assign\nIs this not SIG Auth?\nBy mentioning 'SIG Auth', we mean we want members from that SIG to help review the localization. For one thing, I'm not convinced that will happen. For the other, such mentions are distracting that SIG's attention on PRs which needs their feedback."}
{"_id":"q-en-website-7ae92f761b610feaedf70a069ceb4cb507422b24300789180ed26f65662c8a47","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. --Document Volume and Claim Pre-binding feature. Why is this needed PVC & PV pre-binding is useful sometimes, but this feature is not documented in our official website. It's better to add a topic or subtopic for it. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\n/sig storage cc /assign working on it"}
{"_id":"q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350","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\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"}
{"_id":"q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e","text":"This is an enhancement Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. It is also OK to replace this page with a hand-written overview that achieves the same effect. Why is this needed ReplicationController is deprecated. Comments You can make this change by editing the attribute in the of pages inside . /language en /priority backlog /good-first-issue /kind cleanup\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 an enhancement Request <!-- See for guidance on writing an actionable issue description. --Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. ReplicationController is deprecated. You can make this change by editing the attribute in the of pages inside . /priority backlog /good-first-issue /kind cleanup Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nJust the order of list needs to be changed to list Deployments and then ReplicaSet early and ReplicationController at the end in the , right?\n(and to anyone else) you can make the minimal change you described, or you can consider further tidying. Either approach is valid; if you like, there is a spectrum of thoroughness in how you deal with this.\nOh, I've fixed the link to front matter; it should be to\nHey folks, I can take care of it if OK with that.\nSure you can go ahead!\nThanks! /assign"}
{"_id":"q-en-website-01010a6817889a9d5adf5c2a2d5762fd31162dac42b2962e212a1b80985f4eca","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 remark that mixes up two issues: is not about , rather it is about . even actually relevant to kube-controller-manager? Ayodele Abejide and I can not see any relevant for it (). 1350 looks like a show-stopper for this recipe. Proposed Solution: Fix the recipe. Fix issue 1350. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/sig auth /language en\n/kind bug (seems valid to me)\nNote: Remove the flag --client-ca-file from the Kubernetes controller manager configuration. You can also replace the existing client CA file or change this configuration item to reference a new, updated CA. Issue 1350 tracks an issue with Kubernetes controller manager being unable to accept a CA bundle. i think the problem that --client-ca-file and --cluster-signing-cert-file flags share is that the KCM does not allow CA bundles for both of them. this also implies complications around this guide. the kubeadm ticket is noisy and i don't think it should be linked from this page. note that the step above mentions: Update Kubernetes controller manager's --root-ca-file to include both old and new CA and restart controller manager. at that point if the same file is a bundle the KCM would just error out because of --client-ca-file, thus the recommendation about removal or making it point to a separate CA. used for client certificate authentication to allow clients to validate the signature of the serving certificate. the KCM can still be served over HTTPs. i guess not if the flag is removed from from the KCM, until the old CA is removed from the bundle at which point the flag can be re-. i think there are wider problems here and we should have an issue in k/k tagged with sig/auth that tracks progress on the KCM supporting bundles. i've seen mentions around this being worked on here: the note in this document needs clarification: it should link to the k/k issue, if one day the KCM --client-ca-file supports bundles it should explain why the flag is being removed and what are the consequences of doing that (e.g. MITM?). should the flag removal be temporary until the bundle no longer has the old CA? cc\nIn my opinion, the flag is still needed, when I tested the recipe there were 2 problems at the start, one from and another from , that when I found to be problematic, the point that later only got caught when I removed chain from . That's why I included this in the recipe, that we should either remove it or replace it with the new CA, whichever fits the need cluster to cluster basis. It doesn't makes it show stopper but, yes, I agree that the page needs a bit reword in the paragraph to make it less confusing for people following it.\nPS: Just in case someone wants to re-validate, the error I was getting with with old+new CA certs was similar to \"certificate signed by unknown authority\" and stopped when I replaced it with only new CA. So it was more like the first bundle in the chain was accepted but the newer one did not.\n/priority awaiting-more-evidence Please feel free to /priority some-other-value and /triage accepted if this is confirmed valid.\nwould you like send a PR to amend the paragraph? EDIT: NVM i've sent the PR here, PTAL:\n(sent the PR) /remove-priority awaiting-more-evidence /priority backlog\n/triage accepted"}
{"_id":"q-en-website-6efc396e133370d32267c3ba7aa78436476070477ed5a86db3a1f5c213fe1ceb","text":"This is a Feature Request What would you like to be Translate docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign"}
{"_id":"q-en-website-f75f3e286dd9913351f125cba4a923934d4fc31a459f4212e057e685142d01b5","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: can be set to any value, but . If it's set to any value less than 10s the CronJob will be never scheduled. Proposed Solution: Force the value to be always greater than 10, or warn people there are non-working values Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 1.15.12\n/kind cleanup /language en /triage accepted\nThanks\nRelevant to\nI recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. Specifically I would add a callout, with text similar to: /good-first-issue /sig apps\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 : I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may eventually honor any setting for ; however, we want to document the shortcoming right now. if is set to a value less than 10 seconds then the CronJob may not be scheduled. /sig apps Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign"}
{"_id":"q-en-website-401f86e97ec17e3bb2ffb3cc118b0ae93bf660c4d58289d42712cfee5cb589c8","text":"This is a Bug Report <!--Required Information--Problem: In Dualstack doc updates for 1.18 , it only removes IPVS prerequisites in but not remove it in , you still can find \"Kube-proxy running in mode IPVS\" in the doc. Proposed Solution: remove \"Kube-proxy running in mode IPVS\" in Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en /priority important-soon /kind bug – Can you verify the issue described is correct? If so we can tag it as a good first issue and have someone tackle it.\nHi and Thank you very much for raising this. I can indeed validate that the issue is correct and that the proposed solution is correct and would be more than happy to review a PR if someone would be happy to contribute. Thanks again\n/assign\n– no further action from you needed, this was a small fix. Thank you!"}
{"_id":"q-en-website-8da9faf21cf67d48887517c4e9a62fa4fe99cbeb8cc8645276f0f615ca4d96f8","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/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-5e853c722cb5be1f3f49920c218f61ec7d946ba811cae76193f24d9e8f33ad75","text":"A page just to provide a link another page? My be you are planning more links on this page. If not this page it self can point to target page.\nHi in this there is another link reference to kubectl commands refrence , so far i am understanding is that you want to replace reference Link for kubectl command to be in this ?\nTo fix this, edit  so that it redirects to /good-first-issue /language en\n/triage accepted\n/retitle No page content for\n/assign\nhi could you help to review the PR? Thanks\n~reviewers~ approvers for the English localization (who are mainly volunteers) pick up that task on a . I can take a look though.\n/remove-good-first-issue\n/assign\nI the redirect () but it doesn't seem to be working on the deploy preview or locally. Any advice would be appreciated:"}
{"_id":"q-en-website-6b73162eaa6e8a5d74c0e5c4b16ce18491508ee547cf7dd90a96da5771dd6e73","text":"/language zh /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 : /language zh /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted"}
{"_id":"q-en-website-4321a1db43bbaf244c2de3212770e68af14b179c6edc9df7569804a6965ed9e3","text":"/language zh /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 : /language zh /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\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-a156808cbb38a820c7cb79522ab318fd7db288080800eb31a33cf787a755b20c","text":"This is a Bug Report Problem: The following pages under are currently manually maintained. It is expected that each generated page under has at least one link to it from these files, otherwise it becomes orphaned. The following pages are orphaned: Proposed Solution: Add links to these generated pages.\nThanks /sig cluster-lifecycle /triage accepted /kind cleanup /language en /priority backlog\nWe could instead use Docsy's automatic list generation, and add descriptions to each page (eg, to the front matter of ).\nis marked as deprecated in 1.20, so i assume the generation for it will be skipped (the command will be hidden). the command is graduated as . the graduation and missing is covered here: the rest are indeed missing. is there a way to catch this during CI of website PRs? i don't know how Docsy works, but would appreciate ideas around this as manually maintaining the subcommands is not ideal.\nHmm, looking at this a bit more just setting a might not be enough. The current pages are a mix of generated and manually written ones. There are a few different ways to combine these. It sounds like extending the generator could help there - that could be a separate feature request against the generator code, eg to warn if a subcommand isn't documented as expected.\ni think we could do the following: on the main pages that are currently manually maintained for etc, \"include\" the parent generated page () the generated page could have relative hyperlinks to the generated pages of sub-sub-commands (e.g. having links to , and this can reveal the whole tree relation between sub-commands and sub-sub-commands (and deeper). this means that ideally the generated pages should have a title on top too: and a section for the sub-commands. EDIT: and if the kubeadm commands lack sufficient information it should be in the source code of kubeadm. would navigating around /generated pages sound like a good idea? e.g.\nthat sounds like a plan. BTW, if the generator has the smarts to add metadata into generated Markdown (eg: a YAML list of subcommands, in front matter) then we can implement a Hugo layout that automatically processes that metadata into HTML. I can probably help with this approach, if selected. So you have options: more code in the docs generator, or less docs generator code but then more work for the Go templating.\ngiven the subcommand relation is already described by the filenames: can Hugo just process that instead of requiring the metadata to be part of the markdown? i think i'm leaning towards the first option, but that is because i don't know much about Hugo. if the docs team and prefer the second option, we should go for that.\nI'd rather not hard-code in a full path into the layout code, because I think that could be fragile when it doesn't need to be. If we can set some marker eg in the for each page where that applies, I think I could persuade Hugo to work out the rest of the details.\nLet's fix it by following the current practices. We can file a new issue to track the improvement/automation.\nLGTMed the PR, will add notes to thanks"}
{"_id":"q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72","text":"I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /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 : I think that an appropriate improvement that's in line with your comment is to change to run instead. /language en /kind cleanup /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/retitle Multiple way to refer to Deployment resource confusing in Deployment concept page\n/assign"}
{"_id":"q-en-website-4fdda25e0c05378b3e540313cc61cdcc39ecb037f571b22f8815a35543d5560e","text":"translate into Chinese\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 /language zh"}
{"_id":"q-en-website-26575fa3dd263ae8230e52acb79ae6cd37dda955d2011325f178019dd3597f70","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 page about performing a particular task, but it lives in the Concepts section. Tasks should be in the tasks section. Proposed Solution: Change the title of the page to “Garbage collection for container images” Hyperlink from within to the page (remember, this PR will just cover the English localization) Page to Update: Additional Information: /kind cleanup /language en /sig node /help Relevant to issue It is OK to clean up the content of the page beyond what this issue describes. Check whether it makes sense to remove the section. This could be because we or because the information is out of date.\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 Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: is a page about performing a particular task, but it lives in the Concepts section. Tasks should be in the tasks section. Change the title of the page to “Garbage collection for container images” Move the page inside Additional Information: /kind cleanup /language en /sig node /help Check whether it makes sense to remove the section. This could be because we or because the information is out of date. 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\nNo. I don't agree to this movement. The reason is that garbage collection is an administrator job. However, is mostly about concepts an end user need to know. If needed, we can add links to make sure users can learn what's happening behind the scene. Page movement like this is harmful rather than helpful.\nI've revised the issue description /retitle Retitle “Configuring kubelet Garbage Collection” and add incoming links\n/assign\nTo confirm, the goal of this issue is to: retitle the GC concept page (not move the page or retitle the file)? link from the containers concept page to the GC concept page\nNote: I found 2 Garbage Collection concept pages: The \"cluster-administration\" GC concept page focuses on the kubelet flags. This page is not listed in the \"cluster-administration\" index page. Could the index page list the GC page under the \"Managing a Cluster\" section? A side note, where is defined?"}
{"_id":"q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890","text":"Nginx https 404\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\nHi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information"}
{"_id":"q-en-website-7e7e2dd21679b1368c732867d816c4506e8e407dcadec6fed3c1629e01cb2c9f","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: ! ! Proposed Solution: Page to Update: <!--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/kind bug\n/assign"}
{"_id":"q-en-website-a2b8642adc8f2889b5df544f5c34c4dd888e048b89c47eafad6f1454d44ef5b3","text":"It‘s Content have no change from following link:\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nhi, can you better explain the problem and re-open the issue after that? thanks /sig docs cluster-lifecycle /priority awaiting-more-evidence /close\nClosing this issue. <detailsIn response to : hi, can you better explain the problem and re-open the issue after that? thanks /priority awaiting-more-evidence /close </details\nAfter some testing and guessing, I think the problem is that the fancy tab list on the install-kubeadm page doesn't work for people from China. The reason behind that is the \"\" is not loaded by the browser. The damn firewall blocked the site used for serving bootstrap JS module. Back to the website, I can see the script reference comes from , which can be overridden. Maybe we should do that because we already have one cached () which is a newer version.\nthis seems like a good idea. /reopen /retitle tab list component should use the cached bootstrap-\nReopened this issue. <detailsIn response to : Back to the website, I can see the script reference comes from , which can be overridden. Maybe we should do that because we already have one cached (static/js/bootstrap-) which is a newer version. /retitle tab list component should use the cached bootstrap- Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nYes, I cann't open this link() from china.\nThe problem is that switching tab page from ubuntu16.04 to ubuntu 18.04/20.04 content no change. access this link failed."}
{"_id":"q-en-website-7c88f86de42344238abc46551b48f3b8481150cc50799f122aca757899b3184c","text":"command: wget \"-O\" \"/work-\" : command: wget \"-O\" \"/work-\"\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\nwhy?\nsync from en"}
{"_id":"q-en-website-bff413ca3ae681003cef26f5589e114934acce773adcc4c1158b6b9c5f5ad6a3","text":"This is a Bug Report <!--Required Information--Problem: It appears as if the Secret documentation references a feature that isn't currently implemented. Specifically, it includes the following: Prior to this was accompanied by the text: However, PodPresets have been dropped from Kubernetes. Accordingly, this section should reference a different mechanism to achieve the same goal if such a mechanism exists. If it doesn't it should be dropped. From my research, it looks like no such alternate mechanism exists. In another previous revision of that section, the section read: states that PodPresets should be used for secret automounting. It does not mention other options. It also does not imply that ServiceAccounts are relevant. It seems like the ServiceAccount association was back around 2015-2017. Proposed Solution: Unless a mechanism exists which associates Secrets with ServiceAccounts for the purpose of automounting Secrets in Pods associated with a specific ServiceAccount, this section should be dropped. If such a mechanism does exist, the section should be updated to reflect its use or refer to other docs that do. Page to Update:\n/kind bug Relevant SIG is SIG Service Catalog, but anyone can tidy up (remove the mention of PodPreset). /triage accepted /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 : /kind bug Relevant SIG is SIG Service Catalog, but anyone can tidy up (remove the mention of PodPreset). /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"q-en-website-5fc9b5e9c0b0d2daac9cfac50d795a95e840e6b3a3ae5a8b45a57f91c652fdee","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-5a512241392474648e1b72fdb21fe7506594ed4b93f6f47589a6604a498224ca","text":"This is a Bug Report Problem: The dockershim alias () now directs to the Chinese localized version () because the same alias exists in multiple files. Proposed Solution: Removal of the alias in the Chinese version of the blog post or updated to be A policy or linter might be worth putting in place for aliases as well to prevent future issues. Page to Update:\n/triage accepted /kind bug /language zh\nA similar problem occurred some time ago with aliases in security. I just checked a few other files. Aliases field is set: content/zh/docs/reference/issues- content/zh/docs/reference/issues- Aliases field not set (set in version): content/zh/docs/reference/access-authn- Should add a note to the localization or documentation about how to update the field.\n/assign"}
{"_id":"q-en-website-ea1cccfc179c7a487297c9253d39ff7efdebafa1ecbfeb4b22e29011021468f5","text":"doc address: The link address is invalid after the field is clicked, return http code 404  SORRY /  /  This page does / ] not exist yet. [ ,'| ] [ / | ] [ ,' | ] ] /[ [ ] ]  / [ [ ] ] ] [ [ [ ] ] ] [ [ [ ] ] ] ] /[ [ [ [ ] ] ] ] (#) [ [ [ [ :====' ] ] ]].nHn.[_[ [ [ ] ] ] HHHHH. [ [ [ ] ] / `HH(\"N  [ [ ]]/ HHH \" [[ ] NNN [ ] N/\" [ ] N H [ / N  / q,  / \n/assign\n/kind bug /sig storage /priority backlog /language en /triage accepted\n/reopen\nReopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\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\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-c85df5a0fe24baaae76f1bb451f33522fddbd55e607b7b12f3aac07bd641dd4e","text":"! Chinese page link can not open\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\n/kind bug"}
{"_id":"q-en-website-98a66d2d724672a8819406347a82a8cd743af3be7c91974086a6a2cbc0026c80","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page https://v1- explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.20.x to version 1.21.x, and from version 1.21.x to 1.21.y. (Should be from version 1.19.x to version 1.20.x, and from version 1.20.x to 1.20.y.) Proposed Solution: In Replace =- =- ... Page to Update: https://v1- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign\nI think we should fix the shortcode to use the documented version, rather than the most recent release. /sig cluster-lifecycle /language en\nthe intent behind seems to be misleading if is fed at build time pointing at the latest current k8s version. while extending the latestVersion shortcodes i expected to be static and hardcoded per k/website release branch. i can send PRs for this but i'd need to understand more about the \"documented\" version that you mentioned. i.e. making latestVersion fixed to 1.20 in the 1.20 release branch seems reasonable to me.\n^ for additional opinions.\nDespite a misleading name, is supposed to use not . AIUI.\ni can see is being used in a few places: should all of these be modified to use or only the shortcodes in ? and for which branches - and ?\nis useful, it does represent the most recent release.\nok, i can PR the change for 1.20, and master since this is only a problem for the kubeadm upgrade docs. is also used here, but the versions there are just examples. https://v1-\nhere are the PRs:\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\n/remove-lifecycle stale\n/triage accepted\n/priority-important longterm\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority-important longterm Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/priority important-longterm"}
{"_id":"q-en-website-b307b0abb8b5d4cf1bf1a69869d3b98b1a3e16953279e3b03d8df71a2919c666","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 is broken. Proposed Solution: In Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/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\nalready logged here: /close /sig cluster-lifecycle\nClosing this issue. <detailsIn response to : already logged here: /sig cluster-lifecycle 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-6ff6e751e652c98c4d3a37f23271dd8f8c25fd972041a1c701d83de3f5b4e54b","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 exist bugs in . [Part number 1] [Part number 2] Proposed Solution: [Part number 1] [Part number 2] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/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\n[As-is] [To-be]\nHello . Note: The release notes are auto-generated. What do you think about logging an issue with the release team (release notes)?\nHi Following your advice, I posted an on . Thank you!\nrelease notes team here. yes this was autogenerated but we had to make manual fix to k/k (ref: ) a few days after the official release went out. i think it's the right move to fix it here as well"}
{"_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-c9270b65e4e4ea37cea789ac98a60a55cac6c6e677afe2b9382036a5e7b8a6a2","text":"This is a Bug Report concepts page for spanish links doesn't take to spanish pages <!--Required Information--Problem: The page is the Spanish translation, the links on this page should take you to the Spanish version of the link when available, if not available then ok to leave it pointing to English Proposed Solution: Update the page links to point to Spanish version (ie. es) Page to Update: I intended to review and submit a PR\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/language es\n/assign\n/assign\nThanks for the report, this is quite common as the translation is a work in progress and we don't have (yet) a way to easily detect where a page is referenced. Let me know if you have any issue working with the PR.\nI will work on this page as one-off, and think about how can we automate the detection for all links that should point to the Spanish version.\nMaybe something that can be done at build time? Don't know how is the site is build I guess Hugo but not how much pre-processing is done"}
{"_id":"q-en-website-77c3fc9e2e9391e5e015b7c9f18cdc0b6a49a751030e056a2e4eead533148014","text":"lists RemainingItemCount as alpha but shows it went beta. /kind bug /language en /sig api-machinery\n/triage accepted\nWhat was the version when it was promoted to beta? (The PR seems quite old). Was it if I am not wrong? /assign"}
{"_id":"q-en-website-c39ee55ba0b4cece4bbf57571f6e8923268277ef57bdaa932a5ad6b299eb2e4f","text":"This is a Feature Request translate /docs/tasks/administer-cluster/enabling-topology-aware- into Chinese. What would you like to be /zh/docs/tasks/administer-cluster/enabling-topology-aware- /language zh /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"q-en-website-526c7ae8a5989f0b4441532f28ef37c4493153e2b2e8ad6d6d8b8f3cfeb16f1c","text":"A on is broken and returning 404 page.\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"q-en-website-be366a0e7e3d1c9e6d77b30acb963348724f104cbaeab0a8da44d0628e8e6f07","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 , when user clicks , ! user lands on , which is for KubeCon & CloudNativeCon North America 2021. Proposed Solution: In , [As-is] [To-be] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en\n/triage accepted"}
{"_id":"q-en-website-1543bba1973f0dccb84c0c844fc22a0409a6a9c3aff67089d40f25fe5dbff77f","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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign\n/triage accepted"}
{"_id":"q-en-website-634adeb6a1b405c8af18d5fd7154643068b57f40554a956648b2a2ffb304e5ba","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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. 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\nI would like to take up this ticket."}
{"_id":"q-en-website-f09b1645624007de341f2e3b96af7e2df5812ad7ac689ef228f9fc2332f17d08","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 , sub-items are not displayed in sidebar tree. ! FYI Chinese version: ! Japanese version: ! English version: ! Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nzh: Some Chinese-translated files exist in ko: No Korean-translated file exists in I guess this is the reason why the sidebars of version and version are displayed differently. FYI: On 2021-03-19, the -version sidebar was like this: (screenshot is from the issue ) Even if no Korean-translated file exists in , sub-items are displayed (which are the links to the English version of subcommands). !\n/triage accepted\nThis will affect all localizations /priority important-soon\n/retitle [l10n] Sub-items are not displayed in sidebar tree\n/area web-development\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]:\nCan I work on this issue?\nSure! Please go ahead! /remove-lifecycle rotten\n/assign\n/lifecycle frozen\n/unassign\n/assign I'd like to take a look at this\nTo summarize: Localizations should have the same links listed in their side nav as in the english language docs, regardless of whether the pages have been translated. This is because there is a \"fallback\" set up to display a link to the english language docs if a page has not yet been translated. The fallback links to english docs for generated reference docs (kubeadm docs) are missing in localize docs sets. (or anyone else), does this sound accurate? I'd like to make sure i understand whats broken before trying to troubleshoot hugo/docsy/mystery code section :)\nI've been spending time investigating this and learning how the navigation is built :) I believe i've found the issue. I'll try to summarize below, but I think this is a template issue which should be addressed by docsy. There is a check in () that compares all the pages and sections and then filters out pages that have . We then test for the number of child pages, to determine if we continue to build the next level down in the navigation tree. At this point, because some localizations have the Kubeadm page translated, this check will only find the translated file (files in the kubeadm/generated folder are filtered out bc the file has ). The logic as written determines that kubeadm has no child pages, because it doesn't know about the English pages at this point. This means the rest of the kubadm sub pages links will not be built in the navigation. Theres There is a check later in that merges the localized pages with the missing the English language pages and to inserts links to untranslated pages in the side nav. (). But it only gets to this point if there are child pages, because its wrapped in a conditional (). In my testing i the checking for untranslated pages, replacing lines 49-51 to be the following. This appears to add in the links that were missing. <img width=\"1569\" alt=\"Screen Shot 2022-09-09 at 11 27 38 AM\" src=\"https://user-\"If we agree that this looks and is a docsy issue, I can open an issue there and propose the solution. cc: I would appreciated your thoughts on this, thanks!"}
{"_id":"q-en-website-a1db360be651aafe95f4fd8fe6d7c0ee9fc36337cda5ed4c617c91368c09585a","text":"Affected page: Move this page from Concepts to Tasks (potentially under Tasks Networking). Update to redirect the old URL to the new location (use a 301 code, similar to other entries in this file). /sig docs /language en\n/triage accepted /help\n/remove-help\nI'd like to work on this one to learn something new in website page organizing. Thanks. /assign"}
{"_id":"q-en-website-15474e2a544d42f35d55b4a54b4595a167afd2c5b246e6f569319bcc7702b3d5","text":"What would you like to be In Seccomp should link to instead of Why For a better understanding of how Seccomp works in k8s. As Seccomp is stable fetaure in k8s.\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\nFixed it here"}
{"_id":"q-en-website-e34093bba3db13b222938482d29cd031aedd7b97c833318fb7130475d92462f8","text":"Document's section: Currenty it says: Kubernetes creates one PersistentVolume for each VolumeClaimTemplate That is not wrong, but not exact. What about replacing it by something like this: Per each StatefulSet triggered pod Kubernetes creates a PersistentVolumeClaim object for each VolumeClaimTemplates entry defined in the StatefulSet object /language en\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI would like to work on this /assign\nHi i have raised a this.\nThanks ;-)"}
{"_id":"q-en-website-c93fb4d7eff6cc5d3f448751af75a21ba6b1b18e7ea2a4c241ecdffce8b82148","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 saw by accident very big page files on Kubernetes documentation. For example is lines long and the lines 286- are taken for the sidebar menu containing a lot of whitespace (do right-mouse and \"view page source\"). Proposed Solution: I reported the issue already with Docsy: and proposed a pull request. But this will not be enough. Somebody has to update too. 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/assign\nThe hugo Docsy theme side issue is resolved and closed: When will somebody review and implement pull request ? You can do this separate from a Docsy theme update at It is only about (huge) whitespace reduction, not a functional change. But k8s website users will benefit in user experience."}
{"_id":"q-en-website-7903097305e6ea169afd0e65fec18385d832ae780e6312ba8b2abd7f67f7c5c5","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 statement seems grammatically incorrect due to missing \"on\" after \"information\". Proposed Solution: -Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--/language en /good-first-issue <!--Kubernetes Version:--<!--Additional Information:--\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: The statement seems grammatically incorrect due to missing \"on\" after \"information\". /language en /good-first-issue <!--Kubernetes Version:--</details\n/assign\n/sig cluster-lifecycle /triage accepted"}
{"_id":"q-en-website-3ddabc97b64beb2129ce4114521bc76a75636e727501009178e1bdb79848e4e9","text":"According to the : this feature has been graduated to GA in 1.22 The doc still indicates:\n/retitle Incorrect feature state for Server-side Apply /kind bug /language en Which page is wrong, ? Can you provide the URL for it?\n/wg api-expression\nI think the page is /triage accepted\n/assign"}
{"_id":"q-en-website-121d19e2df240b809749eaf933eb4d7c45ba6e09ca2ab7d917fc01d779d797e6","text":"This is a Bug Report Problem: The konnectivity docs: Include the following instruction: Setting to doesn't seem right: This will break authentication for all tokens that use the default audience value (taken from the value), which is most tokens. This will allow tokens with in them to authenticate directly to kube-apiserver. I don't think we want that. Instead, we should just depend on konnectivity-server specifying the right audience in . Also: is unlikely to be a valid value for . In practice is typically an URL. Proposed Solution: Instead of including incorrect flag values inline, just link out to the correct documentation at Page to Update:\n/triage accepted\n/assign cheftako\nGitHub didn't allow me to assign the following users: jkh. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign jkh 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 jkh52\n/cc\nHi thanks for pointing this out. I just wanted to link this issue with the unfinished discussion in BTW, wouldn't it be more correct to specify both audiences: - where is value for the cluster Please correct me if I'm wrong but do you suggest to specify already existing audience for konnectifity-server, eg. this one which is used in kubeadm clusters by default: - where is value for the cluster Agree on that. I have the following setup in my project right now: I'd like to change it to be more correct. Based on said above. I suppose we have few more options: All three configurations are working, now we need to choose the most correct one. Of course we can link to the documentation page, but as for now it has no any usable examples to allow user simple start using this. I'm not big fan of leaving user without proper examples because they will just start using random configuration which works. Let's define correct defaults instead. Other services (eg. istio, vault) can rely on this configuration snippets as well. From my point of view option C is the most correct, what do you think?\nThe audience is meant for the konnectivity server, not kube-apiserver directly, correct? In other words, seems like those tokens should require proxying through the konnectivity server, kube-apiserver shouldn't accept them directly? ( this was the impression I got in our offline conversation - did I get that right?) I'm suggesting we can probably just leave unset and let it inherit from .\nThis is what I'm proposing:\nOkay this is option B, but this way we would need to configure konnectivity-server with the flag: And konnectivity-agent with the volume: would it be correct configuration, or maybe better to use separate audience (option C)?\nMy current understanding is that we can use , since the konnectivity-server can tell kube-apiserver which audiences to validate against when it makes the request, and those apparently don't have to match kube-apiserver's :\nI agree that we should link to the canonical documentation for setting up service account token issuer vs copying it here. These are now required flags so widespread adoption is imminent. We should leave Konnectivity server configured with . This means that Konnectivity server identifies as and will only accept tokens that are meant for audience . We shouldn't add to kube-apiserver, because we don't want kube-apiserver to accept tokens meant for connectivity server. Looking at the other docs, we likely don't have enough documentation on how to pick a value for . isn't great. is slightly better. Ideally, this is a globally unique URL (i.e. no private DNS or IPs) that supports OIDC discovery. In GKE, this is something like for in project in location . EKS is something similar.\nOh, got it! I don't remember exact reason why I started using this flag, but I just checked and confirm that it is working fine without it. Suppose it was just a configuration mistake. I'll prepare PR to fix this.\n/assign\nHi, I was copied in. How can I help?\nyou're member of , we need an approval for to get it merged.\nBest thing usually is to contact the if a review is urgent / not happening. Although, this week I'm sharing cover for that. So, consider me informed. I'll take a look."}
{"_id":"q-en-website-806f20bac8ba9503d1da4047a34313a5f72f6f9a6fc9333b8837f0f000b31904","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: Certain pages have the document.querySelector(\"body div.container-\") element rendering much too wide. The header/nav is the proper width. <img width=\"1458\" alt=\"Screen Shot 2021-11-15 at 11 19 42 AM\" src=\"https://user-\"Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--N/A <!--Additional Information:--Microsoft Edge Version 95.0.1020.40 (Official build) (x86_64) MacOS 11.6\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-1e5d91c431d5004e8d06000ec65fe4f432e2aed2540790b068f2b85741c09742","text":"links to the wrong Anchor for the CSI Provisioner. It links to #csi-provisioner but should be linking to #vsphere-provisioner-csi Also the link referering to the vsphere CSI repository in delivers a HTTP 404 Status.\n/kind bug /language en /triage accepted\n/assign"}
{"_id":"q-en-website-74f13ca48d219465d3dd13042145897405c776dcab7d93606e0895b9d5588049","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 docs for  say that this label is set on namespaces when you enable a feature gate, . However that's no longer true. In current Kubernetes the control plane always sets that label on namespaces. Proposed Solution: Reword that section to make it clear that the control plane always sets that label Page to Update: Kubernetes Version: v1.22 Additional Information: /language en /kind bug /help /priority backlog\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The docs for  say that this label is set on namespaces when you enable a feature gate, . However that's no longer true. In current Kubernetes the control plane always sets that label on namespaces. Reword that section to make it clear that the control plane always sets that label Kubernetes Version: v1.22 /language en /kind bug /help /priority backlog </details\n/triage accepted\nHi, I would like to work on this issue. /assign\nAny questions about how to fix it?\nI have a few technical questions: the sets the label on the namespaces instead of enabling the , so there would be no role of K8s API server in this process? will the set label on the namespaces? I mean will it do it automatically or we need to do something to set the labels like enabling something?\nThe API server is part of the control plane - see The component within the control plane that sets the label isn't a detail we need to specify here. All we need to mention is that it happens, and phrase it to make it clear it's not optional.\nJust to be clear that the will set the labels of the namespace and this setting of the labels is compulsorily (i.e. it is not optional).?\n(also, we'll get the API Machinery folks to check technical accuracy anyway - it's not on the docs contributors to thoroughly verify this kind of detail).\nOkay thanks . I now have an idea on how to fix the issue, I will file the PR soon :)\nI have a doubt: The phrase which tells that ,would it be better to included it as a shortcode or it should be kept as a normal text.?\nthe best way for folks to review your proposed changes is to open a pull request. (Also: anyone else who wants to work on this is welcome to - please liaise with if that's feasible).\nI have filed a PR but if anyone wants to work on this they are welcome to share their suggestions in the PR Conversation. Thanks."}
{"_id":"q-en-website-51bc6d9464fa510991803542aa6571f7df57aa29014137f3b031ab067d1482be","text":"Why not use PowerShell Get-FileHash instead of certutil for getting/checking file hashes?\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues 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\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]:\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: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:\nClosing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. 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 closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] 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/remove-lifecycle stale\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\n-- makes sense. I've raised a PR here -"}
{"_id":"q-en-website-c61fb9a9e4eeb9161a6e345e4c41fd7a63a53100d6958b9d64ae9b60f8a380ea","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 page , there exists a section \"Accessing services running on the cluster\". When someone clicks the hyperlink in that section, it goes to again. Proposed Solution: I guess that the hyperlink should go to . Page to Update: https://v1- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign\n/triage accepted"}
{"_id":"q-en-website-61ab1a83c47aa3d17cd7ab97b629d6c8bd3b657be571ef7a687aa70db7cc9faf","text":"Ref: The page is centered around Docker examples and needs a rewrite in light of the Dockershim removal. /triage accepted /milestone 1.24\n/sig node\nHi, I would like to work on this but I may need a little help. When we say \"rewrite in light of the Dockershim removal\", does it just means removing the Docker references on the page ( i.e removing \"\" on this page) or something more is expected.\nThanks for taking this on. In my opinion, there are two issues to deal with here. The first is easy. Change \"Docker image\" to \"container image\". I believe the second instance refers to a legacy Docker feature called . I think it is safe to just remove that sentence.\nThankyou :) I'll make a PR by tomorrow /assign"}
{"_id":"q-en-website-9e07a14a27fe3e829c55169cba45a7548f69294159139b2202c92290ec7c9cba","text":"cc: Task docs referencing how to check if dockershim removal affects users to be to the discussions. Link to be : (/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)\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\nIssue raised per\n/sig docs /language en"}
{"_id":"q-en-website-a8de3f81396a90bef148f0ae3faafd37a69561ac99f55ecbe1ee98f58c957805","text":"This is a Bug Report In /content/zh/includes/user-guide-content- I think it's better to translate \"user guide\" into “”\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\nFile: /language zh\n/assign\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/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/language zh /kind feature"}
{"_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-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29","text":"There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\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 /kind bug\n/assign"}
{"_id":"q-en-website-c440581b2df3ea77f2d772b74751bc635d26f72c9a0993ca90840200713f92fd","text":"This is a Feature Request Our workflow has been a great way to meet our commitment in keeping PR numbers at a manageable amount. We've recently introduced a way for new contributors to understand the PR Wrangling process, as a way to onboard possible new reviewers, approvers, and wranglers. What would you like to be The above-mentioned shadowing process was brought up and discussed in a late 2021 SIG Docs meeting, however, has no documentation to explain the process or the expectations of the PR Wrangler and their shadow. We should put together information, to our existing PR Wranglers , that lists details about this program, how to become a shadow, and what participants can expect to learn. Why is this needed To ensure our shadow process is successful, a clearly documented guide is needed so we can better recruit for this program and evangelize it. Given we'll be reporting on this addition to our training in the 2021 Kubernetes Annual Report, we should prioritize the creation of these docs. cc:\n/language en /sig docs /triage accepted\nHi, I would like to work on this issue. Thanks. /assign"}
{"_id":"q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684","text":"Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues 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]:\nThanks for reporting, I can open a PR to fix this! /remove-lifecycle stale /assign"}
{"_id":"q-en-website-b15e60c66f0fd739f2fb31060f88342323f57121d5be223510513a453901f522","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/retitle [ja] Translate /docs/reference/scheduling/policies/ into Japanese\nRe-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /retitle [ja] Translate /docs/reference/scheduling/policies/ into Japanese 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 [ja] Translate /docs/reference/scheduling/policies/ into Japanese\n/triage accepted"}
{"_id":"q-en-website-41e086576cfe5c619ac935e47802c2f978dcc4955edb7353615e1c119f7bbbcd","text":"In the v1beta1 admission config example, I had to use rather than See\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:\n/sig auth /language en /assign"}
{"_id":"q-en-website-fff038ba39281fa9f68f4f7cf1c791e9a9867e0cc8c10d6ff8d148e851ce8d68","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: marks the userspace kube-proxy as deprecated. This was missed from the v1.23 docs updates and . Proposed Solution: Mark the kube-proxy in userspace mode as deprecated. Page to Update: <!--Additional Information:--/sig network /language en /priority important-longterm\n/lifecycle frozen /triage accepted\n/assign"}
{"_id":"q-en-website-86fcd5caffdae77528ee3611ea1d9ac08574fe276906d772ff477e83b37606ea","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\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-48fb8579b5eeb3d432876b518e800e05e460a8f095c1bbaad7728e78677802ec","text":"Update , job-tracking-with-finalizers section, as k/k PR is disabling by default due to an unresolved bug.\nSpecifically the note () says that \"it is enabled by default.\"\nthis feature is currently enabled by default in v1.23 and will be disabled in v1.24, right?\n/sig apps /language en\nI also proposed to disable it by default in 1.23 , but the release managers haven't approved it yet.\n/triage accepted /sig apps\n/assign\nThanks"}
{"_id":"q-en-website-a7fe5888cd3e3303489db159dbc5df31a25401fab65a27b34caca25634b4f8f1","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 at the top of the homepage () seems to currently redirect to I assume this is the same issue as Proposed Solution: Remove the /dockershim alias from the ZH blog page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nSame symptoms, different PR. /triage accepted Thanks. /priority important-soon\n/assign"}
{"_id":"q-en-website-4de8abcb920b5add5d520eb9bf2d97958c93aedb52bd34f4cf44231fdd61f627","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: while cleaning up mentions of the legacy \"master\" taint in kubeadm docs: saw the following: it seems the generated reference API docs for kubeadm still include the \"master\" taint. Proposed Solution: cleanup mentions of the old taint from kubeadm's API reference docs at perhaps these need to be synced with: for dev-1.25 and main at k/website we removed the old taint from there before 1.24 was released. 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 cluster-lifecycle /priority important-soon /kind cleanup\ncc"}
{"_id":"q-en-website-c85922be7415596e0269ba9a9ab9956bbc9ce636eebb4d620c97e2b418c93ca7","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: Apply Pod Security Standards at the Cluster Level documents Pod Security admission defaults, but for Kubernetes v1.23 rather than any more recent release. Proposed Solution: Either: Edit to automatically render with the version of Kubernetes being documented Update for Kubernetes v1.24 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority backlog /lifecycle frozen /triage accepted\nWhat would need to change here? The Kubernetes minor version in the commands or also the version in the intro paragraph? (wouldn't that remain 1.23 since that's when the feature went beta?)\nThe tutorial shows you how to deploy a v1.23.x cluster; it should be v1.24. Maybe if we don't specify any version explicitly, that's good enough (I haven't checked, and I'm not very familiar with ). Making that version always match the latest release is left as an exercise for the reaser.\nHi, I have a question if we automatically render the Kubernetes version being documented for the page, would it be okay to mention something along the lines of : ? Thanks.\nYou can use this shortcode to show the version: See for an example.\nGreat, now I can try to work on this issue on the lines of the example. Thanks. /assign"}
{"_id":"q-en-website-00bb6173b77e0637f1aebc6055b5c3a25941e39300b51be8133ab4bc6c4a429b","text":"Simple documentation issue: Section for \"CertificateSubjectRestriction\" admission controller is \"CertificateSubjectRestrictions\". The appended 's' is not valid and will prevent apiserver startup if used in --disable-admission-plugins. Note: plugin is listed correctly in the 'defaults' list.\nFixed by /close\nClosing this issue. <detailsIn response to : Fixed by /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/triage accepted /language en"}
{"_id":"q-en-website-c02cfe41918055372d864c0f3142661b3d8ce34aca8492374c633cbf911af2d1","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: Information regarding volume snapshot API in the following blog is not accurate. Volume snapshot API moved to GA in 1.20, so volume snapshot v1beta1 was deprecated in 1.20. Proposed Solution: Information regarding volume snapshot API in this blog is correct: Please update the API Removals Deprecations blog accordingly. 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/retitle Incorrect information regarding VolumeSnapshot API in v1.24 upcoming removals article /area blog /language en What is the correct statement about the fate of the v1beta1 API for VolumeSnapshot When did (or will) that API version transition from deprecated to unsupported?\nI suspect the fix is to edit: to: Does that sound right? /triage needs-information\nChange 1: which provides standardized APIs design (CRDs) and adds PV snapshot/restore support for CSI volume drivers, entered beta in v1.20 Change 2: Above has to be: [diff ]\nThe following is correct: . Volume snapshot and restore functionality for Kubernetes and the Container Storage Interface (CSI), which provides standardized APIs design (CRDs) and adds PV snapshot/restore support for CSI volume drivers, moved to GA in v1.20. VolumeSnapshot v1beta1 was deprecated in v1.20 and is now unsupported. Refer to and for more information.\n/assign\nI completely agree with the contexts that has shared.\nNew PR has been raised for this issue."}
{"_id":"q-en-website-442d1dceb41340a1e8b0350672225b5d6fea8ca084cb86b67a38ab473cf00698","text":"Just above this anchor #node-affinity-per-scheduling-profile, the note block is referring to the Pod spec pod-with-node- 2 above, but it's placement appears to refer to the one immediately above. It takes a little bouncing around the page to sort it out :)\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-8ceed321adb9bb785c08befd00f329ff2680a5010c632092c81b475383e6b558","text":"Description of Node Affinity example pod spec \"pods/pod-with-node-\" contains an error: does not apply. The spec shows instead that key \"\" should be \"\". Under the Node Affinity Weight section, the following note is also out-of-place: It needs to be moved to the previous section.\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 issue is a duplicate of . /triage duplicate"}
{"_id":"q-en-website-7ed003f36ff037851e1ce066cfc8070e195e0a4b519adc19daf864395a404cf6","text":"This is a Feature Report Problem: misssing Chinese translation docs: content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX Proposed Solution: add Chinese translation docs in website Kubernetes Blog Comments /language zh /assign\nEnglish page:\n/triage accepted"}
{"_id":"q-en-website-89ec09a0ee7274de005227b6ef5aebfa2cab9d889b99eecbb002548242d2b6f6","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 the to only ignore the directories and at the top level of the repository. Why is this needed If somebody wants to create a content directory named , that ignore will conflict. We should tidy it so it wouldn't. Comments /kind cleanup Docs for : https://git-\nCan you assign it to me..??\n/assign\n/triage accepted\n/priority backlog"}
{"_id":"q-en-website-47741c81ffa1b144414db9041a2621bf5c0692295fcc5902a783a1c3a2c89f9d","text":"web\n/retitle [zh-cn] Fix table formatting errors on the kubectl page\n/triage accepted"}
{"_id":"q-en-website-aa94bbae7c17b3209db89fa80124d07bf7ae2c7befec859a57eb802e00c3789b","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 command for strategic merge patch: \"kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-\" Proposed Solution: correct command: kubectl patch deployment retainkeys-demo --type strategic--patch-file patch-file- Page to Update:\n/wg api-expression /language en\n/assign\n/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 : /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"}
{"_id":"q-en-website-0a9e16f3733f164ec327f36316aaef8e3737476f6fe5ff2ea14b629013472ebe","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: Kubernetes can use an annotation, , but this is not registered or documented. Proposed Solution: Document the annotation in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig auth\nmentions this annotation, so it has been used in the past (and, I suspect, it is still used).\n/assign\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]:\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/lifecycle frozen /priority backlog\nThanks SIG Auth folks!"}
{"_id":"q-en-website-990476a5d3d458d0e8c0f589f0ae472bd713d16285eb9b00d40bbccffb05d7be","text":"Problem: The text . on is redirecting to , it should point to these Check the github repository page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text these instructions to create a documentation pull request against the repository to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text . on is redirecting to , it should point to these Check the github repository page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text these instructions to create a documentation pull request against the repository to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"q-en-website-05793bce3bf596c30743efff4e1a3e1af94fb5a63083aa8e0b7af350ee5aba99","text":"Problem: The text on is not working, it should point to this Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume plugins to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to this Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume plugins to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted"}
{"_id":"q-en-website-130a375f516dbc3c1407629f09c307d35f209dffc8f583f28183545fba2ad72d","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: implies that Kubernetes has Docker Engine support. In fact, Docker Engine only works with Kubernetes if you either: connect Kubernetes to the containerd that makes Docker Engine work use an adapter such as Proposed Solution: Pick an option: the sentence: a bigger revision to the concept page (check if there is already work under way) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en\nHi is this work fine or if you like to add something\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"}
{"_id":"q-en-website-ba41cb1987fa630163c7a291cab3011488071e3e18c672df549e7e1154755421","text":"But the document doesn't say what to do in this kind of case. Creating a secret using --from-file in this case won't work; instead have to create the secret by passing the --docker-server etc arguments.\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-d898f604daa97a49e6ca4848784edabf944453abf048ed063e63d88fb79c0c2a","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 content/hi/docs/reference/glossary/replica- 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-e25372679a1ae4e8a519f69ed80315fe9d788a6496495ce883b82d6c681e7e7f","text":"Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text FlexVolume to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted"}
{"_id":"q-en-website-b1ea532711c3074cf1ae265c435c0b6a95ebcd3f2607b5c7873412e1dda826c4","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: documents metrics for Kubernetes v1.26 but that's incorrect because at the time I'm filing this the live documentation is for Kubernetes v1.25 Proposed Solution: Revert whichever PR bumped the document too early or do a careful partial revert that only omits the v1.26 changes Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig instrumentation /language en If v1.26 gets released before we fix this, it's OK to close the issue. Consider a backport to the v1.25 docs, though.\n/assign\n/triage accepted\n/assign"}
{"_id":"q-en-website-d4e088e49775a905a0ad78fd2230ef28029f40b6a5023f2d34c7a9719f5efe08","text":"This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:\n/area web-development /kind feature\n/area web-development Something similar to https://medium- ?\n/retitle Enable click-to-zoom for some diagrams and other images\n/triage accepted /priority backlog /lifecycle frozen\nThanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.\nFor now I'll investigate more and try to find out what can work so assigning it to myself /assign\nA couple of hints:\nThere is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code\none is a good reference for same functionality with example. I'll try both and raise a PR after that.\nWe using vector images.\nThis issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted\nMy apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.\nThis could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen\nLet me see if I can assist with this. Edit: I request review and feedback on pull request"}
{"_id":"q-en-website-b0cd9125ba23cb615c65468d551574cb465d19bac54d3f7f37d7e987286f5b2b","text":"This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :\n/sig docs / language en /assign\nIf triage is accepted, i would be happy to contribute on it. PTAL.\n/language en Fixed here .\n/triage accepted"}
{"_id":"q-en-website-d24958dbd3ea1898ccfc04bdfeac1e967ca3a83581035e7db7119351a204bf4d","text":"Observed this issue while reading . I have gone through the the whole file need to do these changes. ्रीगेशन लेयर आपको अपने क्लस्टर में अतिरिक्त कुबेरनेट्स-शैली API स्थापित करने देता है। Need to remove this कुबेरनेट्स need to change this to -API ें URL -URL पाथ /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\n/language hi /kind bug"}
{"_id":"q-en-website-3d560b207efb75cde6445cd8a6069c5934c4aa02d3b15e368303ec24ab127b2f","text":"This is a Feature Request add and translate Chinese document: content/en/docs/concepts/scheduling-eviction/dynamic-resource- URL <!-- 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. --Localization Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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-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-1d9812d26b20b3685071055b84181ca22bc147b1e059c26cb6fae2e00354437f","text":"reference:\n/assign\n/assign\nhello, can you please leave this this will be my first contributions towards open source. hope you don't mind.\nSure\n/unassign\n/triage accepted\n/kind documentation"}
{"_id":"q-en-website-48802673bcb1a5b7c6624b4fd0c4dc8f115a6aa4205dccae2bf428082bfd6daa","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 image files in need to be converted to an SVG. Currently, they are PNG. The originals are PPT files that can be found at Earlier attempts to convert them to SVG resulted in poor-quality images. Proposed Solution: If anyone has the tools and expertise to convert the PNG/PPT to high-quality SVG that will look the same as the PNGs, we welcome the help. Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign If anyone gets to this first: great!\nhey! looking to contribute to this project !..can I?\n/triage accepted\nI've made progress on this and hope to send in a PR later this week."}
{"_id":"q-en-website-8832f3c1d52762d5e12a743c053b754543b94e4473bd2230f8298c8f8f467cea","text":"This is a Feature Request What would you like to be Add the commands which are under the Clean up section of the and tutorials into the shell code block snippet. Currently, it is under the triple backticks () as shown in the following screenshot: ! ! Which is not look more prominent. Why is this needed It provides a better structure to the section. and then it will be highlighted on the page. Comments None\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 docs /language en\n/assign\nFixed it here:\nI'm not sure I agree with the issue description. I was nevertheless happy to merge the actual PR.\nthank you, I opened this for the content so that commands under Cleanup should more clear like others command mentioned on the page."}
{"_id":"q-en-website-c427590bfe5872ba7ea2727992246cf4bc01ade4da5462dab563c71ae3046bdc","text":"This is a Feature Request CEL expressions were originally documented for . When ValidationAdmissionPolicy was , the to the new API. We now multiple other enhancements (e.g. ) where the documentation would need to be duplicated. What would you like to be Instead of continuing to duplicate this documentation, resulting in documentation that will invariably drift and become inaccurate, let's instead introduce website documentation and link to it for all the documentation that is the same for all usages of CEL in Kubernetes. Website documentation will contain: escaping rules Kubernetes specific type information (e.g. equality) Libraries available What data is accessible to CEL expressions (e.g. ) API documentation of fields that contain CEL: What root variables are available in the specific context (e.g. \"object\" or \"self\") and what the variables provide access to What level of type safety is provided (full type checking, informational type checking, runtime only type checks?) Why is this needed Avoid API documentation inaccuracies and drift. Comments\nNeed to also document\n/sig api-machinery /sig docs /language en /triage accepted\nHow about a Reference page titled “CEL in Kubernetes”?\nIf we'd like a short docs URL, eg , that can be a thing (using a Netlify redirect with a temporarily moved status)\n/retitle Move CEL expression documentation from API documentation to website\nThe reference page idea is great. Once we get past enhancement freeze I'll open a PR.\nSIG API Machinery folks: what's your preferred priority for these docs?\nI intend to complete this for 1.27.\nStarting work on this now."}
{"_id":"q-en-website-b477db53a8daa4eade7e0cbdc389229cf993f88deb1955a6a7dd14e485f64f62","text":"The docs on currently make no mention of field validation. Now that of unknown and duplicate fields is graduating to GA, we should mention it briefly here.\n/cc\n/triage accepted\n/wg api-expression /language en /priority important-longterm /sig api-machinery\n/assign"}
{"_id":"q-en-website-b50f3e957d5d1e5cb22c3eda4f6f5f5e506a70d1592f4359d69452258236334a","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: Link for Federation in is broken Proposed Solution: Should be updated with correct link 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/area blog\n/assign\n/language en"}
{"_id":"q-en-website-57697f3976e44b51239d9532890ead17ca387ff9e95e59752a230a5209f36956","text":"This is a Feature Request After release, we don't need . We should update the instructions on the task to include verification using cosign 2.0 <!-- 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 <details<summaryverification using cosign 2.0</summaryAdd a note if cosign version < 2.0 </details<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed There are some breaking changes in cosign 2.0 and we should update the instruction for the verification of images. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\n/sig release /sig security /retitle Update page Verify Signed Kubernetes Artifacts for cosign 2.0 /kind bug /remove-kind feature /language en /triage accepted Thanks\n:+1:\nI can work on this /assign\nHey Are you still working on this issue? If not, can I work on this?\nHaven't gotten to it as I expected to. Please feel free to work on it /unassign\n/assign\nFYI\nApologies for not being able to review the PR. I am going through University exams which is ending tomorrow. I just rushed through the changes that you made and you really did awesome work on this. I'll look more into this after the exams. Thanks for working on this."}
{"_id":"q-en-website-94f439c923e3c39c498ad8178b369f4875c795579f48dcc5e81224046744e1d8","text":"This is a Bug Report Problem: The versions of the cri-tools and cni-plugins dependencies was updated in packages, but not in the documentation: Proposed Solution: Update the versions, to match what is in the deb/rpm packages. Currently they are not pinned, but installs the latest: Compared with the deb installation: Page to Update: Kubernetes Version: 27.0 <!--Additional Information:--Related:\n/sig cluster-lifecycle /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 : /sig cluster-lifecycle /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted /priority backlog\n/assign\n/unassign"}
{"_id":"q-en-website-3fe00b077d85b55e97589a5922e253dc53d552e0f5c964d6d93014279031c6af","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 think adding some expressions to indicate controller manager runs many controllers explicitly, moreover indicate the actual amount of controllers in document page is useful for beginner. Why is this needed When I communicated with some k8s beginners, they think controller-manager only run 4 controllers refered to the document. Actually controller manager has run nearly 40 controllers currently, and the amount will increase in the future in predict. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --\nIts difficult to mention all the controllers in the document as some examples of the controllers that run within the kube-controller-manager process. There are additional controllers for different aspects of the Kubernetes cluster.\n/language en Rather we can say there are more controllers that run within the kube-controller-manager. With few more examples\n/triage accepted /priority backlog Don't add more examples. Instead, reword to make it clearer that the 4 examples listed are selected from a much larger set.\nExpression in is puzzled too\nThere I would make changes. Swap: remove “replication controller” out, using “statefulset controller” as its replacement remove “endpoints controller” out, using “endpointslice controller” as its replacement\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\nI'd like to work on this\n/assign\n/assign\nHey has assigned this issue already. You can find another issue that you can work on."}
{"_id":"q-en-website-1c6ae3910ad09e8553c0fbd72ee29cc965c2e7070773221914c5708b103e3074","text":"The command showed nothing. But this command worked. It looks like the labels have been changed and now the example is different from the real state of version 1.27.3.\nPage related to issue: /language en\n/retitle Incorrect label in kubectl command for inspecting Leases for kube-apiserver\nJudging from the k8s upstream code, this label has indeed been changed and the documentation needs to be updated. /cc for confirm\n/sig apps\n/assign\n/sig api-machinery\n/triage accepted\n/assign"}
{"_id":"q-en-website-e580c4048725c608f97a4941d94e4a34e08f1996285cf767652069c298f84881","text":"This is a Bug Report <!--Required Information--Problem: The under the in redirects to the following link: i.e. concept page in which there is nothing about Service Proxy. It is due to the revision of the Service concept page by the following PR: Proposed Solution: service proxy should redirect to instead of Page to Update:\n/sig network /sig docs\nI am working on the issue and will raise a PR soon. Thanks /assign\n/triage accepted /priority backlog\nFixed it here:"}
{"_id":"q-en-website-73c9bb6db2fc86f277807adbb862ed6fe8c9444e624cada44e77c843dcd7c013","text":"This is a Bug Report Problem: The link for under the in is wrong. It is redirected to the instead of that it should redirect to the Proposed Solution: IPv4/IPv6 dual stack should redirect to the instead to the Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/sig network /sig docs\nI would like to work on it /assign\n/language en\nThis issue is resolved here\n/triage accepted"}
{"_id":"q-en-website-726f91f8d6680834846e2669fc9ae108cfa29d6a443d881d20c3f26feb2067e9","text":"From the link to is 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\nPage related to issue: /language it\n/retitle [it] Broken link for \"Create a cluster in High-Availability\" in Kubernetes Components page /kind bug\n/assign\ncan i contribute to this\nThe link is broken in every component !\n/assign"}
{"_id":"q-en-website-f2118c1b83bf7a78c158c67a3165acd3c2452aea2a25fcfac2be591e279e9c49","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Proposed Solution: Page to Update: /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nDuring my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.\n/area web-development\nI tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.\nI see, In that case I'll try to find anymore pages that might be having the same issue.\nSimilar issue is present in case study"}
{"_id":"q-en-website-683630a2ded3f0e30169950c07afbe199360b9a39939cf6583173d7c34cee575","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: According to , Kubernetes uses an annotation: . However, this annotation isn't registered (registration means adding it into ) Proposed Solution: Register and document the annotation. I am not sure which version of Kubernetes / will add the support for this annotation. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig api-machinery /language en\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\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\nAnyone is welcome to work on this. See for information about contributing to Kubernetes, including to the documentation.\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\nhey can i work on this issue\nAnyone is (still) welcome to work on this. See for information about contributing to Kubernetes, including to the documentation.\ncan you assign me this issue i would like to work on this issue\nyou are welcome to work on this issue; we have a no cookie licking policy in SIG Docs. Anyone is welcome to work on an issue. If someone has already said that they plan to work on it, it's polite to liaise with them first. However, a second contributor can join the effort: either by opening their own PR, by reviewing the first contributor's work, or by some other means such as pairing. We rarely assign issues to contributors because of the policy on .\nI'll add one thing. If people - including you - would like to document a missing annotation, take a look at Working top down (ie, oldest first) is even more helpful.\n/assign"}
{"_id":"q-en-website-fd97b1b9ade73db7322c1e7d03b44ed9cd34471f3984c9885d4c718014a83e1d","text":"This is a Bug Report Problem: Repetitive word in Installing section under Note. Proposed Solution: Remove the repetitive word 'to' Page to Update:\n/sig docs /language en /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 : /sig docs /language en /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/retitle Repeated word in Install kubeadm page /triage accepted\nI will sumbit fix for this plzz /assign\nI have attempt to make change for this inf"}
{"_id":"q-en-website-f0f198a4e87bd657c33d0c9e241644403bc7dfa7b4dc7a8fe75d5ce234aca581","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 to in the code security section of leads to a 404 error. Proposed Solution: Replace the link with a working one or remove it. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/sig security /triage accepted\ncan we use the following link for ZAP: The above link redirects to the ZAP website.\ncc your thoughts on this\n/assign"}
{"_id":"q-en-website-96b393461a43f397697c33a4873df7e43cc8fc9f163c1f594c785ec4b374c2ec","text":"Kindly note that you asked us to delete the service in the previous section. Please update the docs by asking to restore the service first before running this command.\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nCould you please provide some details on the issue in the section? /triage needs-information\nPage related to the issue: /language en /sig autoscaling\n/kind bug\n/assign"}
{"_id":"q-en-website-a97cf05d0b93869cbe1220b49eb827e15c4ae48d4f8e15c7656fdef86249faa4","text":"Run kubeadm upgrade node phase kubelet-config to download the latest kubelet-config ConfigMap contents into the local file The local file name should be\nPage related to issue: /language en\n/retitle Incorrect file mentioned in command\n/sig cluster-lifecycle\nplz I want help to fix this /assign\nFYI, the same incorrect filename exists in other places on the same page. Two are in the second blue-barred Note pane below the command, and three are further down in the section\n(or other maintainers) Can I get confirmation and go ahead please; if this be a tirage-accepted issue to that i can proceed with the fix.\n/triage accepted /kind bug Thanks for spotting this.\nI have attempt to make fix for this in"}
{"_id":"q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1","text":"This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see"}
{"_id":"q-en-website-78a0c1802b897b0651a8e86e46745f88bc205a8705c6211e9b59a67defd1ab60","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Within , add a new and brief page that has an overview of autoscaling. This means adding a new Markdown file. The new page should mention: (aim to make it clear that this is a thing that autoscales nodes, not Pods) (aim to make it clear that this is a thing that autoscales nodes, not Pods) Optionally, also mention: - marked as third party software as it's a separate project from Kubernetes - marked as third party software as it's a separate project from Kubernetes For this issue, all that's needed is a few words about each item. Later PRs could add more detail. Why is this needed our documentation on autoscaling is incomplete readers would like to have their workloads automatically sized to match demand. Comments This helps with /language en /kind feature PS. I didn't mark this as a good first issue. However, if you're looking for something to work on, and haven't already contributed to Kubernetes' docs, there may be some issues available marked as good first issues. See this . If you have already worked on an issue, please leave these for people who are new to contributing.\n/triage accepted /priority important-longterm /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /priority important-longterm /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI would like to work on this issue /assign\nShould I Make a new file inside Workloads!! In 1 PR I will be creating 2 topics like (HorizontalPodAutoscaler, VerticalPodAutoscaler) and will it be sufficient, because It will be taking 2-3 PR's!\nFor advice on how to contribute to the Kubernetes docs, please ask in #sig-docs on the Kubernetes Slack workspace. If you're not already a member of that workspace, you can visit for an invitation. Anyone is welcome to work on this issue. it's slightly unhelpful to assign an issue to yourself and also to ask questions about how to work on it; ideally, people only assign an issue once they are confident that they know how to resolve it.\nOur no cookie-licking policy means that anyone is welcome to open a PR that closes an open issue. It's still friendly to reach out to people who might already be working on the same thing. See for an explanation of the jargon.\nThanks I was just asking it. I can fix this issue!\nHey This has been pending for more than a month. So, May I go ahead and create a PR? I have a basic markdown structure for file is ready and I can add more details as needed after raising a PR.\nPRs are welcome, and because this project is open source, nobody needs permission.\nIn light of our policy on cookie licking: /unassign I think we'll make progress better without any assignee. If anyone wants to share that they have started work, feel free to open a draft pull request that mentions this issue."}
{"_id":"q-en-website-294bf34ec688d7f154f12ae076aa7df8a9009536b82d434f04217f7fda23237b","text":"This is a Bug Report Problem: The link for in  is incorrect. It is redirecting to but it should redirect to Proposed Solution: should redirect to instead of\n/sig docs /kind bug\nPage related to the issue:\n/language en\nI would to like to solve this issue if triage gets accepted.\n/triage accepted\n/assign\nThe issue is fixed here:"}
{"_id":"q-en-website-365e9687894267021dc2445e25427204970c928fe4b20e1383fe4bcf2eb81912","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 code block is not being processed correctly, resulting in the page rendering in an unexpected way. <img width=\"625\" alt=\"Screenshot 2023-12-06 at 16 52 11\" src=\"\"Proposed Solution: fix L84 (to yaml) 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/language ja /assign\n/area localization"}
{"_id":"q-en-website-9b20aa1d7b434b6ac5dc76003bcd629434c04ffb8329fb9aad9a9c3dc9870747","text":"Please note: This issue is not suitable for new contributors since you need some familiarity with how Kubernetes works. The Kubernetes website currently lacks a guide on creating Windows/Linux nodes. See for more details. SIG Windows opted to remove the guide that did exist for creating Windows nodes, in PR Write a new task page about creating nodes for all operating systems. This could, potentially, be in a tabbed format as mentions in the issue referenced above. We would also need the entry reflected on the creates the Linux task page by moving / refactoring the existing \"join node\" contents from the \"create a cluster\" page: creates the Windows task page by taking the content from at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: adds tabs in the to choose between OS for joining nodes. /priority backlog /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Problem Statement: /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted Thank you for filing this\n/sig cluster-lifecycle\nIf you know how to set up new nodes (with, at least, the tool): you can work on this issue. You don't need anyone's permission to open a pull request. All we ask is that you read our and that you abide by the project's code of conduct.\n/assign\nRelevant to\nAre you still working on this issue?\n/assign sending PR soon.\n/priority important-longterm\nRelevant to\n/retitle Write new task pages about creating Kubernetes nodes\n/cc\nDone in PR /close\nClosing this issue. <detailsIn response to : Done in PR Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"q-en-website-bd4dfde8efbc01170c61323b19f9c0c7288762ae5ba3c7478ff92fe13cf027aa","text":"This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:\n/sig docs /language en\n/assign\nBeta APIs are off by default with\nis not a beta API though /triage accepted"}
{"_id":"q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd","text":"Hi Currently we obsrved that following image is not availble\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/language en /sig docs\ncan you please provide the page link of the issue?\nHI Kubernetes/Website PFA link\n/retitle Container image is not available for /kind bug\nThis looks similar to issue we already have I think it is a duplicate. /triage duplicate\nThanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned\nClosing this issue, marking it as \"Not Planned\". <detailsIn response to : Thanks for raising this! 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-0b11797e8859523eb0e1cc3a2d92c0c438b909b0fffef922670c863b5b817a9c","text":"Missing important step new people SSH into the node\n/language en\nHi could you please explain the issue in detail. /triage needs-information\nPage mentioned in the issue (based on the title): /language en\n/retitle Users not instructed to SSH into the node before executing commands in \"Upgrading Linux nodes\" page\n/sig cluster-lifecycle\nI'm not sure this is valid, though there isn't much detail to the issue to explain what the concern is. The commands on that page need to be run on the node being upgraded, but I think how the administrator connects to that node is out of scope. It may be SSH, it may be by accessing the cloud providers console. It may be by rolling up a crash cart and plugging in a monitor and keyboard. That all depends on the individuals environment.\n/remove-triage needs-information\n/remove-kind support /priority awaiting-more-evidence /kind feature /sig cluster-lifecycle\nThose labels are not set on the issue: <detailsIn response to : /remove-kind support /priority awaiting-more-evidence /kind feature /sig cluster-lifecycle Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nMy opinion: if you (the reader) don't know how to get a shell on a node, it may not be a good idea to try upgrading it. Best learn the basics first.\nWe could list “shell access to the node“ as a prerequisite. I don't think we can or should assume SSH; I'm barely happy that we assume superuser access comes via .\nfor new contributors. page to update: change: to: make sure you add in the PR description. /help /triage accepted\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 : for new contributors. You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster You need to have a Kubernetes cluster, shell access to all its nodes, and the kubectl command-line tool must be configured to communicate with your cluster /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/kind feature /remove-priority awaiting-more-evidence\n/priority backlog\nThis one looks like a candidate for a \"good first issue\" label. I think that the page should also have the shell access note, regardless of the method used (ssh, rdp, etc).\nI don't think this is a good first issue. A good first issue would have a description that helped totally new contributors find out how to help, and the description for this issue at the time of writing is:\n/assign\nGot it. Going through the details, I see another problem here. The pre-req of having shell access to the nodes seems mostly relevant (a corner case) for the node upgrade task, for other cluster maintenance tasks, API access to node management seems enough. The problem is that the , and many other pages use the same prerequisites document (). So, adding the \"get shell access to the nodes\" phrase will alter all these documents where this step is not needed. I think that, for this particular task, we should not use the include prerequisite doc and rewrite the paragraph locally on the pages, as a compromise between convenience and accuracy. What do you think?\nThat'll work fine.\nGiven the need to modify two documents and the potential for content drift across releases, etc, I decided to add a new prereqs include file with the modified paragraph instead of rewriting the whole prerequisites section on both documents. Let me know what you think. Thanks"}
{"_id":"q-en-website-fe29d03168fdbebd9f13a3305c2c5336921beff85629d6d4956dceafee405fd1","text":"found typo \"ontrolPlaneEndpoint\" in the below <img width=\"862\" alt=\"typo ontrolPlaneEndpoint\" src=\"\"There is a typo \"ontrolPlaneEndpoint\" in the localAPIEndpoint description it should be \"controlPlaneEndpoint\"\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nPage related to issue: /language en\n/retitle Typo in auto-generated \"kubeadm Configuration (v1beta4)\" reference page\nThe mentioned reference page for \"kubeadm Configuration (v1beta4)\" is . The page is generated from the upstream source code . As the page is generated from the upstream source code, any fixes would need to be addressed there. For those interested in contributing to resolve this issue, please refer to the upstream contribution guidelines outlined at:\n/sig docs\nthis is not a typo in the code files and also in my browser it's shown as controlPlaneEndpoint, so maybe it's a rendering issue. ! cc\nbut again, there are no typos in the code / go docs. also NOTE that v1beta4 is WIP API that should not be used yet by users.\nthe in is also dropped in another place on that page, screenshot below. I'm not familiar with the autogeneration for these pages, is there some processing on the word that is dropping letters when converting from the original? Looks like in the source file its written with a capital and in the generated file its with a lower case. Not sure why it would only so it sometimes though. We should check to see if this is happening on other pages. /priority awaiting-more-evidence <img width=\"789\" alt=\"Screenshot 2024-03-27 at 9 44 26 AM\" src=\"\"\nAnother interesting observation looking at the - it appears to only happen on the v1beta4 version of the docs, not the previous versions. Looks like it was modified with .\nPut up a fix in . It looks like this wasn't from an autogeneration error and just a simple typo when the docs were updated for v1beta4."}
{"_id":"q-en-website-cb1fa64fcf6f6439541b56d0a24e4be5a354e115075f31166889a1e331dad530","text":"chapter refers to the Memory QoS feature but pointing ; link should be updated to point to feature description in k8s official documentation.\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 reported in issue: /language en\nI would like to work on this issue.\n/assign\nThe issue is fixed ."}
{"_id":"q-en-website-5382a1d88442546b93aeeba0afa5f02f8cc1d944d80a4ba96824212378eabd91","text":"in\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/language en /sig docs\nI would to like to work on this issue.\n/assign\nThe issue is fixed ."}
{"_id":"q-en-website-8c70215724b3414e64fc43b22542bd6d8b5fd3bf42e2a4b374c3bd09585d0f28","text":"This is a Bug Report In Kubernetes Training page in hindi the link is not valid which do not show the several Kubernetes Training Partners. <!-- 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 embedded link is not valid. ! Proposed Solution: Update with the valid link Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language hi /sig docs /assign\n/area localization\n/triage accepted\nThis issue is resolved under pull request\nso i am closing this issue marking as resolved and completed\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-7daa4b636affe1c393c1212832c7ab2bd6856722df55d074a22af272b18322c9","text":"Hello! in the Pod OS section of this page, it says: ... **Editing for clarity: Forgive me if I'm misunderstanding, but kube-scheduler should pick a node for the Pod to run on, and not the other way around? The way the above sentence is worded sounds like kube-scheduler picks Pods to run nodes.\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\nthese two statements donot contradict as first one say that selecton of node by kube-scheduler is not based on . kube-scheduler pick a node of run based on various other creterias but not consider frield\nI think you might correct the text might need some correction.\nLet me see if I can help with this. /assign"}
{"_id":"q-en-website-b98e6a21d5646ce0963d834261f77377a0fcf68ea7a65eece583205fbc9373c2","text":"This is a Feature Request What would you like to be Set a banner to announce KubeCon 2024 NA Why is this needed We usually turn on a banner for the upcoming KubeCon about 4 weeks ahead of the event. Logos are available from: (Note: be sure to copy the logo into this repo) should help with text. Also see the config from a last year's KubeCon. Comments This change will need approval. I would like to set the banner to start on the ~Oct 14, 2024~ Sep 30 and to end on Nov 15, 2024 at 1800 CET (UTC+1). edit: We've been asked if we can do a 6 week banner rather than a 4 week run. /priority important-soon\n/triage accepted\n/assign\n/assign"}