{"_id":"doc-en-website-e2eb7206bdbed8b290ce16cc9df713aabb9da022f49827593082437f30edcb95","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. It is needed for PR Comments /language ja /assign\n/triage accepted"}
{"_id":"doc-en-website-6cb4c6a8eec5fb520dcad0d76be50115bda9757dd9f7566d095eac099cdb38b6","title":"","text":"This is a Feature Request What would you like to be Create new directory and . Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\n/triage accepted"}
{"_id":"doc-en-website-7c3bfb760b0f32dbb78080eee4e9d6eaa1c0d612259f5fd19aad6cdea5095731","title":"","text":"I wish /docs/getting-started-guides/docker/ I wish this page existed"}
{"_id":"doc-en-website-ff47120f5ef0aa098e4e7382085205bde4f0c0f768f8ae73a601cd727875b707","title":"","text":"I wish /docs/admin/dns/ linked correctly to the federation guide, at"}
{"_id":"doc-en-website-d232590f0e2354932eacaeb48dc20bea33acc8ad01357d69547972d06247cf01","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. Proposed Solution: Update to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/sig cluster-lifecycle\ncc\ni see the discussion / PR here: using in the kubeadm docs makes sense. /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 : Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. /help </details\n/assign"}
{"_id":"doc-en-website-611b15338596d91ddf8fce52c1acf70b9de26a9cc5df3b8893687d47764ea2ac","title":"","text":"This is a Feature Request What would you like to be There are terms that can use the addition of a glossary tooltip to show the meaning of the said term. There is no or reference section Some terms can use references like : , Why is this needed Rather than searching for the definitions of some terms , the references can help 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 The page needed to be updated here is :\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/kind feature /language en /sig docs\nIf the triage is accepted would be happy to contribute references I have searched while reading the concept. /assign\nWorth doing, but the change I outline in is more valuable to work on.\nhere seems to be about the and page in particular. I'd agree with the general idea of making the content brief and putting extra information in the reference. For control-plane-node-communication page, I see your comment about adding a diagram there. Will try to add that as well.\nFor now, I'll push this commit, in case even if we shift this content to reference or another section, we would still need some of the links and references.\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\n/remove-lifecycle stale"}
{"_id":"doc-en-website-4962ce7fcabfca79c3ca98c943354f6e18b9bfa0b930e33f6baddee8440f0ba2","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In , the step No. 3 is talking about the location of binary, but actually in this section (\"Install plugin\") we should care about the location of binary, not of binary. Proposed Solution: In : And optionally, wrap these words with backquotes in : : kubectl L47: kubectl L62: kubectl L159: kubectl-convert L165: kubectl-convert (L180: kubectl-convert) - Already suggested above. Page to Update: )-,Append%20or%20prepend%20the%20kubectl%20binary%20folder%20to%20your%20PATH%20environment%20variable.,-Verify%20plugin%20is <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/language en\n/triage accepted\n/assign"}
{"_id":"doc-en-website-eb374f50a5934d6c6cf42433078b94dab633680d41a4a181f8f8441503596135","title":"","text":"! w sudo systemctl enable crio --now\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nThis is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Typo in zh/docs/setup/production-environment/container-runtimes Proposed Solution: -Page to Update: zh: (en: ) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/retitle [zh] Typo in docs/setup/production-environment/container-runtimes /kind bug /language zh\nPage is a little bit lagging behind. Will fix. /assign"}
{"_id":"doc-en-website-a1db360be651aafe95f4fd8fe6d7c0ee9fc36337cda5ed4c617c91368c09585a","title":"","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":"doc-en-website-bba31c347b50b7954619fd2ab98d3261beeaa9d34337c27d9746375bcdb7113d","title":"","text":"says: It should be AN upgrade.\n/triage accepted /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 : /triage accepted /sig cluster-lifecycle /help </details\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 </details\nThanks for reporting. I am willing to fix this issue. /assign\n/language en\nShould I work on this issue\n/assign"}
{"_id":"doc-en-website-2ef3cd3bde987032564b81f56ec33f2e8bceb650635d5fa971d15d3410a7256b","title":"","text":"This is a Bug Report Problem: it seems that there is wrong indentation example- Proposed Solution: change to: path: / backend: serviceName: web servicePort: 8080 instead of: path: / backend: serviceName: web servicePort: 8080 Page to Update: Additional Information: This is the error thrown: $ kubectl apply -f example- error: error validating \"example-\": error validating data: [ValidationError([0]): unknown field \"backend\" in , ValidationError([0][0]): missing required field \"backend\" in ]; if you choose to ignorethese errors, turn validation off with --validate=false $\nThank you for your submission and have tried to fix it. /kind bug /language en /assign"}
{"_id":"doc-en-website-ea5533ae774bf9643fdcaeefc22e1f2621622a2ef1d2b0fc9e53f91b9d8ca44c","title":"","text":"~This is Support~ In the , i am able to see under Kubernetes Documentation. Respective tiled content buttons are aligned respective the content length or size. As a user , i would like to see them aligned as a bordered tile content with buttons are aligned look like a row irrespective of tile content length. This improves the user experience Please let me know if drawings are needed to understand.So that i can take a capture of it and attach.\n/area web-development /kind cleanup a mockup would be useful\n/priority awaiting-more-evidence (adjust this once the discussion has made it clear)\n- PFA.It is screenshot of button aligned.I have the tile border which is not the primary objective though(Just to border line the content) ! Hope this mockup helps.\n/remove-priority awaiting-more-evidence /priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nStale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten\nRotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close\nClosing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/reopen /lifecycle frozen /retitle Poor alignment between tiles and buttons on home page for docs\nReopened this issue. <detailsIn response to : /reopen /lifecycle frozen /retitle Poor alignment between tiles and buttons on home page for docs 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-kind cleanup /triage accepted"}
{"_id":"doc-en-website-abd586a38057194b51a27b7b6ab46ac5e582b21ffbffbca67ffa05acba679cec","title":"","text":"No navigation panel says anything about bound service account tokens. describes service accounts and their non-bound tokens. mentions them in a 4-th level subsection under automation in the admission controller (which omits the fact that the kubelet is also involved in automating bound tokens, see ), but that subsection is omitted from the TOC because it is 4th level. Apparently that 3rd-level branch is only taking responsibility for describing service account automation in the admission controller. Bound service account tokens are an aspect of the authentication functionality that should be described on their own right, in the page on authentication.\n/triage accepted\n/sig auth\nThere isn't really a concept page on ServiceAccount. If there were, we could migrate the content to that concept page, and then hyperlink to that new section from its previous home.\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\n/remove-lifecycle stale\nIn fact: /lifecycle frozen\n/priority backlog\n/sig security\nis somewhat relevant\n&hellip;until now:\nI reckon will close this issue."}
{"_id":"doc-en-website-1dd2c3431c2904276e018cb0403ec8adde540b13ab43e604a90ee1a3d089ff54","title":"","text":"ClusterReplicaSetPreferences docs point to a source code file in the main repo This also happens in /docs/tasks/administer-federation/replicaset/\nDo you mean FederatedReplicaSetPreference? I can't find ClusterReplicaSetPreference\nexactly! FederatedReplicaSetPreference is correct. Sorry for it\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\n/assign"}
{"_id":"doc-en-website-b5afe9625acd835bfb356724335541400d355ff53ffcc31c220548c4d068d851","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign"}
{"_id":"doc-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29","title":"","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":"doc-en-website-f74b0115e05bf15e2e0d8bdbfa0a03d57f315791ac08780f75f4be9463184846","title":"","text":"This section: I would add information like here: Note: In v1.22, if the user is not setting the cgroupDriver field under KubeletConfiguration, kubeadm will default it to systemd.\nthis section: already links to: PRs welcome with proposed improvements. /help /sig cluster-lifecycle\nIf someone wants to help here, I'm not sure what steps they should follow to assist. Because of that: /remove-help\n/language en\nI think the suggestion is to add something about to container-runtimes pages but I don't think that fits well on that page because it only covers the container runtime side. What could be though is that there's a note/reminder to ensure they are always the same. I can work on that if we agree what's what we want here.\nhmm, looks like this is already covered too.\nsome additional feedback in\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/assign"}
{"_id":"doc-en-website-b9b97b635b211fcadbcf336461efbdbe8ea320ad06426906ea27434f0027dd35","title":"","text":"This is a Feature Request translate content/docs/tasks/tools/install-kubectl- into Chinese What would you like to be content/zh/docs/tasks/tools/install-kubectl- /assign /language zh\n/triage accepted"}
{"_id":"doc-en-website-cf17f9181476a2ddbc5b1b625ece354489d0bea118662a7db8b76d9dac5fd79a","title":"","text":"This is a Bug Report While applying written in is triggering an error Whereas by removing the labels from the and Applying the kustomization directory to create the ConfigMap object get created successfully. <!--Required Information--Problem: cat <<EOF Here is the configmap created previously. Proposed Solution: Update it with suitable answer. Refer : for kustomization update. Page to Update:\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs /language en\nThe unknown field was in this commit and it was not supported refer to the code We can add labels via refer to I can help open a PR to update the code sections."}
{"_id":"doc-en-website-de266447b2e8fd5264e4270b5b629bdf359f0c642648e8ae0bc6fc009c7edba9","title":"","text":"Keep the doc consistent with\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-6ca3deaf78ebac97edabf246a49c2a44bee6fa6be2165f4e4d7ae30bdfad8709","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is giving 404 Proposed Solution: if doesn't have the pt version Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/assign"}
{"_id":"doc-en-website-55f173d13f9952dad1158823f2b7d8f29643fa4aa55024a98ad0523b44f8d29a","title":"","text":"This is a Bug Report Problem: [zh] /docs/concepts/storage/ephemeral-volumes/ is missing in Chinese version Proposed Solution: Add content/zh/docs/concepts/storage/ephemeral- Page to Update: content/zh/docs/concepts/storage/ephemeral-\n/language zh /assign"}
{"_id":"doc-en-website-9e90a60dde3c877195044c856ef4345c8a94695e37668a0563a21e6a268e0d5a","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--The typo in the example. The first \"game-config-2\" shall be \"game-config\"? <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The typo in the example. The first \"game-config-2\" shall be \"game-config\"? I believe the game-config-2 is the name of configuremap in 2nd example. Proposed Solution: Change the first \"game-config-2\" shall be \"game-config\"? Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nkubectl describe configmaps game-config Name: game-config Namespace: default Labels: <noneAnnotations: <noneData game.properties: 158 bytes ui.properties: 83 bytes The game.properties and ui.properties files in the docs/user-guide/configmap/kubectl/ directory are represented in the data section of the ConfigMap. kubectl get configmaps game-config-2 -o yaml\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":"doc-en-website-aec2f53cab89c905d7e2fb52af479dd2c3274906b838890432e7c3e8fc3cac3d","title":"","text":"Add a link that explains how the limits are enforced at the OS level. For example, a) How the \"shared CPU\" is allocated between various running containers? (e.g., how they differ from multiple java processes running on a plain vanilla CentOS VM running without k8s) b) What are the background processes that are managing these quota limits? (both k8s and OS processes)? c) How much resources are consumed by these background processes, compared to (a), (20%, 40%, 50%)? d) Can some of these managerial quota processes be turned off (e.g, to let OS handle the CPU sharing)? If yes, then how? If no, then why not?\nWhich page do you want to update? Do you have a link which redirects to the desired site ?\nthis is the page which mentions in issue link also . PTAL\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."}
{"_id":"doc-en-website-94f391ac04d3e66a833fbb50dd4df5cc5e913b4a7c2b00289dc7c05351284b35","title":"","text":"This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:\n/remove-lifecycle rotten\nHow about linking to /triage accepted /language en /priority backlog\n/assign"}
{"_id":"doc-en-website-873d0de31c74c7f24523ea4bed6f2b1708654c23e9945a845aecad223fb67587","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: I wondered what are the restrictions (if any) that Kubernetes imposes on the names of objects of a kind that gets defined by a CustomResourceDefinition. I am not talking about the name of the CRD itself. I tried to find this in the documentation, and couldn't. I asked on the channel on the Kubernetes Slack, and was referred to . The text there says Since a CRD is itself an object, I thought this was clearly talking about the name of the CRD itself (I temporarily forgot that I know that the name of the CRD itself is constrained to be ). But I was assured that this text is trying to talk about the objects whose kind is defined by the CRD. Proposed Solution: Update the cited doc to be clearer. Page to Update:\n/sig docs /language en\n/triage accepted /wg api-expression Since a CRD is itself an object, I thought this was clearly talking about the name of the CRD itself Yes, that's right. Both I and confirm this; I'm an emeritus tech lead for SIG Docs, and is a current tech lead. (sic) Would be good to add that detail to the page."}
{"_id":"doc-en-website-4019a5b5848a9fd820d633ac36fabfce16bf62ffd968d6551fc193bb1b311399","title":"","text":"Links to github on this page seems to be broken\n/triage accepted /assign\nAlso see issue"}
{"_id":"doc-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e","title":"","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":"doc-en-website-71ac5b8048cadd128b1abdc75e11c144d9986ff815d18f3a078448fd61f4673e","title":"","text":"This is a Feature Request Will relocate this file from to in which may involve some text updates and link fix.\n/triage accepted\n/language zh\n/assign\n/assign I handle the language/zh-cn\nRegarding assignee issue I share the following comment in the releated PR. :)\nYes, this is not a simple relocation, which involves with much localization of new paras and text."}
{"_id":"doc-en-website-3248c3b0cf27be3160c4e7eed39165a2f94659a3ab6d4bb2db3eb5d7dafdfff4","title":"","text":"This is a Feature Request What would you like to be Translate the following document 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":"doc-en-website-2808a5e97b5e7be025dfcc00d4fa4f0196a40a7917d6a1153c3f253be3ed6e7b","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update Why is this needed links are outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-44390e2844ca9d1fd3f15733e2c5d09aeb62ea1a46ae413cde50c1c53343af27","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-78928ba5a1eaa70b957a3b98a1d8cf04c04a411639623fe64793c55c84891316","title":"","text":"The page assumes one is using and as an architecture. The download commands won't work for e.g. / .\n/kind bug /retitle kubectl download page for Linux assumes amd64 architecture\n/language en /triage accepted /priority important-longterm Thanks for filing this\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 issue has been marked as an important bug and triaged. Such issues are automatically marked as frozen when hitting the rotten state to avoid missing important bugs. Please send feedback to sig-contributor-experience at . /lifecycle frozen\n/assign"}
{"_id":"doc-en-website-9558cf9917263d844174e8ab737d598330dbe444b7c5abbe583ce50a10ea8297","title":"","text":"This is a Bug Report Problem: Glossary term id and title must be same as per the current design. But for Glossary , term id is documented wrongly as whereas title and file name is . Proposed Solution: Update term id from workloads to . Page to Update: <!--Additional Information:--\n/language en /sig docs /assign\nI don't think this is true. We prefer it if the term ID and the display text are similar though.\nHi ok, might be my understanding is wrong on it. But i was verifying the existing Glossary items, most of them are documented term id and title are same. Also if we use term id as in PR, build is getting fail and giving error as invalid term id \"workloads\". Test cases are accepting only if we mention term id as . is the related error, Thanks.\nLooks like a bug, isn't it?\nHi Yes, but I'm not sure if the bug is in the documentation or in the test cases. First, we must determine the correct term id among these two (workload/workloads), and then only we can proceed.\nI've gone through the other files in the and noticed a pattern that the id most often matches with the title itself. Hence for this, I believe workload should work fine. However, I'm not sure why a change in the id is leading to CI failure?\nThe glossary shortcode does care about the field? I don't think so. That is the reason why referencing the field rather than the file name sometimes failed.\nAny updates onto it?\nI looked up what is for: it's the fragment identifier on the glossary page.\nThe following is from the shortcode. is the variable used in the shortcode, then it is used to generate the file name of the glossary. The code never extract the in the glossary entry, right?\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at ."}
{"_id":"doc-en-website-08e2f1156a65ea7875a8dfac941a3dc79d72d4e85b71a2691d0b8dfe459c94ec","title":"","text":"/lifecycle stale [1]:\nIf we look at this, here it is trying to match which doesn't exist. That's why the error is comming if i am not wrong. What do you suggest to be done?\n/remove-lifecycle stale\nSIG Docs: Can you please have a look into this as its waiting since many days.\nIs there are fix proposal for this? /triage accepted\n/assign\nIMO we can change id to that will exactly match with existing filename which can fix the issue. I will propose a PR if OK.\nPR raised"}
{"_id":"doc-en-website-347acd50a47814ab392a4657544c33068afa1d4823b8bc786fdefca2715c4d37","title":"","text":"dns-horizontal- kube-dns-autoscaler dns-autoscaler 2\n/language zh\nplease describe the issue in English\npage related to the issue:\n/triage needs-information\nTranslate to English: The kube-dns-autoscaler used in dns-horizontal- and the dns-autoscaler used in subsequent commands are confused and out of sync. It seems that the English version also has this problem. /triage accepted /kind bug /retitle Inconsistent name in the DNS horizontal autoscaling example\n/language en\n/assign"}
{"_id":"doc-en-website-c6194e6889c7eadce3dabc1e5f18b3b4f62ca2abf0ce45003245d649a63da5d9","title":"","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."}
{"_id":"doc-en-website-6dacf3ddf43d755eb515703773c0fff747d89050cc7d9099ad5bf964a573a357","title":"","text":"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":"doc-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\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":"doc-en-website-b55d75b348e6af347998acf47ff2800883ce9c348bdb10387b26eff108d68543","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be enhanced? I think \"Subscribe to KubeWeekly Newsletter\" section at bottom of Home page is:- too much white/grey space that can be shortend. input area where user will enter his/her email id is a little small and maybe it will be better if that gets a little enlarged. <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --!\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 web-development\n/priority backlog\nPage:\n/good-first-issue The files to edit can be found in assets/scss\n/remove-help /remove-good-first-issue Don't label issues as good first issues unless they are also triaged as Accepted\n/assign\nwhen we shorten this white space I feel there is no need to enlarge the input area as it aligns perfectly once shorten. !\n/close\nClosing this issue. <detailsIn response to : /close </details"}
{"_id":"doc-en-website-99753022dfebf9d2675bda906258b2c03fed778eac641e22ae206044b9243163","title":"","text":"This is a Bug Report Problem: is mis-configured for markdown files, and is stripping white space at the end of lines. Markdown uses these spaces for formatting in some casees. Currently, if the .editorconfig file is being used (via plugin or whatnot), then these formatting cues can be removed on save. Proposed Solution: add the following after the section in the file. dotfile to Update: .editorconfig Test environment MacOS 10.14.6 Both of: VS Code using neovim using\nGood spot /kind bug /triage accepted /priority backlog\n/assign"}
{"_id":"doc-en-website-507a5fa3d61731a60dd8b0d85fdcc0bbac059aaff7640b1e4c7cfe56cdef8465","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Documentation - description is not fully inline with current version. Current text: \"Non-resource paths include: /api, /apis, /metrics, /resetMetrics, /logs, /debug, /healthz, /swagger-ui/, /swaggerapi/, /ui, and /version.\" The following non-resource don't seem to exist anymore: '/resetMetrics', '/swagger-ui' ( swagger 1.2 was deprecated and functionality seems it was already removed), '/swaggerapi'. The non-resource path '/ui' would need more checking, but it seems is part only of some tests. Proposed Solution: Description should be updated accordingly. For example, the text could be updated as: \"Non-resource paths include: /api, /apis, /metrics, /logs, /debug, /healthz, /livez, /openapi/v2, /readyz and /version.\" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--{ \"gitVersion\": \"v1.18.2\", \"gitCommit\": \"\" } <!--Additional Information:--\n/assign\n/priority important-longterm /language en\n/kind bug"}
{"_id":"doc-en-website-8d0c6a328169f0869059233626a5de0d654ddb1f11fe3d35f2a909aee5f345ac","title":"","text":"restartPolicy under initContainers is not allowing to create Jobs specified into the below documents Error Message: Job in version \"v1\" cannot be handled as a Job: strict decoding error: unknown field \"[0].restartPolicy\" Document Link:\nHi I believe the error message you are getting is because you might have used feild under the section. But it is not allowed under the . /language en\nPage related to the issue: /sig docs /sig node\nHi , Below is the Job configuration:\nCould you please provide the code block with proper indentation?\nupdated above section\nThe indentation should be corrected as below\n/kind bug\nmentions a feature gate, but doesn't make it explicitly clear that you need to enable it. The feature gate is named . The fix I recommend: add a brand new page edit to direct readers to that new page /remove-kind bug I don't think there is anything actually incorrect. /triage accepted /retitle Unclear documentation about sidecar containers\nIs anybody working to fix this issue? If no, i can take it.\n/assign\nFeel free to involve me, if you need any help.\nSure, Thank you.\nPR raised to fix the issue .\nAlso see\nTo learn more, you can read (but not plagiarize)\nHi, I also having this problem I tried to add restartPolicy as to under containers and init containers, but I get the same error. I do not got any errors for the restartPolicy, but and are gave the error mentioned at the top. Im using Minikube, and my CC: Your suggestions highly appriciatable\nLooks like you are using 1.27, but this feature was in 1.28.\nThanks I updated my k8s Even though I can not use and in both places. ( and I put this marker in the above comment). It says,"}
{"_id":"doc-en-website-2b62fde3b6c9de3d34a5db803d9ec0633641559656f4a18ec8a85ca8dd2921db","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In section of Node Pressure Eviction Page, a Note is referred to the deprecation section of that doesn't exist. Proposed Solution: The Note should be removed as there are no deprecated flags for kubelet garbage collection. Page to Update: /sig node\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 Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:\n/remove-lifecycle rotten /assign"}
{"_id":"doc-en-website-19fc1330b797d0e35b379d295daa29fcc534e9129b8451e00edc06684c2a0353","title":"","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":"doc-en-website-1074e52fbca84f0b6710b4911b77c66c931cfc0456a346eab39cd05085ac7f1f","title":"","text":"I will localize this blog to zh-cn version. To avoid any conflicts, this issue is opened. /assign\n/language zh\n/triage accepted"}
{"_id":"doc-en-website-7c686c6c7e9e52d9e2a1fa8203151d2bb124d7e31251a8975e1295f5404ee32d","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\nI've already translated this page, but currently, the branch is not created so I haven't created the PR yet. I'm going to create a new PR for this page after a new branch is created. The commit I've translated is here: Japanese: PRPR\nmasterPR\n/close\nClosing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-863c075457a65bde9f4c492af6636bdf601eb0786afd4dcdae56c016f0956a33","title":"","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."}
{"_id":"doc-en-website-4619f0673c85cf15c5e7519c5473b97ccd2e8da37d5237923670459732563959","title":"","text":"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":"doc-en-website-cc2f4be79248a428830496563bd6b73c081083a0beddfc31255b8a31b5e6e909","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --In , update the link URL from to update the link URL from to update the link URL from to update the link URL from to update the link URL from to update the link URL from to Why is this needed redirects to , which is a fork of and currently 62 commits behind . The latest commit of : on 29 Oct 2021 The latest commit of : on 12 Feb 2019 and for other CNIs, it would be better to use the final URLs than using redirecting URLs. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update:\n/assign\n/triage accepted /kind cleanup\n/retitle Fix incorrect / outdated URIs in list of network plugins /language en /priority backlog"}
{"_id":"doc-en-website-c13c957046d9284c4b197dc0dab24af187eedff0267caf6ac93d4fc2427389b1","title":"","text":"This is a Feature Request What would you like to be add translation about: Why is this needed do not have this article in chinese for now. Comments /language zh /assign /sig-docs\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-73fd36df0b11a972f64baf2e341bbd5d0281bb7eaafb992abfbc52873cb100a8","title":"","text":"I have a catastrophic problem with my production control-plane just because I naive believe in the instruction of the output of . My control-plane was gone and I couldn't recover from the failure because could not restart. After some tests, I found that need to be so that it tell the to use the correct internal IP that allow both new control plane and the current plane to talk to each other. Specifically, those IPs should allow etcd to communicate throw both servers. Without the default IP interface was used, but the firewall that I set on the default IP did not allow etcd to connect through. At this point, I would like to make a change to the document in a way that it emphasize the importance of in the command.\n/language en /sig docs /kind feature\nPage reported in issue: /sig cluster-lifecycle\n/retitle Highlight the significance of in kubeadm join for HA cluster setup\nall k8s components work like that. not only kubeadm. if you want custom IP from a different interface you need to pass it to the advertise address flag, but also as --node-ip to the kubelet. overall this setup with private IPs is not recommended and is difficult to manage. instead you should make the setup so that the public IP is the default route. then firewall the cluster properly. PRs for the above \"create cluster\" page with a note fix are welcome. the note can talk about \"init\" and \"join\", public IPs and firewall. /help /sig network\n/triage accepted\nactually, let me try to send the note. /remove-help\n/assign"}
{"_id":"doc-en-website-ea1cccfc179c7a487297c9253d39ff7efdebafa1ecbfeb4b22e29011021468f5","title":"","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":"doc-en-website-49446c8a4c85d999b7103b13c5a93e213ed672e53bb3624dfd6d9ff33d8ffc5c","title":"","text":"This is bug report Due to the prow source code was moved along with ghProxy to the repository on April 9, 2024 so there is invalid link in for . Problem In this , which is redirecting to the invalid page Solution Give the right path location for\nPage to update\n/sig docs /language en\nI will raised PR for this. /assign\n/kind bug\n/priority backlog /triage accepted"}
{"_id":"doc-en-website-5e2b0562e6c7d4d270937fe8ae84fccf84d87342c55540811cf24dbb3bbc2395","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: line 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":"doc-en-website-e25372679a1ae4e8a519f69ed80315fe9d788a6496495ce883b82d6c681e7e7f","title":"","text":"Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text 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":"doc-en-website-fc4ca23a2a6f4051cf0b25800460e23abdd7e428834daefb3e7657dad72c27f9","title":"","text":"Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text 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\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-bb999599dcc5d1adfdd9e331f35a7946b453607463016b7728dac0cc5bfb41e1","title":"","text":"This is a Feature Request The red banner introduced with is too intrusive. Most Kubernetes users don't actually care about this deadline, and there is no way to dismiss it. What would you like to be A simple \"dismiss\" button that sets a cookie to hide the banner in any future visit, like other websites do. Why is this needed I'd argue that most users of the website just want to read the documentation, they aren't going to submit images to that registry, so the warning isn't useful. Comments This could be reused for future banners.\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 Add way to dismiss banners in the K8s website We would implement this for all banners, not just red ones.\n/area web-development\noh boy! are you in for a ride!!\nxref: also, here's how i deal with papercuts on the web -\nWhich all banners are you referring to? I'd be willing to take this up.\nThere's a banner displayed now, it looks like this: ! Imagine if you could click to acknowledge that you'd read it and didn't want to see it again for a fortnight. (separately: does feel relevant - ruled out taking action as they don't plan to push a container image there, which I think reveals a misunderstanding. I think it's worth repeating banners every couple of weeks in case it helps a message to land better).\nWhich ...To clarify for anyone reading: This banner applies to pulling / downloading container images from the Kubernetes project, this banner is aimed at users, not Kubernetes developers. Nobody can push directly to either of these hosts and the change isn't related to pushing / submitting images.\nThanks and for the explanation! I'll take this up and try to resolve this. /assign\nare you working on this issue? I would like to help if you want. Do let me know.\nYes, I'm working on this still, mostly it's completed already, but thanks for the offer!"}
{"_id":"doc-en-website-5e755246cb15c4805b4739ab935dd0533a391a56162fd9010c33c731b9ff5f38","title":"","text":"The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\nAs XDRAGON2002 seems is evaded, could you please proceed?\n/remove-lifecycle stale\nI'll help with this, it seems like a good feature\n/sig docs"}
{"_id":"doc-en-website-69dd19060a8fcdbb148c3217193b9a7b9fb47722f9f95d64c928e6c229babd9e","title":"","text":"This is a Feature Request What would you like to be Translate docs/reference/glossary/secret into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign"}
{"_id":"doc-en-website-e341681a44ba2e9345f104e6bd15f892dc8ef892490de9f911ac35d01a5b63f2","title":"","text":"This is a Feature Request What would you like to be Add a comparison between the CRDs and API aggregation layer. should explain this - but doesn't! Why is this needed It's needed so users can understand the difference between CRDs and API aggregation layers.\n/sig docs /sig api-machinery\n/trick-or-treat\n! <detailsIn response to : /trick-or-treat Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nWe can take some reference from this to understand the difference between and .\n/triage accepted /wg api-expression\nThis issue looks interesting. I would like to raise a PR for more explanation. /assign"}
{"_id":"doc-en-website-e3d5660009f41c7c01b0472eb3af219351dc33fd6e829931622470d730d16a2a","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: isn't rendering correctly. Proposed Solution: Fix the Markdown for this page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language it /kind bug /priority important-longterm"}
{"_id":"doc-en-website-f0e8fbd693a842b67e3977cff6ee6e47bd55aeff6a4bc4e14de538d688f4d840","title":"","text":"Several of the types used in AdmissionRequest does not seem to be documented anywhere. The links point to the general Kubernetes API docs, but the actual types does not seem to be defined there. Searching in the docs does not turn up any obvious references, and neither does web searches. Types missing documentation:\n/sig docs /language en\nYes, no documentation for and But for , it should be . The doc is here:\n/triage accepted /assign"}
{"_id":"doc-en-website-632b7fc6594a662f40331ff19c227bc66b5521a16f7973e1cdb1135c20038df6","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --About Some corrections need to be made. Why is this needed JSON in .dockerconfigjson dump is strange. Lack of options for kubectl command. And some more correction is needed. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja\n/assign\nThe Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:\nThe Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:\n/remove-lifecycle rotten because the related PR is under reviewing /triage accepted"}
{"_id":"doc-en-website-77c3fc9e2e9391e5e015b7c9f18cdc0b6a49a751030e056a2e4eead533148014","title":"","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":"doc-en-website-81aad4a071b61b59bd0d35dd312618c39d9b1f6623dbfa221fa2c5a57b71b244","title":"","text":"The specific location of the document is The documentation says You can acquire all these from the nginx https example. This requires having go and make tools installed. The link of the Chinese document is: he cannot access the link of the English document is: accessible\n/triage accepted /language zh /kind bug\n/assign"}
{"_id":"doc-en-website-ac720335fdfc1e41d807ff44e34bdc2f1bb9f7d62243b8e49d0312bc238c169f","title":"","text":"This is a Bug Report The glossary tooltip for is referencing section, instead it should reference to page.\n/sig docs /language en\n/assign\nfixed\n/retitle Incorrect glossary tooltip link for 'Container runtime interface' /priority backlog /triage accepted"}
{"_id":"doc-en-website-401f86e97ec17e3bb2ffb3cc118b0ae93bf660c4d58289d42712cfee5cb589c8","title":"","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":"doc-en-website-d4709e7875707525d37f38598da68fe3bb69fd80a3452e27a78912f17872d063","title":"","text":"Hello, I noticed some punctuation errors on page /language zh\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign"}
{"_id":"doc-en-website-2814bbe638e841c08a3005e420da9bec85177a6c7dd9086f3e659856291ad338","title":"","text":": \"Switching to another Kubernetes package repository\" and particularly the one for CentOS/REHL shows commands for Debian based system, not REHL based rpm\nI'm not seeing this. Can you point out where there are deb commands for RHEL? !\nExcuse me it is for old versions: https://v1- https://v1- https://v1- !\nI'm also not able to see this for Old version?? !\n/retitle Broken tab layout on \"Changing The Kubernetes Package Repository\" page in older doc versions /kind bug\nThe problem stems from the existence of two tab layouts on this page having the same name \"k8sinstallversions\". This issue has been resolved in the branch. To address this issue in old docs versions, we'll need to backport and apply the fix to each corresponding old branch (release-1.25, release-1.26, release-1.27, release-1.28). Considering that the older versions of the documentation are no longer actively maintained, there's a question of whether it's worth investing efforts into fixing this issue.\nI don't think it much important!\nI'd support a backport. One of the things we do want people to learn to do with older Kubernetes versions is: to upgrade them! /triage accepted /priority backlog\nI can try to help with this. /assign\nI think the backporting is done which resolves this issue\nIf it is ok we can close this issue\nThe fixes have been back-ported to the older release branches. Closing this as completed. /close\nClosing this issue. <detailsIn response to : The fixes have been back-ported to the older release branches. Closing this as completed. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-fff038ba39281fa9f68f4f7cf1c791e9a9867e0cc8c10d6ff8d148e851ce8d68","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: 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":"doc-en-website-216cec239c90f2580ea262db5992b101dc21d3387d4557c8063d80c919fabd7f","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign /triage accepted"}
{"_id":"doc-en-website-34f37d6f94778872134c41bb68d6f0e64cdcef7bb83ab0ce96f15af4f7727d36","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: 1 file changed, 1656 insertions(+), 2119 deletions(-) for Korean is outdated. Proposed Solution: Update according to 1 file changed, 1656 insertions(+), 2119 deletions(-) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko\n/assign\nParent issue :\n/milestone dev-1.20-ko.1\n/triage accepted"}
{"_id":"doc-en-website-9ba392b392e4c6eed5c44520a0185cae0e55e235f376532b6b3cc265c62c70f7","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/triage accepted"}
{"_id":"doc-en-website-391a1f9249aecf915e9cf612979895361f8623d75675478f9fd35addec47169c","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Client Libraries lists 3rd party software. Kubernetes docs allow content for third-party projects only when: Content documents software in the Kubernetes project Content documents software that’s out of project but necessary for Kubernetes to function Content is canonical on , or links to canonical content elsewhere Proposed Solution: ~Remove links to 3rd party client libraries~ Sort list alphabetically Page to Update: Additional Information: Part of umbrella issue /language en\nThere was some discussion in about this. What was the outcome?\nThis is also relevant to\nWe discussed this in the 2020-06-23 SIG Docs weekly meeting. proposed flagging the third party client libraries with an cautionary note about quality. recommended ensuring that all client projects within are linked to notes that this is strictly content as outside what's allowed in the but that it is useful to a wide user base also points out that client libraries in general (whether in-project or otherwise) are useful to make Kubernetes work as you want it to? This content is unique (there's not a good alternative page elsewhere on the web). What's important is to identifying an owning SIG and having some means to keep the list live and relevant. Removal is held until the end of the v1.19 release cycle, so positive discussion before that date is helpful and I encourage it. /sig community /sig api-machinery we are conflicted about where to put this; we're not sure it fits inside documentation any more - would SIG Community be interested in hosting this list? what are your views on this list, in light of\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : We discussed this in the 2020-06-23 SIG Docs weekly meeting. proposed flagging the third party client libraries with an cautionary note about quality. recommended ensuring that all client projects within are linked to notes that this is strictly content as outside what's allowed in the but that it is useful to a wide user base also points out that client libraries in general (whether in-project or otherwise) are useful to make Kubernetes work as you want it to?"}
{"_id":"doc-en-website-2720502c559ab16256609e095cf497029eabfa7df455bfad4f30e4cedcccf014","title":"","text":"/sig api-machinery we are conflicted about where to put this; we're not sure it fits inside documentation any more - would SIG Community be interested in hosting this list? what are your views on this list, in light of Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nRaised visibility in\nsadly some projects under the org is not actively maintained. those libraries (go/java/python/dotnet/js) already linked are fairly active. can we consider to append a new link for C/C++ which is newly & active months ago? i wonder if the community-maintained list is stale b/c it seems rarely updated. also i noticed there's a number of repos stopped maintaining for 1-2 years or even longer period of time: am slighting leaning on keeping the community list as most of these projects are driven by individuals instead of dedicated vendors -- the more we have the better?\nShould this issue remain open? Thanks!\nI can see one thing that still needs doing /retitle Sort third party client library links so the link text is clearly in alphabetical order. Order by language then by URI.\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\nThe remaining sorting is straightforward; if it weren't for the issue history I'd say it's a good first issue. /help /kind cleanup\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 : The remaining sorting is straightforward; if it weren't for the issue history I'd say it's a good first issue. /help /kind cleanup Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-306a58c1ed6c0c7dfa1c0858b792a4745f1fdfd48a79d1b92dbc573eb210cb6d","title":"","text":"This is a Feature Request What would you like to be Update README- Why is this needed has been updated after translated Comments /language ja\n/triage accepted"}
{"_id":"doc-en-website-4475c98cf955b9915a0331d4febab584317cdd1c4bc791c0cf078a2425b62729","title":"","text":"This is a Bug Report Problem: includes dead link to at the bottom of the page\nI guess it is here -"}
{"_id":"doc-en-website-c0d57aec86df1376d3ec04424329d82067ef5e5d6e3d0dd7db443b1baef8569d","title":"","text":"Ref: needs a rewrite. It mentions Docker (and Podman!) all over the place, which is a good indication that the docs are old enough to need a rewrite. At a minimum, remove mentions of Docker in these topics: /triage accepted /milestone 1.24\n/assign\n/assign\nReasked folks in Slack for correct disposition\nAsked in the SIG Node slack channel:\nTo summarize the consensus from talking with folks about this issue, specifically the examples in Using a Private Registry section: The steps in the Using a Private Registry section are still valid. However, as written, it makes it sound like Docker is the only/recommended way to do this-which we dont want. We should be able to remove the docker examples and point folks to this page , which covers most of the same content with third party disclaimers already written into the examples. I plan to open a PR later this week with these changes!\nHas anyone opened a PR for this issue? It seems to be referring to"}
{"_id":"doc-en-website-f5ca4e7c732d79358694b85cd7a4fad02529153508209689df11d0838223e8b7","title":"","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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Add \"event\" entry to the Kubernetes . Why is this needed s are referenced several times in other definitions, but it is not itself defined.\nCaution for people working on this: there is an API in and there is also an audit Event type in . The glossary entry should help readers who are confused between the two /language en /triage accepted\n/assign I would like to work on this\nAwesome, thanks"}
{"_id":"doc-en-website-392aed2b61040b168cc752cc19b1c2b35603956e76a73adc2fe66037d56a841e","title":"","text":"I created a new deployment \"mydeploy-dotnetcounters\" with two containers, one with resource request and limit set and one without. The new deployment had these labels: The HPA for a different deployment \"mydeploy\" started to fail with: The \"mydeploy\" deployment had these labels: I resource request and limit to the second container in the \"mydeploy-dotnetcounters\" deployment and the HPA for \"mydeploy\" recovered. It seems that the HPA decide what pod to check based on what labels match. However these is no mention of that mechanism in the HPA documentation ( that I could find ). Not here: And not here: I expect the HPA for one deployment to not be affected by the configuration of another deployment. I expect that I can read about the mechanism by which an HPA decides which pods' metrics to examine. Create a deployment with an HPA. Create a second deployment that is a clone of the first, but with an additional label and with resource request cpu not set. No response <details</details<detailsGKE v1.20.11-gke.1300 </details<details</details<details</details<details</details<details</details\nThis issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig docs\n/sig autoscaling\nThis really belongs in the repo /transfer website\n/language en /triage accepted /priority backlog /kind feature Thanks for the suggestion\n/assign"}
{"_id":"doc-en-website-d707ea5e76e769653992e0383c489fca9ef7919324f1320d3587246539cb6af9","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: Links in the Terminology section point to (obsolete?) documents. Proposed Solution: Point them at master. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nthanks! Addressed in PR"}
{"_id":"doc-en-website-6d0b3c0979783df3196daac80bc8f9f110fd5a9abb60930128ca2fa97a53ac9c","title":"","text":"The Chinese version of this blog is missing. I will localize the blog. To avoid any conflict, this issue is opened. /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-ae88bd577b26ced3a92976b9bf1de88f1e09fd1fc07f48a446965776b7be7f86","title":"","text":"I would like to have the \"Container Environment\" page to be translated into Italian page /language it /priority important-soon\n/assign /lifecycle active"}
{"_id":"doc-en-website-0d78ef1906dd1bc2e088499c1132d3c3a92b9f54c80f13180a6be95c584f315f","title":"","text":"FEATURE STATE for feature says According to page it is still alpha, being first introduced in 1.22. Should not the FEATURE STATE line then say ?\nPage related to issue: /language en\n/retitle Empty feature state tag for \"Memory QoS with cgroup v2\" in \"Pod Quality of Service Classes\" page /kind bug\nWe should fix so that the correct feature state is reflected. /priority backlog /triage accepted\nIt appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI will want help with this. /assign"}
{"_id":"doc-en-website-4b07e2cb0e465c81b6502364e84d0f7fdb19e5e4c835c0a4d3136e4fc61ce076","title":"","text":"'[ API]'s link is 404, there needs a Chinese doc for 'Gateway API'. The website is and the target website is\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\nPlease describe the issue in English\n/language zh\nPage related to the issue:\n/triage needs-information\nMy description is already English.\nyes, The gateway page have to be translated in Mandarin language.\n/help\n/remove help This issue is not ready for a new contributor to work on.\n/remove-help This issue is not ready for a new contributor to work on.\nMy description is already in chinese when I clicked on !\nThe issue is about the page\n/assign ops, 404 link, I am working on this."}
{"_id":"doc-en-website-bc77df4a722a5290f8f21b899c52b8c0aed47feb928eb6c53cc93c051b8a453f","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: has not been updated to track the enhancement in Proposed Solution: Update that page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/sig api-machinery /assign\nGitHub didn't allow me to assign the following users: borgerli. Note that only with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: has not been updated to track the enhancement in Update that page. <!--Kubernetes Version:--/sig api-machinery /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\ncan you please take care of this too?\nSure, I'll make a PR to update the doc.\n/triage accepted"}
{"_id":"doc-en-website-174097c07c8e7ab5e6c25e4d980e4793943a41e2fddd6e865f7558a0eb2bf024","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Add a page titled “Upgrading Linux Nodes” Why is this needed We have an for Windows. Someone who runs Linux worker nodes may well want to see a page just like that, but explaining what to do for their Linux-based node OS. It is OK to adapt existing pages and to link to them. Comments /sig cluster-lifecycle /priority backlog /language en\nHi there is a section on in the , which has the content for upgrading Linux worker nodes. I wonder do you want a separate document for it?\nYes. This issue is a request for a document just like but with Linux in the title. It is OK to adapt existing pages and to link to them.\nright, i can recall the section only says: From the Windows node, upgrade kubeadm: and no addition for another os. This will be helpful. are you working on it?\nThanks, for the information!\nHi thanks for your comments. Yeah, I am working on it. I will soon open a PR for it.\n/assign\n/triage accepted\nI have raised a PR: Please take a look!"}
{"_id":"doc-en-website-ceed0f46698337115cafeb19d14b277652ac93926f82984016091ac396a83095","title":"","text":"This is a Feature Request translate docs/reference/glossary/garbage- into Chinese. What would you like to be content/zh/docs/reference/glossary/garbage- /language zh /assign\n/triage accepted"}
{"_id":"doc-en-website-7d81cba4e890155fabc33052f31d247b6edba4519db1a303689694a215125a61","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Add a comment to the example Kubernetes client config in Why is this needed Storing a password in a Kubernetes client config is risky, and we have an opportunities to call out other options. Comments A good alternative is a and separate secret storage. /language en /sig security\nonce this issue is triaged, I'd expect that contributors look at the issue and decide whether they know how to resolve it. If you - or anyone else - aren't sure how to resolve a particular issue, that's OK. In that case, you have a few options: ask in Kubernetes Slack for advice for this issue specifically, WG API Expression or SIG Security might be able to offer advice around good practice with password storage look on the web using a web search engine. For example, has links to pages that might offer advice here look for a different issue to work on. With over 200 other English language issues open, you may find another issue that you do know how to work on. It's OK not to work on an issue that you don't understand how to fix. In general, asking the person who reported the issue isn't the best way to get help. Sometimes they may know exactly what is wrong but not have a clear idea about what to do to fix it.\nIf you decide that you don't know how to work on this then I recommend that you unassign yourself, so it's clear to other contributors that help is needed here.\n/triage accepted"}
{"_id":"doc-en-website-05793bce3bf596c30743efff4e1a3e1af94fb5a63083aa8e0b7af350ee5aba99","title":"","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":"doc-en-website-e557c973ce5c3fa0d2ef5618ce9421fef2a4fc47be8d42d69bd1e6bc3495c4e2","title":"","text":"This is tracking issue of our progress from Q1 2021 onwards. In the beginning of this milestone, as per our , we have translated 220 pages from 84 contributors (the script from main repo shows 260+ pages), with around 8,000 views per month. In this milestone, we still continuing on updating the obsolete pages. We are not officially listing down target pages to translate, but feel free if you have spare time to translate some. Please check this documentation about which gives step-by-step on how to start to contribute and translate using official guidelines. There is a list of outdated pages (40 out of 162 pages for this milestone) and please feel free if you want to take part on this work."}
{"_id":"doc-en-website-7cc82ba248fb595f1863e462429db19f302adf4f74450183fcd1bc3ab85cab26","title":"","text":"[X] removed [X] removed content/en//docs/tasks/tools/install- [X] removed [X] removed content/en//docs/tasks/example-task- [X] removed content/en//docs/tasks/administer-cluster/cluster- [X] removed content/en//docs/setup/learning- [X] removed content/en//docs/concepts/configuration/assign-pod- [X] removed content/en//docs/concepts/configuration/pod- [ ] removed content/en//docs/concepts/configuration/manage-compute-resources- [X] moved content/en//docs/concepts/configuration/resource-bin- [X] moved content/en//docs/concepts/configuration/taint-and- [X] renamed content/en//docs/concepts/scheduling/scheduling- [X] renamed content/en//docs/concepts/scheduling/scheduler-perf- [X] renamed content/en//docs/concepts/scheduling/kube- [X] renamed [ ] removed content/en//docs/concepts/workloads/pods/pod-[ ] removed [ ] removed content/en//docs/concepts/workloads/controllers/jobs-run-to- [ ] removed content/en//docs/concepts/extend-kubernetes/poseidon-firmament-alternate- [ ] removed [ ] removed content/en//docs/concepts/cluster-administration/cluster-administration- [ ] removed content/en//docs/concepts/cluster- [ ] removed content/en//docs/concepts/cluster-administration/cloud- [ ] removed content/en//docs/concepts/cluster-administration/controller-[X] removed content/en//docs/concepts/cluster- [X] removed [X] removed [X] removed [X] modified content/en/includes/task-tutorial- [X] modified content/en/docs/home/supported-doc- [ ] modified [ ] modified content/en/docs/tasks/debug-application-cluster/resource-usage-[ ] modified content/en/docs/tasks/run-application/horizontal-pod-autoscale- [ ] modified content/en/docs/tasks/run-application/horizontal-pod- [ ] modified content/en/docs/tasks/run-application/run-stateless-application- [ ] modified content/en/docs/tasks/run-application/force-delete-stateful-set- [ ] modified content/en/docs/tasks/tools/install- [ ] modified [ ] modified content/en/docs/tasks/configure-pod-container/configure-service- [ ] modified content/en/docs/tasks/configure-pod-container/configure-persistent-volume- /language id /cc\n/triage accepted\nI'm taking the 4th part, as I've done the in\nThanks ."}
{"_id":"doc-en-website-f7e9609ca612cbb0442d2bb9cec81d3a682a9f473daf2e633a93c9726ebf9e85","title":"","text":"it is updated.\nis moved to as mentioned here\nis removed and redirect to official minikube webpage , as mentioned here\nThe whole pages are move into including as mentioned here\nThe whole are removed in , I'm going to remove the directory as well as it's unused now.\nis moved to via\nis removed via\nJust sharing a useful trick for finding related PR which delete/modified a file: e.g. The output will be similar with this: Please note the commit hash in the output (, in the case of the example above). You can use the same command to find which commit modified a file by changing the filter from to (refer to for more filters). In case of modified file, you might get multiple commit hashes, pick the latest one (contains the recent changes), or just pick ones that suit your needs. Go to, e.g., (replace with your commit hash in step 1). Find the related PR with the commit, e.g. via web UI: ! In bottom left hand corner near the branch name, in this case , you can see the PR id . Click on the link and you will be redirected to the respective PR page, then you can analyse what changes has been made and what actions needed to incorporate it to our localization.\nis removed here together with others.\nis removed here\nHi ... it seems this issue is automatically closed. Do you have any idea how to re-opened it?\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\nThanks :)\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\nHi .... I think we need to close this issue, because it has already behind the schedule. Do we need to complete all within 1-2 weeks? or we need to carry forward to next quarter?\nHi All, I have opened Q2 2021 tracking issue"}
{"_id":"doc-en-website-126f2b4b934adf197fa09d20636f13cc9d9425f89f017bcdea5f26095e288d63","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The documentation on Pod Topology Spread Constraints indicates: Proposed Solution: The documentation should read This feature went default-on when it hit Beta in 1.18 per the [Feature Gate Reference] () Page to Update:\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-6e10bb851593f30736a275d2429ff6cd2a0b392be8967f313f48c54073fdb40d","title":"","text":"Hi Team As per the documentation link: Kube api-server is supposed to validate the keys for secret type: However, I have observed that secrets are still being created if the valid keys are not in the secret manifest. apiVersion: v1 kind: Secret metadata: name: secret-basic-auth type: stringData: username: admin # required field for\nThanks for mentioning this. What's not right about the documentation, in your opinion, /language en\nAs per documentation, for the secret type: , they keys (username, password) are validated during secret creation. However, I am able to generate this secret of type without mentioning password key in the manifest. Is the documentation correct? If yes, then validation is missing?\nIt sounds like you're saying that specifically is wrong. As well as removing that text, we make it clear that “must” means ”you are expected to ensure this” and not “your cluster enforces this“. /triage accepted If you want the cluster to enforce that those keys are set, you could make a feature request As an aside: would be nice to document some ValidatingAdmissionPolicies that do enforce this rule.\n/assign I will create a PR for fixing this.\nFixed in /close\nClosing this issue. <detailsIn response to : Fixed in /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-c0795a37b777bbb07342654b08f1ff1996f707787bcfd1d9ef33c2a76999ad78","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [X] Bug Report Problem: The link \"build-tools/\" doesn't work anymore and returns 404. Proposed Solution: Fix the link Page to Update:\nFixed. Thanks!"}
{"_id":"doc-en-website-4c25fec0e0da9485ba1c07a43b6b26241ff3d0e0d17251f6516f16796f7ae81e","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: Page url: in line 83, click PetSets guide occur 404 error. Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nFixed."}
{"_id":"doc-en-website-7d3fe46dc5c033c3dba5d785154b4628ed19dee190c783302a5f25cac3def5b7","title":"","text":"This is a... [ ] Feature Request [X] Bug Report Problem: link \"Minikube installation guide\" points to which is 404 Proposed Solution: fix the link by making it absolute: Page to Update:\nFixed."}
{"_id":"doc-en-website-426385cb735db2a5d2dfe0abd63d894358d30a3461a177fd3c82f9c2c3d70a55","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: Multiple links on the page generate 404 Not Found Examples: (redirected from ) (redirected from ) Proposed Solution: fix the links Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nHere is the full list of broken links on xhyve driver kvm (driver installation) xhyve (driver installation) See DRIVERS docker-env command minikube start minikube stop minikube delete full CLI docs"}
{"_id":"doc-en-website-fb434cfff9f10c632cd4e9d8ca66f0e52a2edeed826c1908a3288710b8be5a58","title":"","text":"I wish /docs/user-guide/horizontal-pod-autoscaling/walkthrough/ actually contained the information, or at least a link to autoscaling by custom application logic (as referred to by the first sentence in the article - . The second half of this article seems like the correct target link -\nFixed. Thanks."}
{"_id":"doc-en-website-68fd3cc97aa76d3867e42410c5604d65a120a78a8d063d108fc689e1c8be3bc6","title":"","text":"This page returns 404 not found.\nYup. It was moved over to a different folder ...\n/language en\nThanks! Do you know what is the currently available link for the English doc? The search is not very helpful btw, the Chinese link is still working though...\nWell, I think we should move it back. Proposing a fix now. If it turns out that team doesn't want to move it back, we may need to add a redirect entry as an alternative.\nlet's discuss the move back in this issue. Can you set out a case for reverting?\nSure. I'm assuming that there are audiences from different user groups reading the docs and even learn by doing. A long while ago, we (primarily chenopis) started an initiative to provider journeys for different group of users. Some of those efforts are still , archived into a directory. The idea was to help users find the materials they need based on their roles in operating or using Kubernetes. This background is where I came from. For cluster operators (or admins, or whatever you call them), they often times enjoy a higher privilege (aka more responsibilities) to keep the cluster running healthily. That means they need to ensure the following things work properly: access control and admission control storage provisioning and networking setup auditing, logging and monitoring upgrade cluster config secure cluster data and backup them properly ... These are not concerns of an application developer. An application developer uses the cluster to deploy, scale their applications. For example, they rarely have a say regarding when to evict a Pod out of a node and they cannot decide whether and which upstream DNS server is used. Similarly, a cluster operator doesn't care that much how application Helm charts are composed, version controlled. A production deployment is pretty different from the minikube one we use for learning and erring. So ... DNS and related tasks is not an application level thing. It is a cluster administering job. That is the reason I'm proposing this (partial) revert."}
{"_id":"doc-en-website-3c92c8fe65e93bab71dbed52583bc0fc693d67e4248b3ad9045c5701d988b397","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The cluster autoscaler uses an annotation, . However, we don't list that annotation in Well-Known Labels, Annotations and Taints. Proposed Solution: Update Well-Known Labels, Annotations and Taints to mention the Pod annotation and why you might use it. We could mention that you typically set this annotation in the Pod template within a DaemonSet and that you don't set that annotation on the DaemonSet itself. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en\nI would like to work on this. /assign /sig autoscaling\nFixed it here:\n/triage accepted"}
{"_id":"doc-en-website-7eedb3986c79b1352dabe1638f8f86161888b95adb18e5c497cc8b05f44bfd6e","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: I saw an out-of-tree product mention that static pods \"can not use\" ConfigMaps and Secrets. I was unaware of such a prohibition. I went looking in the k8s website. I spent a lot of time not finding any mention of such a restriction. For example: mentions static pods but not the restriction; describes ConfigMap and Secret type volumes but does not mention the restriction; the Go sources for the relevant API types do not mention the restriction (). I eventually found the restriction wrt ConfigMap mentioned in , but I think it should not appear only there. Proposed Solution: Update either or both of the first two pages I cited that currently lack the restriction. Update the API types to mention the restriction. Page to Update: Listed above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/triage accepted\nI can work on this one. Thanks. /assign\nI just realized there is an additional --- and more severe --- restriction on static pods. They can not have a ! As a corollary, they are not given a by default. For example, using a static pod: ... note that there is no ! is one place where this would be relevant.\nThe prohibition is even broader and simpler: the definition of a static pod can not refer to any other API object. For example, PersistentVolumeClaim is another thing that a static pod's definition can not reference."}
{"_id":"doc-en-website-e34093bba3db13b222938482d29cd031aedd7b97c833318fb7130475d92462f8","title":"","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":"doc-en-website-526a642fb0018ad3d855ee68d67706adccaffad8076b156b2fc2119fa8bb5338","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Replace the diagram in with a SVG-format vector equivalent. Consider switching from rows to columns - that will fit better into the available white space. Why is this needed There is an ASCII-art diagram in the page at This gets the point across but looks a bit unpolished, and readers might think that the feature is also not finished. Comments /kind cleanup /language en /priority backlog\n! How about like this ? color also can talk about :)\nI like that look. I would use the Kubernetes blue and gray colors - maybe blue for pods, gray for kube-reserved and system-reserved, no color (or white) for eviction-threshold.\nall right. /assign"}
{"_id":"doc-en-website-770a24e94a0e0a0a92e0bbe9ad23cbd547cddf4adaedb9b3dd751249876d7dc3","title":"","text":"I have noticed that the blog meta links (e.g. the twitter link) on sidebar of blog pages are opening in the same tab, while on other sections of the website, they are opening in a new tab. What I would like to be updated- I would like to change the target attribute of the links in the blog section to \"_blank\" to make them open in a new tab when clicked. This helps improve the user experience by keeping the user on the current page while still allowing them to access the linked content. Impacted page Thanks!\nI'm not sure opening each and every blog in a new tab or window is the right choice for everyone.\nhi, it is only opening the sidebar links.\n/triage accepted\n/area web-development"}
{"_id":"doc-en-website-7dec0a773546e9f3818b3c8d59955de950e26bca34e60fe75dbd3392b0cf90ba","title":"","text":"This page is outdated according to the comment of this ticket, because if you follow the instructions, you always get an error like the one below in any worker node when you execute: where is:{ \"metadata\": { \"name\": \"nginx-sandbox\", \"namespace\": \"default\", \"attempt\": 1, \"uid\": \"hdishd83djaidwnduwk28bcsb\" }, \"linux\": { } } E0107 22:25:16. ] \"RunPodSandbox from runtime service failed\" err=\"rpc error: code = Unknown desc = failed to setup network for sandbox \"888e1ca106ad4e8439154c056cbf6d926b1417c43aba37f8a5052a916e5f8516\": plugin type=\"calico\" failed (add): pods \"nginx-sandbox\" not found\" FATA[0000] run pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox \"888e1ca106ad4e8439154c056cbf6d926b1417c43aba37f8a5052a916e5f8516\": plugin type=\"calico\" failed (add): pods \"nginx-sandbox\" not found` and seemingly it is due to \"calico daemonset watch apiserver to get a list of pods, and apply network configuration based on the pod spec.\" So, the page may be deleted or the list of sections below removed:\nPage reported in issue: /language en\n/retitle “Debugging Kubernetes nodes with crictl” is outdated\n/sig node\n/triage accepted\nFunny, one of the reviewers of the doc, is the same person, that posted the note in the containerd issue, In fact, we don't recommend user to run and on a Kubernetes node , those commands are there just for some special debug case.\nAs per my investigation, all example commands work fine in the except for the mentioned sections. As per the referenced issue, I think it should be safe to delete the specific sections instead of a whole page. The documentation also has a warning message under section which refers to the sections that need to be deleted. So, if these sections are to be deleted then the warning message should be deleted as well.\nstill has the same example as included in . So it can very well be a bug."}
{"_id":"doc-en-website-a88d056325c10f1fd3ff76675a6888e08165b6fdaf01ae73c8fe7f0e09457628","title":"","text":"/cc Would it be okay to delete these sections in the documentation? If so I would like to raise a PR for the same.\nthank you! Please propose a PR with the changes. We may also link to the official docs.\n/assign"}
{"_id":"doc-en-website-e3ae386fd4db0893367e9b8fda7048b845d258ad98a92fb460957a5b9252f6ce","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.\n/triage accepted\n/assign"}
{"_id":"doc-en-website-6243c4b64017c12b3eae7280d7e7ac7c2209d2ce4321a32b166c8b0b08b7d386","title":"","text":"The script actually defaults to k8s version 1.1.8, but the docs says it is 1.1.4\nThank you for the PR, Mike!"}
{"_id":"doc-en-website-f31c48d684145f1c2fe1a94cf5332da3ebc4344cbf167cbda245b0f72f0d7a11","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x] Feature Request [ ] Bug Report Problem: In the 4th paragraph in the \"What is a Pod?\" section, there is a sentence: \"Containers in different pods have distinct IP addresses and can not communicate by IPC.\" The paragraph seems to imply that different pods communicate via IP. But it is not clarified. Proposed Solution: Please clarify how different pods communicate since they cannot use IPC. 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\n/remove-lifecycle stale /assign"}
{"_id":"doc-en-website-ffd4ebaf606ed66267358cfc14655843035c4bf62a19bf07faf3043933aa0ae4","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be The version of the crictl in \"install kubeadm\" doc when installing without package managers is v1.17.0. It should be v1.22.0. Why is this needed I think it should be updated because newer versions are available unless there are compatibility issues with Kubelet. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This is where problem exists:\n/sig cluster-lifecycle /triage accepted /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /sig cluster-lifecycle /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nHello, I would want to work on this issue as my 1st PR . Can you please assign this to me :)\nHi I think you can start working on it and submit a pull request. I do not know how to assign it to you.\n/assign\nThanks. Just to confirm I have to change the crictl version to v1.22.0.\nI'not sure. Maybe kubelet is not compatible with crictl v1.22.0 or there was another reason.\nthis matrix might be out of date, but according to it =1.16 critools are compatible with =1.16 kubernetes:\ni'd say just send the PR to update and if something breaks for someone users will report it. (our current e2e tests are not using the latest 1.22 critools release...)\nOkay sure. Thanks I will send the PR"}
{"_id":"doc-en-website-78ebf7c2255782b1615d453ce52e87a860b1a29d4663b070d2af87ff46951bbe","title":"","text":"Using a desktop or laptop PC and Brave: Many (all?) pages on waste a lot of screen space esp on the right edge. The pre-formatted text blocks on these pages are cut off, while there is plenty of unused screen space next to it (if you scroll down a bit). Sample: <img width=\"1519\" alt=\"Screenshot 2021-10-15 at 05 52 52\" src=\"https://user-\"Of course you can scroll these text blocks horizontally, but esp on large pages with many code blocks this is distracting. I would like to read the text without scrolling horizontally. Obviously a lot of screen space is used for the menu on the right edge, even though it is not visible most of the time. Do you think this menu could be put somewhere else, e.g. on top of the page, below the index on the left side or to some kind of popup?\nThanks We use We'd definitely consider a different layout. I think for us to triage this, we'd want to see a sketch (wireframe? mock up?) of how the site would work differently. Perhaps a button to collapse / uncollapse the right-hand sidebar? Another thing we could do, because the cheat sheet is one of the most popular pages, is change how we render that one page. We definitely have the technical means for this. I'd want to be convinced that the change we'd make wouldn't adversely affect someone else's user experience. /language en /priority awaiting-more-evidence\n/area web-development\nMaybe this change would be enough (edit ): If someone wants to try that, go ahead. /triage accepted /priority backlog /remove-priority awaiting-more-evidence /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."}
{"_id":"doc-en-website-d467bd4e6116d0179dc46cb645a985166d4225ba60b0802327871cd31cc63fbe","title":"","text":"If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Maybe this change would be enough (edit ): If someone wants to try that, go ahead. /triage accepted /priority backlog /remove-priority awaiting-more-evidence /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\nIt feels a bit weird since the solution was already provided above, after adding the CSS from above it looks like this, should I go ahead and open a pull request for this. !\nHappy to have someone work on this. Please go ahead! /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 : Happy to have someone work on this. Please go ahead! 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 afro-coder was looking for issues with no assignee and this on propped up therefore the assignee :)"}
{"_id":"doc-en-website-b0fe9b3234e742051dd695f662559052c675f7107eb7c6570cd190e1f6fe8477","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [ X] Bug Report Problem: SSH Tunneling link is broken Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--"}
{"_id":"doc-en-website-a01b7fb7c5a3a26f7c6e43d5730a59a50b3e55b8665ca1f8ec01497597c344b7","title":"","text":"This is a Bug Report Problem: page contains the following broken links: If we go through the Running ZooKeeper, A Distributed System Coordinator Introduction. If we go to click PersistentVolumes it should redirect us to PersistentVolumes Page but it shows us Volumes Page which we have to rectify here! ! Proposed Solution: Fix the broken links by Updating it to: Page to Update:\n/sig docs /language en /assign\nhey Can you look into this issue!!!!\n/retitle Incorrect link redirection on \"Running ZooKeeper\" tutorial for \"PersistentVolumes\" /kind bug\n/priority backlog (or lower) /triage accepted /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /priority backlog (or lower) /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 Incorrect link redirection in \"Running ZooKeeper\" tutorial page for \"PersistentVolumes\"\nThanks\nBut I have to work on this issue!!! I have self-assigned this issue to myself, Why someone else has raised a PR For this ??????"}
{"_id":"doc-en-website-c1ae5b6ee3437bc5d760f3103a94388e3ef2cce1528b5f68ff71c14f7efa47ea","title":"","text":"This is a Bug Report Problem: The of PodSecurityAdmission is mentioned under . Which is wrong, the correct one is . Proposed Solution: Change the from to . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\n/sig auth /assign\nFixed it here:\n/triage accepted"}
{"_id":"doc-en-website-118fa112b2f829df963c52f8a03a2c019195e20088572055bb55098d09f75e41","title":"","text":"This seems to be a typo, shouldn't it be traffic-distribution and not trafic-distribution ?\n/triage accepted /good-first-issue Yep, looks like that was a typo in the recent updates.\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\n/language en\n/retitle Typo in \"Service\" concept page /kind bug"}
{"_id":"doc-en-website-73758b576c572cd2066645cb8a6e15fa08689ac6a7d77c741cdb3510e428aaa4","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [ ] Bug Report [x] Documentation request Problem: Can we use equality-based requirement selectors like this in yaml/json files: Proposed Solution: Clearly mention if this is possible and if so include a small example. 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\n/remove-lifecycle stale /assign"}
{"_id":"doc-en-website-480e8a10405cccb6c157f2ae7ca8a86f3fc0603ff2c2e50f935043ee276e4c90","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: When somebody configures shell completion for , the instructions explain how to turn that on for your current session. However, that advice only works if the reader picked the approach in the “User” tab. If someone picked the “System” tab, the advice does not help them update their current session. Proposed Solution: Change that page to advise the user to run Some other change that also helps the user, regardless of which approach they took. Page to Update: Additional Information: Prompted by /language en /priority backlog\n/triage accepted\n/assign"}
{"_id":"doc-en-website-ca886486e57b4b0d670eb8a5ad5feed9feaa5ca742b50d8f6c3979e03e4bc4b5","title":"","text":"This is a Feature Request Since v1.16, extensions/v1beta1 has been deleted and it should not be used in docs What would you like to be The following pages should be edited due to this deletion. [ ] [ ] [x] [ ] [ ] [ ] [ ] [ ] [x] [x] Why is this needed extensions/v1beta1 is deleted in 1.16 Comments\n/kind cleanup /priority important-soon (I think)\nIf you are looking at this as potentially something to contribute to, it's OK to suggest a PR that fixes only one page, or only some pages. If you do that please mention “Partial fix for issue ” in the description of your PR.\nthanks for contribution here. Could you please share which pages would you take? Let us make the assignment more clear and help other contributors easily start their work.\nThank you for your comments. I wrote the target file into PR titles. And I will write to the comment about netlify demo pages and original pages to enable checking the diff easily."}
{"_id":"doc-en-website-7b12cbb6062a4d7fd8a6566b26aeff44c1faf514d3d655285f27322bf636759b","title":"","text":"\"The works with the NGINX webserver (as a proxy).\" The URL given against the text \"NGINX Ingress Controller for Kubernetes\" is not working. It returned 404 error(Page not found) in my case.\n/triage accepted /kind cleanup"}
{"_id":"doc-en-website-74c91f5959de05a53f7ea09880d9e5471986aa6d7e98c5a4a0c1552f9b99915b","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be The documentation for container runtimes at: needs to have a clear warning that by adding the suggested change in , this will actually PREVENT from successfully initializing a cluster (this is my experience multiple times with K8s 1.20.4 on Ubuntu 20.04 with containerd - not Docker). Why is this needed The current wording does not indicate that the suggested change for containerd's will actually break things. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --It is not clear even why that suggestion is there given that it stops from working.\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 current text reads: How would you reword this How about: When using kubeadm, you must manually configure the cgroup driver for kubelet. /language en /priority awaiting-more-evidence /sig cluster-lifecycle\nThank you for all the work that you do, related to Kubernetes and all other open source projects you contribute to. Your efforts are really appreciated. My own experience is that the configuration snippet there is actually harmful in the scope of using kubeadm. I realize now that the page is discussing how to use containerd with the systemd cgroup driver in general... but the typical person coming to the \"\" documentation is there to learn how to use containerd in the context of kubernetes. That makes that configuration snippet a bit out of place since it will actually prevent the usage of kubeadm. For this reason, I believe it is better to be crystal clear and explicitly mention all of that. \"To use the systemd cgroup driver... [plugins... ... SystemdCgroup = true However, when using kubeadm to initialize the cluster, the above configuration should NOT be done (it will actually prevent kubelet from bringing up static pods)."}
{"_id":"doc-en-website-4933149324763025021df9f47e9fc0464d9cc04bd6d01909d5f4157639c8e889","title":"","text":"Instead, manually configure the cgroup driver for kubelet.\"\ni don't see anything invalid on the page, but ideas for clarification are welcome. When systemd is chosen as the init system for a Linux distribution, the init process generates and consumes a root control group (cgroup) and acts as a cgroup manager ... ^ the above already explains when the systemd driver is needed. it is the opposite. if you are using kubeadm, you must configure containerd with . and then pass the same driver to the kubelet as explained here: cgroup drivers have been confusing users for a long time and this is really a problem in the CRI spec. there is a plan to automatically handle them but this might take a while to complete.\nthis area of the docs is seeing some refactor, so you can add comments here too:\nThis is the source of our difference:. I have tried that setting multiple times (at least 4 times). It does NOT work for me on Ubuntu 20.04. When I do NOT specify that setting in containerd's , then and ONLY THEN does it work... for me.\ni just tried following our documentation for installing containerd / installing kubeadm / creating kubeadm cluster. everything works fine for me: also a number of different CI setups are running kubeadm like so, you must be failing something in your setup. i doubt this is a containerd / OS bug of sorts, but it could be. /kind support\ndid you restart containerd after you : the step here should be after the driver is changed, so that's a documentation problem:\nopened PR for this: (it also closes this issue)"}
{"_id":"doc-en-website-d720ea7220331452267e3112064a3a37462b2af0ba815ce9d30f5f602e2d2b23","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Links to some ephemeral volume types are wrong. Proposed Solution: In , update links as follows: → → Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-1929a9d1e69e84954e6108acbd3cdaaae8b37d3d7ab3ccb234964071476346b8","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-5ac7e580a4a5047db0654ec0a0cf56ab21ddf4774ed7446ea4c6b3ae65392382","title":"","text":"Since is a page better suited for those learning Kubernetes, the , and forced storage detach on timeout section is better suited to be on the See comment thread:\n/language en /sig docs\ndo you feel like there is any restructuring of content that needs to happen with this move? Or is it a request to straight move those sections from one page to another?\n/triage accepted I think a straightforward move is the right change to prioritize. Extra help is welcome but not at the expense of delivering the fix later.\n/priority important-longterm see\n/assign\nsee if this PR does what you're looking for. Thanks"}
{"_id":"doc-en-website-b932e5138bdac8ff60059257a99b1e3f05fa7550982ca3ed7109086c4b58f753","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/triage accepted"}
{"_id":"doc-en-website-9b3f68408da684080e7c813f1b7f037197977987dafa1b3a18b0caeb7d892c88","title":"","text":"The existing documentation for Topology Aware Routing says however, this was before refactored and fixed the kube-proxy traffic policy problems caused by the lack of definitions on the Service traffic types This caused issues like fixed with , because we have mixed mode, If I understand correctly, right now and are not exclusive, since the former applies the traffic that is originated from \"outside the cluster\" and the later only applies to the traffic originated within the cluster. If that is correct , we should modify the documentation to say \"Topology Aware Hints are not used when internalTrafficPolicy is set to Local on a Service. It is possible to use both features in the same cluster on different Services, just not on the same Service.\"\n/assign /sig network\n/retitle Stale docs for topology aware routing constraints\n/language en\nThanks for catching this Agree with your proposed fix.\n/triage accepted /kind bug\n/assign"}
{"_id":"doc-en-website-3491998ca9d0249fcb811e88a528b383914b6756c02b859c1e76b9060db6f795","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate to Korean Page: Why is this needed Not translated yet Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ko /assign\n/triage accepted"}
{"_id":"doc-en-website-8da9faf21cf67d48887517c4e9a62fa4fe99cbeb8cc8645276f0f615ca4d96f8","title":"","text":"This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-be9cf93ca27737b56a0560eb1530a7657e00928813d668a116b58ae1ef887df6","title":"","text":"This paragraph is a bit backwards. It would be more intuitive to start with the \"Make sure that the br_netfilter module is loaded before this step...\" phrases.\n/language en /kind cleanup /priority backlog /good-first-issue Thanks\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 : /language en /kind cleanup /priority backlog /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/sig cluster-lifecycle"}
{"_id":"doc-en-website-e2c02c57260836e42ba79813059f27ea0428bb656297408b5674454e4e76341b","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: [zh] Need trans for <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/language zh\n/assign"}
{"_id":"doc-en-website-91b7687e0a28864e16407b9b77426bffe21b2ce4ff1d898f0432c634afad108c","title":"","text":"This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --- Translate \"\" Why is this needed There is no Japanese translation for this page Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/area localization /language ja /assign\nthank you!! /triage accepted"}
{"_id":"doc-en-website-5c32aa73237fd3238b7a2700d112aab7c7e0bb080d4f74a4f293a19f79845e24","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page has a heading, , that isn't actually needed. Readers can work out that the page has an introduction by reading the text from the start. Typically, we don't start our document pages with a heading such as Introduction; instead, we have introductory text before the first heading. Proposed Solution: Delete the line from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /good-first-issue /language en If you have already worked on an issue and have had your change merged, please consider holding back on this one. That will let other, less experienced, contributors find this to work on it.\nThis request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The page has a heading, , that isn't actually needed. Proposed Solution: Delete the line from <!--Kubernetes Version:--/good-first-issue /language en </details\n/triage accepted /priority backlog\n/assign\nI'm closing my PR and expecting new folks to actually contribute to fixing this minor issue. Feel free to raise a PR for this issue! /unassign\ncan I work on this issue! /assign"}
{"_id":"doc-en-website-76b43ec3128db4e03509c83c7e0f74b4f0688d6accebfb2bd3973dc4d482ca7a","title":"","text":"Umbrella issue: Remove the following from L6-8:\n/kind cleanup\n/language ko\n/assign\nThis issue is included in also."}
{"_id":"doc-en-website-6e5e0e23601c6efd16dd8f4195cbbff3beb947012c67189ad480595df9ec0b84","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Documentation contains an error: URL: chapter: kubeadm blocks when removing managed containers: Text in doc: Inspecting the logs for docker may also be useful: Error: This command runs into an error (on my ubuntu 18.04 distribution): Proposed Solution: Replace command with: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version: v1.18--<!--Additional Information:--\n/sig cluster-lifecycle /good-first-issue /help /kind bug it should have been or just let's go with:\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 : /sig cluster-lifecycle /good-first-issue /help /kind bug Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/assign"}
{"_id":"doc-en-website-9f431e84cce6aafc91323dc0d6775e295fe85f6f7d7de0d75aac3d1e39a263e8","title":"","text":"A link reference from to has the title text whereas the current title of that page is It will be a little less confusing if the link title was adjusted to be the same as the page title.\n/sig docs /language en /assign\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind suggestion I Agree on your point. If triage accepted, i will update this reference text from to that can avoid confusion. 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 Agree on your point. If triage accepted, i will update this reference text from to that can avoid confusion.\nThis issue got resolved with PR .\n/triage accepted"}
{"_id":"doc-en-website-c02cfe41918055372d864c0f3142661b3d8ce34aca8492374c633cbf911af2d1","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: 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":"doc-en-website-294bf34ec688d7f154f12ae076aa7df8a9009536b82d434f04217f7fda23237b","title":"","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":"doc-en-website-b0d96459fe356ea713f1d8d8f427c2c928b40fcedadf2efd81caea69a19595f2","title":"","text":"As part of \"Remove Docker Engine\", this page should probably also tell the user that may want to clean up space was consumed by docker, e.g. . Otherwise, potentially much space is left used but unmanaged on the node.\nSounds good. We could link to and similar page fragments; if we do, we should caution people that Docker's advice has a risk of trampling on containerd. Ideally, we provide just links to third party docs here. However, neither Docker Engine nor containerd has docs for migrating from one thing to the other (let alone any Kubernetes-specific considerations). I'm happy to treat that as a valid exception from the usual .\n/sig node /triage accepted /language en /priority backlog\n/assign"}
{"_id":"doc-en-website-aa94bbae7c17b3209db89fa80124d07bf7ae2c7befec859a57eb802e00c3789b","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: 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":"doc-en-website-10bf0ee45de357030d3db7fc1b41823d3018d30963d4cc4b74a64d74b1dac5e2","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Kubernetes previously paid attention to an annotation, . We now use instead. Even so, should document that annotation. Proposed Solution: Document that annotation; as a side effect, this registers it. I assume that we should also mark it deprecated. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog /sig scheduling\n/assign\n/triage accepted"}
{"_id":"doc-en-website-a2f7ea7b58605fcdf2cd646b47f6f97783109fe2cf3f9025cd372e7a506027b0","title":"","text":"This is a Bug Report The doc about finalizers doesn't give any information about the fact that the API server considers a deleted service account or a deleted pod's token invalid after 1 minute the DeletionTimestamp. ref: <!--Required Information--Problem: Proposed Solution: Document with a note. 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 en\n/sig apps"}
{"_id":"doc-en-website-62f2f27b522585ce62982dc29a1f12a055d8690cf1de08842fda4352a7a9cea0","title":"","text":"This is a Bug Report Problem: The of is mentioned in . which is wrong, As per mention in the the correct Feature state for is . Proposed Solution: Change the Feature State of from to . Page to Update:\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/sig network /assign\nFixed it here:"}
{"_id":"doc-en-website-e83ca0527a314375619d61e9fde6778ce6277d6565047a18aaf8b6bdf72780ef","title":"","text":"This is a Feature Request Hi, I would like to request a change made in doc page: It would make more sense if the \"Create Pod that uses the container runtime default seccomp profile\" section was after \"Enable the use of RuntimeDefault as the default seccomp profile for all workloads\" section, and not the very last option of creating pods with seccomp profiles. I feel like it would improve the flow.\nPage: /language en\nI am new to the kubernetes website project, Can I work on this issue ?\n/retitle Improve flow for Seccomp security tutorial\nAnyone can work on this issue, providing that they follow our .\nHi Are you working on this issue?\n/triage accepted\nif no one is working on this then I'm up for it.\n/assign\nHi will this seems valid to you?\nyeah I think having a slightly different order of the sections would make understanding the topic better. I'm in favor of that! :)\nthanks for your views on this. I will soon create the PR for it.\nFixed it here:"}
{"_id":"doc-en-website-e06362b8de3f22bab1054cc602defa2c98dc557f753555dde2be1666642d1f59","title":"","text":"This is a Feature Request The chapter that describes volume should mention field and recommend to use it when possible. What would you like to be should mention field Why is this needed This improves cluster security and should be always used when possible. Without a warning users might not know or just forget to specify this flag. Comments We might use a warning from as a draft and modify it accordingly. /sig auth /kind documentation\nThe label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : This is a Feature Request The chapter that describes volume should mention field and recommend to use it when possible. should mention field This improves cluster security and should be always used when possible. Without a warning users might not know or just forget to specify this flag. We might use a warning from as a draft and modify it accordingly. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\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/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 ."}
{"_id":"doc-en-website-5cb1fa97d52ab98d3d6ae1ab7bc893ac6d12937cd3a3f15ef2600188fc89d728","title":"","text":"/lifecycle rotten\n/remove-lifecycle rotten Still working on this?\n/sig security\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\nAdding the PSS as is the future as K8S 1.21 is deprecating PSP. All Documentation for mention Read Only should also be covered in this docf from now on.\n/sig storage /remove-sig auth\ndoes this mean that readonly for hostpath is allowed and working but just not documented ?\nyes, exactly\nthat is ownsome I was just going to rule out this solution because of the security issue. Thanks for your answer I'll test it right away.\nwell, I am using this manifest but I get this error\nthe VolumeMount on the pod spec allows a readonly setup but not on the Volume definition.\nYou're right and that's what I meant. Perhaps, I explained it a little vague.\nwell in that case I think you should close this issue as it is not an issue? the hostpath volume type does not support readonly but the container volume mount supports it and is documented here :\nMy point was that we can promote best practices by adding a hint to the documentation. Most of the people, don't read API specifications, they google and find a page with documentation. In this case, an advise of other options might be useful.\n/remove-lifecycle stale\nWould very much have appreciated if suggestion had been implemented; would have saved me a bunch of time looking for a way to mount a hostPath readonly.\n/assign I can add a note in"}
{"_id":"doc-en-website-50f308dc497e049ad8ebc592fd943a08ac4defceb0b845c84ae66c870404c97d","title":"","text":"When re-syncing , found that are being translated into \"\" and \"\" on the same page. I am confused about which word would be better when looking for documents. So I think it would be great if we reach a rough consensus and write into the in the Mandarin localization guide. Including \"\": 56 files / 229 lines / 243 words Including \"\": 68 files / 182 lines / 196 words Including both terms: 31 files It's hard to tell the correctness of files including both terms without reviewing them, it will cost a lot of time. So here is just the line count for occurrence of two terms. <pre<code 17 19 2357 <a href=\"\"content/zh-cn/docs/reference/access-authn-</a5 6 558 <a href=\"\"content/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-</a13 5 226 <a href=\"\"content/zh-cn/docs/reference/access-authn-</a4 7 526 <a href=\"\"content/zh-cn/docs/tasks/administer-cluster/securing-a-</a6 4 2410 <a href=\"\"content/zh-cn/docs/reference/command-line-tools-reference/kube-</a3 25 1383 <a href=\"\"content/zh-cn/docs/concepts/security/pod-security-</a3 4 903 <a href=\"\"content/zh-cn/docs/reference/access-authn-authz/kubelet-tls-</a3 4 1003 <a href=\"\"content/zh-cn/docs/reference/command-line-tools-reference/kube-</a7 3 1981 <a href=\"\"content/zh-cn/docs/reference/command-line-tools-reference/kube-controller-</a10 3 2033 <a href=\"\"content/zh-cn/docs/reference/access-authn-</a2 4 1630 <a href=\"\"content/zh-cn/docs/reference/using-api/api-</a2 2 2513 <a href=\"\"content/zh-cn/docs/reference/command-line-tools-</a2 2 1151 <a href=\"\"content/zh-cn/docs/reference/setup-tools/kubeadm/implementation-</a2 2 1091 <a href=\"\"content/zh-cn/docs/concepts/security/multi-</a3 2 1374 <a href=\"\"content/zh-cn/docs/reference/access-authn-authz/admission-</a15 2 603 <a"}
{"_id":"doc-en-website-00cc361d57665c9ef3ddf1b14dcd2dccc8f570641915933100afc2649183951a","title":"","text":"href=\"\"content/zh-cn/docs/tasks/extend-kubernetes/configure-aggregation-</a1 4 849 <a href=\"\"content/zh-cn/docs/reference/access-authn-authz/certificate-signing-</a1 3 668 <a href=\"\"content/zh-cn/docs/tasks/configure-pod-container/migrate-from-</a1 2 500 <a href=\"\"content/zh-cn/docs/tasks/configure-pod-container/configure-</a1 2 147 <a href=\"\"content/zh-cn/docs/concepts/cluster-</a1 1 1182 <a href=\"\"content/zh-</a1 1 344 <a href=\"\"content/zh-cn/docs/concepts/cluster-administration/system-</a1 1 373 <a href=\"\"content/zh-cn/docs/concepts/security/rbac-good-</a1 1 1140 <a href=\"\"content/zh-cn/docs/setup/production-environment/tools/kubeadm/create-cluster-</a1 1 370 <a href=\"\"content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-</a1 1 431 <a href=\"\"content/zh-cn/docs/tasks/administer-cluster/namespaces-</a1 1 519 <a href=\"\"content/zh-cn/docs/tasks/administer-</a1 1 645 <a href=\"\"content/zh-cn/docs/tasks/configure-pod-container/configure-service-</a2 1 2240 <a href=\"\"content/zh-</a4 1 60 <a href=\"\"content/zh-cn/docs/reference/access-authn-</a15 1 588 <a href=\"\"content/zh-cn/docs/setup/production-</a</code</pre\nOpinion: I found (Security Framework: identification, authorization, authentication, and permission control). As it said: mapping to authorization, and mapping to authentication.\nAccording to the official bilingual vocabulary list of Taiwan (temporary unavailable for unknown reason): is recommended to be translated to / is recommended to be translated to / / / / (Just for the reference, it's not that suitable for translation.)\nHope we can get inputs from active translators. CC\n/language zh\nwow, in my understanding, current authentication is with less confusion. Authorizer is recommended to use , and is for authorize and authorization. For most people, authz (authorize, authorizer, authorization) is related to for their first impression."}
{"_id":"doc-en-website-cdb663bac58083802a3c3e9fd5b6b147fe979f89b7fb47374a966daf999679b5","title":"","text":"This may cause some review efforts.\nI agree.\n+1\n+1 I refer to the localized content of AKS and EKS, and hold the same opinion. /triage accepted\nI think we all agree to the translation provided in . Hey may I ask you to add it into the glossary of terms? ‍\nOk, let me have a try to add this glossary."}
{"_id":"doc-en-website-97a7c83c93c2cd980605fcad0c62862d8890e7212379e83bce672e9da094b350","title":"","text":"This is a Bug Report Problem: In the Japanese localization of k/website, it is necessary to express \"controller\" as \"\" (not \"\"). In , it is expressed as \"\". ref. ref. Proposed Solution: fix \"\" to \"\" Page to Update:\n/assign /area localization /language ja\nref.\n/triage accepted"}
{"_id":"doc-en-website-9e07a14a27fe3e829c55169cba45a7548f69294159139b2202c92290ec7c9cba","title":"","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":"doc-en-website-982aeb364f8dfce8d68430ef16c26b036e8099de313bf68aeca2c21b434dc3f0","title":"","text":"Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /assign\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\n/close New tracked in\nClosing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-0c58f2e701d18fee353da8ab611d48b0d58646527ee40dfadeaf96b791b05a94","title":"","text":"in this section: we document the kubeadm skew against the control plane, but we do not mention the skew of kubeadm against: the kubelet kubeadm itself replace the section with the following to clarify all points:\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 </details\n/assign\nthanks for assigning your self. i've some quick edits to the text a couple of minutes ago.\nfound them\n/triage accepted"}
{"_id":"doc-en-website-1eaa797c254ca8401a413bccd7ee02da3b7f261e357f842667273c2ad44c6964","title":"","text":"<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: When I was reading this , I felt very confused. The meaning of this sentence is to explain that the node, volume, pod and container level information cannot be obtained from the summary API? But I read and code implementation: My understanding is: The node, volume, pod and container level information can be obtained from the summary API. So is an expression error? Proposed Solution: Enhanced description to avoid ambiguity or misrepresentation. Suggested modification: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--The English version of the original PR: /assign\nHi agree it needs fixing per I have a bunch of notes, please add your thoughts so we can clarify this matter. It is confusing.\n/language en The best place to add more notes is issue\nThanks for the reminder, I've comment to\nit sounds like the original author intended instead. Outputs definitely works too.\nUse as the word makes sense, thanks for the reply!\n/triage accepted"}
{"_id":"doc-en-website-5ade8775949ffdfcb4ee79c13436686ad5cba99f026286f5091e0c5be6fa8b46","title":"","text":"This is a Feature Request translate /docs/tasks/administer-cluster/migrating-from- into Chinese What would you like to be /zh/docs/tasks/administer-cluster/migrating-from-dockershim/index.m /assign /language zh\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details"}
{"_id":"doc-en-website-b265bf0fad0514d0ab89ed077ad3bcdcc64bbed832d933ecc22dc21027987e88","title":"","text":"This blog has not zh version yet. I will localize it. Open the issue to avoid possible dup. /assign /language zh\n/triage accepted"}
{"_id":"doc-en-website-e6f17f164eb2dc746e8cdbeb691b986404561b26de65c6273b27af551abc6a80","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: At 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":"doc-en-website-808cafbf55eb7b4debbe3b40475d0b24491d21f56f2be7419a5570e15cc416a0","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The Bold isn't effect in \"Auditing\", as shown below: ! Proposed Solution: Modify the format to make the bold effective. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--\nIf this issue been triage/accepted, I think I can fix this. /assign\n/sig docs /language zh\n/triage accepted\nThanks for the catch! You can fix it if you want.\nSure, let me fix it."}
{"_id":"doc-en-website-6dbe0dd4a9935f07fb375dfbcb3cada118bc71fd2dd89b0cde59ef902acd66cf","title":"","text":"Problem: The text on is not working, on the official website of weave, it has mentioned that the service has ended so; I believe it should point to this Check the page Installing Addons  for the problem. Page to Update: Suggested Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the text Weave Cloud account link to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, on the official website of weave, it has mentioned that the service has ended so; I believe it should point to this Check the page Installing Addons  for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the text Weave Cloud account link to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nI'd change: to\n/triage accepted\n/sig docs\n/assign"}
{"_id":"doc-en-website-b86f5e89c5eb4d26ad0a8fc5d443532a99120aa1dd78ea4e4548e80640b22e4f","title":"","text":"This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Through the progress with many contributors, the content of got a little bit unclear. ] (Most of the sentences are updated about 3 years ago.) ] Let's call the sentence Consequently, a volume outlives any containers that run within the pod, and data is preserved across container restarts. \"the sentence A\". In the paragraphs of the current version, the sentences ahead of the sentence A is not a basis or reason of the sentence A. Proposed Solution: Page to Update: /assign\n/triage accepted\n/sig storage"}
{"_id":"doc-en-website-d727e297796746a6d1da1ec8c1003298a151d0566782a0c688929011bcaa08f1","title":"","text":"<!-- 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 Link to at the end of Make this link particularly prominent. It should come before the other three links in the What's Next section of the page. Why is this needed directs readers to visit However, people who get to the end of do not see any link back to Comments This is a consequence of the Katacoda shutdown - - and our response to that shutdown. /language en /kind feature\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 Proposed fix in\n/good-first-issue (retrospectively)"}
{"_id":"doc-en-website-a6c3ef6aa91f26ea7d20eb51e2fbb7ce5ddb2ce218682b76b123192855fba473","title":"","text":"This is a Bug Report Problem: There is incorrectly translated content in docs/concepts/storage/volumes/#hostpath . in English: in Korean: Proposed Solution: Page to Update:\n/kind bug /language ko\n/triage accepted"}
{"_id":"doc-en-website-a6dac3c4c6dd8ba485304b998aa68be7e744562c79ae58b0623295f2356b0ae5","title":"","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."}
{"_id":"doc-en-website-303914100c60e82ccb16a5197eb63ebe8376aa98bc4cd417e62810e4ec82f153","title":"","text":"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":"doc-en-website-df5186f90374f670868ecfe208055187bcadeb0211b7636ea644fd8c5eebfa0c","title":"","text":"Cloning is only supported within the same Storage Class. Cloning has supported different storage class\nThis issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details\nHello It sounds like you might want to report that a web page is wrong. If that's right, what's the URL of the webpage? Also, could you quote or point out the text in that page that isn't right? /language en /triage needs-information\n/sig storage\nHi i would like to explain this issue if i am not wrong wants to update this . As is merged so now users will be able to clone a volume with a different Storage Class. The destination volume no longer has to be the same storage class as the source. But in current documentation we have the behaviour as. Cloning is only supported within the same Storage Class. Destination volume must be the same storage class as the source\nI would like to work on this. /assign\nSorry my bad.. Thanks for pointing it.\n/remove-triage needs-information"}