This is a Feature Request What would you like to be Translate content/ja/docs/tasks/debug/debug- into Japanese. Why is this needed This file is only translated the title, not translated the description and the body text. Comments /language ja
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign


If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign Thank you


If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign
Ahan! A great approach to helping new contributors. Sorry I missed that point. /unassign
Hello Team, This is my first issue on kubernetes/website. I would like to work on it /assign
Keep working on this issue. Feel free to raise a PR


This is a Bug Report Objective should be replace by उद्देश्य in content/hi/docs/tutorials/kubernetes-basics/create-cluster/cluster- <!--Required Information--Problem: Objective is english word in hindi content Proposed Solution: Replace with उद्देश्य Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/kind documentation
/assign


Umbrella issue: contains multiple "use cases" for Secrets. However, many of these are mini-tasks. In this issue, I'd like to discuss each of these use cases at a high level to see which we can remove, which we can trim, and which we can move to a new or existing task page. That way, the "Use cases section could even be a bulleted list with links to relevant tasks. Use case: As container environment variables Recommendation: Delete Justification: the goal is achieved in . This also isn't a use case, it's a way to use a secret. Use case: Pod with SSH keys Recommendation: Delete content, keep use case as bullet Justification: the steps add no value beyond the existing task to . Use case: Pods with prod / test credentials Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page. Use case: dotfiles in a secret volume Recommendation: Remove steps and keep as bullet point with additional info about why it would be useful. Use case: Secret visible to one container in a Pod Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page with actual steps to achieve more than just "secret visible to one container". Perhaps including RBAC steps. If you're interested, review each use case and leave a comment for each agreeing, disagreeing, or providing a different approach to each use case. After we've discussed and settled on an action for these use cases, we can start the actual work! /sig docs /cc
/assign
I think the "Use case: As container environment variables" can be removed as the goal is achieved in too.
Yeah agreed, although I'm separately removing that section and linking it to our existing task page as part of
Let's shift "Use case: Pods with prod/test credentials" and "Use case: secret visible to one container in a Pod" to and attach the link in the use case section as bullet notes.
/triage accepted
Imo the prod/test thing might not even need to move - it can live as an example in the concept but the task steps seem quite basic now that I think about it. Just referencing two Secrets in two different Pods...


This is a Bug Report <!--Required Information--From k8s v1.24 the and are no longer available as a feature gate in k8s. From v1.25 there is a separate document that contains information on feature gates that have been removed i.e. . In the and feature gate link to the page which is incorrect, instead of that, it should be page. The information for both feature gates is on the Feature Gates (removed) page not on the Feature Gates page. Proposed Solution: SupportNodePidsLimit and SupportPodPidsLimit feature gates should be linked to instead of Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/kind documentation /assign
For GA'ed feature or deprecated feature, if the gate is removed, we may want to remove the linking texts altogether rather than having existing text pointing to the outdate gate names.
Hi Just want to confirm it: So for this, you want to remove the whole note section for both feature gates, because both feature gates are removed. Am I understanding right?
is it seems good to you?
I meant this: move the "removed" feature to the dedicated page, if this is not done yet. The "removed" features will stay there for the sole purpose of reference. For all texts (including notes) that reference these gates, remove those references. If a feature is deprecated and removed, those texts may well become invalid. If a feature is GA'ed and removed, those texts may be still valid, but the reference to the gate should disappear.
Thanks, for your response.
and both feature gates were graduated in v1.20 and removed in v1.23. Both are present on the dedicated page i.e. . So I will remove the reference to these gates.
I will create PR for it soon.
Fixed it here:


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Add description that startupProbe successThreshold must be 1. Why is this needed The limitation has already been mentioned in the English page. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I checked startupProbe successThreshold must be 1. /language ja
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


This is a Bug Report Problem: Links for API compatibility and Kubelet Device Manager API Versions under in task are Invalid. It gives a 404 Page not found error. Proposed Solution: For API compatibility the link should be: For Kubelet Device Manager API Versions the link should be: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /sig docs
Fixed it here
/triage accepted


The content of the file version showed in section is wrong. Previous versions where showing the right content, e.g. .
The one in the dev-1.26 branch is not a valid Deployment manifest. The API server will reject this YAML since it is missing some required fields.
Ah, the problem might be that we don't want a YAML file that is a valid Deployment manifest, since this is actually being used to generate a special document used for a with custom Kubernetes semantics. /kind bug I didn't actually know that would accept a thing that's not a valid manifest for ; that's going to be hard to teach / document. Is that even a supported / recommended way to do the change? (I can see that it works; whether it works is very different from whether we endorse it). I think this is a valid report. Maybe we should use an inline example rather than an external file; maybe we need a way to exempt this one YAML file from validation. If we use an inline example, that would mean changing we can keep would need to change.
If this YAML has to be an "invalid" Deployment manifest, using an inline example is more appropriate IMO.
I'll also ask SIG Architecture if this use of is one we endorse.
Exactly, this is one of the "tricks" behind SSA: you only provide (to the you indicate). Providing a fully compliant (from an schema pov) Deployment manifest would actually be a mistake if you only want to modify the field using SSA. Kubernetes client-go was updated to support these non-fully-conformant-from-an-schema-pov manifests: defining the new types for this to be possible as described in this .
/triage accepted /assign
OK, so the input to is no longer defined to be a manifest: it's actually an apply configuration, and all valid manifests are also valid apply configurations. However, defaults to validating that the supplied apply configuration is a valid manifest. You can then turn off that validation by using . Have I got that right? If so, I think we missed a key docs update when we made that change to / client-go. is the only mention of the term apply configuration on the Kubernetes site; the docs don't describe this at all. The rest of this comment assumes that the apply configuration concept does need documenting. I think we should clearly document which subcommands work with manifests and which with apply configurations. For example, I'd have to turn to the source code to answer which kind the subcommand expects, and that's not something an end user should need to be doing. A few subcommands and plugins to consider: - -
I also think we should track a new issue for to document the apply configuration concept, and leave this issue to cover the specific bug that reported.
is solving the reported fault (so properly closing this issue), thanks for it. I think there is still room for improvement in the "Transferring Ownership" example this issue is targeting (maybe to consider it in a future update of these pages?): For the "more advanced" case (the one targeted by this issue) it is proposed to use a partial manifest; used term here should be "fully specified intent" as it is the introduced term at the beginning of this same SSA doc. page to name these "shorter" yamls we can use with SSA. In the final is not needed, better to remove it to not confuse the reader.


This is a Feature Request What would you like to be Translate tasks/administer-cluster/use-cascading-deletion/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


I was doing the step-by-step installation for v1.26.3 and found this as the final step for installing on Windows: installing the plugin, clean up the installation files: del Please correct me if I am wrong, but isn't the kube controller that I just installed? It isn't an installer, it's the product. Your instruction should not be to delete it. If I delete then I won't have kubectl installed anymore. Make sense?
/kind bug /language en /triage accepted For Windows, we don't provide our own installable package and the instructions don't explain putting the kubectl binary anywhere special. Until that changes, let's not advise readers to delete .
do we have to comment down or delete the 5th instruction there ?
/assign


In the third sentence on the second paragraph it reads: | operations, such as containerd or Docker. It is not clear if is a typo or a new term.
I believe writing "such as containerd or Docker" was not necessary because it was not very accurate , only writing till operations is fine enough . But still it is not an issue there .
is a container runtime that manages the lifecycle of a container.
/retitle "Using Minikube to Create a Cluster" unclear on meaning of containerd /language en Page to Update: For additional info, adding a hyperlink pointing to the corresponding official doc of the container runtime would be useful here.
I think the sentence is referring to the container tools and containerd manage the lifecycle of container on VMs.
Yeah, I get that. For someone new not familiar that this is a tool, might be confused. I originally thought it ws a typo and later realized it was referring to a dameon process. Not sure if there could be a link to docs of containerd so the reader won't get confused.
yes i also think adding link to docs of containerd would be useful for the reader to get clear understanding.
/assign
/kind documentation /triage accepted Improvements are welcome!
We could add a reference to our glossary entry:
/language en /priority backlog /help
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language en /priority backlog Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
It is not the only problem on that page, the description of minikube is not very accurate (anymore) either... But it will soon need to change anyway, when the online tutorials disappear, so probably time for a rewrite ?
/assign


This is a Bug Report Problem: Issue clarified privileges of kubectl debug node (through PR ) including " will fail" but in newer versions of Kubernetes 1.25 on EKS, works, although there may still be permissions issues as before. Proposed Solution: Change to " may fail" Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Created PR


This blog has not zh version yet. I will localize it. Open the issue to avoid possible dup. /assign /language zh
/triage accepted


Just like the pods and the control plane have hover which makes it easier to understand. There should be a hover that should explain what does replica mean here and in what context we are using it as for a beginner it might will be confusing to understand what replica is
Would you be able to provide us with the web page's URL that requires modification? If it's possible, it would be helpful to include the URL in the issue description as well. /language en /triage needs-information
Reference:
/remove-triage needs-information
/retitle Include in glossary and add tooltip for it on "Kubernetes Components" page /language en
Can I work on it now?
/triage accepted Anyone - including you - is welcome to open a pull request. This is open source in action! /priority backlog
/assign


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update translation /ja/docs/home/supported-doc-versions to current English version Tue May 31 06:54:51 2022 +0600 Why is this needed fix outdated doc Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


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:--
If this issue been triage/accepted, I think I can fix this. /assign
/sig docs /language zh
/triage accepted
Thanks for the catch! You can fix it if you want.
Sure, let me fix it.


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. -- page has some problems. -page link isn't working. resource metrics pipeline full metrics pipeline the Japanese page exists, some links jump to the English page. Pod Service Why is this needed it is inconvenient for the user. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted


Hello there, I would like to suggest adding a link to the CEL Playground in the Kubernetes documentation. CEL (Common Expression Language) is used in Kubernetes APIs, such as the , and the CEL Playground can help users easily test expressions. The playground also includes a set of examples and the . I believe the link would be useful on the following pages: The CEL Playground is available at and the source code can be found at I also invite you to test and contribute to the project. Thank you.
This 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
/sig docs
/transfer website The repo is not quite the right place to track this.
/language en /kind feature
If we add a link, I would add it to: (and I wouldn't add it to the reference page ; instead, we can have link to the three pages I listed above)
/wg api-expression
@ Hey which particular points on these links would you want the CEL playground. I will be glad for more clarification on this?
IMHO, a mention similar to the mention of on the would help: but saying that users can quickly test CEL expressions in the playground.
Hi I've opened a PR () with some suggestions for adding the CEL Playground link. Please take a look and let me know your thoughts. Inviting to share their thoughts as well.
I'm supportive of this. It's a wonderful tool and the community will benefit from being more aware of it.
/triage accepted


It is unclear what is meant by The statement appears directly under the heading "Creating a Deployment." It is confusing, and it is unclear what relevance defining an "environment variable" has to do with a deployment. Could it be that the author intended to present an action item of defining a pod, and linked to another article that coincidentally contained markup to do so? Suggestion is to clean up the paragraph, and link it to an appropriate article on defining pods, if so.
/sig apps
/retitle Unclear text in “Creating a Deployment” section of Deployment concept
/language en /help /triage accepted
I recommend removing from the page. That's a small fix that doesn't need us to work on the rest of
/assign
page to be updated:
Looks similar (possibly duplicate) of issue we already have
True. /triage duplicate
/remove-triage accepted
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-help Oops


It is quite unclear from that the feature "GenericEphemeralVolume" is a feature gate because its design does not follow the guideline. The following steps should be done: write the feature gate name as inline code, e.g. change the wording from "feature" to "feature gate" Also there is no information about the components on which this feature gate can be enabled. But! This feature gate is only in . Looks like it's not a feature gate now. Consider removing it from the page.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Page related to issue: /language en
/retitle "Ephemeral Volumes" page references the usage of a deprecated feature gate
/sig storage
feature gate has been removed in , the text needs to be updated.
/assign


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.
/sig docs /sig api-machinery
/trick-or-treat
! <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
We can take some reference from this to understand the difference between and .
/triage accepted /wg api-expression
This issue looks interesting. I would like to raise a PR for more explanation. /assign


This page should probably link to resources for defining standard annotations. Especially the thinks mentioned as examples. That would unify it a bit (for example contact address). Maybe link to
Page related to issue: /language en
/retitle Signpost from "Annotations" to "Well-Known Labels, Annotations and Taints" reference page
We can enhance the section by including a link to the reference page, as well as any other relevant pages. This will be beneficial in guiding readers to explore those additional pages.
/kind feature /triage accepted /priority backlog
please i will want to work in this! /assign
i have riased pull request please review.


In page , the first part describes that an online interative tutorial is included. But in fact, this tutorial was shutdown a few months ago. I think that may confuse some readers. !
/language en
Some replacement of words can fix this paragraph, but why katacoda/killercoda playgrounds are not used in these tutorial pages to make it interactive? /sig docs /kind feature
/assign
Seems like it's katacoda related.
Hi you don't need to translate anything. Just create a PR for english. (Optionally you can translate this if your know some other languages too. If you try to do so, raise a single PR per language.)
/assign
/kind bug /language en /remove-kind feature /triage accepted /priority important-longterm To discuss potential replacements for Katacoda (which has shut down), visit If anyone would like to support the Kubernetes project to set up or make use of a free replacement for Katacoda, you can: send financial to the Linux Foundation (very indirect support)
/assign


Config API needs to be localized into zh-cn.
/sig docs /language zh /area localization
/triage accepted
/assign


This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: [Install and Set Up kubectl on Linux] page layout is collapsed. Right side layout is displaced to down. Proposed Solution: Right side layout should be in place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: !
/language en /area web-development
I will try to help with this. /assign
(or any maintainers) Can i get some hint and go ahead to work on this please?
It appears that the changes in have inadvertently resulted in the layout of page broken. Potentially addressing could solve it.
We should fix the layout of the page. /triage accepted /priority backlog
/retitle Page layout for "Install and Set Up kubectl on Linux" is broken
/remove-area web-development This is more of a content fix.


This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs
This issue was created to be assigned to Could you add a comment here to assign this issue to you Edith, please?
Hi I would love to work on this translation.
/assign


This is a Bug Report While the left hand side navigation menu in Hindi and English is not fully matching and can create some issues for a native hindi reader . <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The option in English has been changed to in Hindi which can be an issue while navigating for a native Hindi reader. Proposed Solution: I have 2 options, I can change it to or . Suggestions required Page to Update: Screenshot(can be easily compared up) Hindi ! English <img width="960" alt="image" src=""<!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language hi
/retitle [hi] Navigation menu displays 'Home' instead of 'Documentation'
It appears that there is already an existing (umbrella) issue , addressing this request for all the different langauges. Additionally, there is already a PR raised specifically for the fix in Hindi language.
Marking this as a duplicate. /triage duplicate
if possible assign it to me i can work on it
You don't need an assignment to work on issues, Anybody is welcome to propose a fix Being said that, If someone will/has already proposed a PR, It's polite to co-author with them (but not mandatory)
This issue although addresses same type of issue as in , but in different place. is addressing specifically for footer across all localizations. And in this issue it is for Navigation menu and that too for specifically Hindi localized page. So, i think its better not to consider it a duplicate. For those, who want to work on it. Changing this key-value pair with value can probably fix it. !
Can I plz solve this issue? I want try do some localization cjhange to deepen my udnerstanding and help languages team where i can :)
/remove-triage duplicate Based on info provided in
Anyone is free to propose a fix by submitting a pull request; you don't require anybody's permission as we operate in the spirit of open source collaboration. Just a friendly reminder, these changes pertain to Hindi localization, so having familiarity with the Hindi language would be advantageous, although it's not mandatory.
Okay got it. Thanks! I will assign to myself in that case. /assign
I have riased plz review and let me know if its okay. Thanks in advance.


Problem: There are broken link in page. Proposed Solution: --Page to Update:
/triage accepted
/assign
Is the issue still open, anyone working?
Yes, I'm working on it!!
/area localization
I think has already raised a PR!
PR working on this issue


This is a Bug Report


This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign
/unassign


apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
Use kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
provide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information
Page related to the issue :
/language zh
/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm
/triage accepted /assign


The following links for Weave Net are no longer viable, and should either be updated (e.g. pointing to the GitHub repo where it is now maintained, , which again, admittedly needs to be updated, but puts the onus on the project itself), or the page should be completely removed: Google link-to-highlight: ,by%20the%20policies. This issue resembles
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Submitted PR with fix for review and merge. Can also remove page and associated links if this is regarded as a type of technical debt.
Page mentioned in the issue: /language en /kind bug


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Document (and register) the legacy annotation The page to change is: Why is this needed We try to document all of our annotations, even the ones we ask people to stop using. Comments /language en /lifecycle frozen /sig network cloud-provider
Could be useful, let's consider doing this. /triage accepted /priority backlog
I'd like to work on it /assign I'll share the findings here so the content is confirmed first.
How's this :
I got reference from cloud-provider-azure and Microsoft docs.
From it looks like we need a pile of other issues about unregistered annotations for this cloud provider.
Yes, you can find the other annotations here: https://cloud-provider-


This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --- Translate "" Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/language ja /assign
/area localization /triage accepted


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 ?
Page related to issue: /language en
/retitle Empty feature state tag for "Memory QoS with cgroup v2" in "Pod Quality of Service Classes" page /kind bug
We should fix so that the correct feature state is reflected. /priority backlog /triage accepted
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
This 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
I will want help with this. /assign


The section of the "Set Kubelet Parameters Via A Configuration File" concept contains a broken link that needs to be updated to point to the correct documentation page. The link labeled "reference document" in the following line is broken: Update the link in the markdown file to remove the extension, correcting it to the following format: Where to fix: File to change To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /priority backlog /language en /triage accepted /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : ## This is a Bug Report Learn more about kubelet configuration merging in the . ### Additional Information: To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /priority backlog /language en /triage accepted /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
If you've already worked on Kubernetes docs before, please consider leaving this issue for someone new to contribute.
I would like to work on this /assign
- Would you be willing to leave this issue for a new first time contributor to work on?
yes sure! I was confused about taking it on. I'll unassign myself
I would like to work on this as a first time contributor! /assign
if you'd like any advice, join our Slack workspace - - and head to #sig-docs
Thank you appreciate the info. Will reach out if I need!
are you still working on this issue. I would like to work on this issue as my first contribution.
since yesterday? We're OK with people offering to step in, but: this is typically after weeks of not hearing from someone, not hours. Anyone is welcome to work on this issue and we do have a “no cookie licking” policy to support that. However the best way to make a new contribution would be to look for a different issue. I think a PR to work on would be useful.
Another issue to consider working on (for anyone who's looking for a Good First Issue):
I thank you for the information you provided. I was unaware of that because I am new to open source. I would look for other issues to work on as my first contribution.
Hi Yes, I am still working on this :) Please bare with me folks, will hopefully get this done by mid next week latest but will update here on progress. Thank you!
Hi Team, I have created the PR with solution. Feel free to review and merge :)
Fixed as part of /close
Closing this issue. <detailsIn response to : Fixed as part of Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted


This is a Bug Report The link provided for [Node Lease objects] is wrong <!--Required Information--Problem: The provided link is navigating to top of the page not to corresponding sub section. Proposed Solution: URL link should be Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/assign
/triage accepted


This is a Bug Report The glossary tooltip for is referencing section, instead it should reference to page.
/sig docs /language en
/assign
fixed
/retitle Incorrect glossary tooltip link for 'Container runtime interface' /priority backlog /triage accepted


Hi, In k8s v1.30 documentation page , in the top FEATURE STATE line, the indicated Kubernetes version where this feature reached "stable/GA" is said to be 1.30; if you check which it is in k8s v1.29 doc page: it says 1.29 .... for 1.28 doc it says GA/stable was reached in 1.28 ... and so for the previous releases ... It looks there is a wrong moving version for this, pointing to the current one "owning" the doc page. According to it should say: FEATURE STATE: Kubernetes v1.14 [stable]
Page reported in issue: /language en /kind bug
We should correct this discrepancy in the feature state. /priority backlog /triage accepted
I try to help with this. /assign


Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Note that this issue is for Japanese Speaker Original: /language ja /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
/assign
san, can you please review the PR


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
thank you!! /triage accepted


This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The annotation is unregistered, but used in Kubernetes code. The says: However, we don't have a mechanism to register annotations that are not also documented. So, it needs registering. Proposed Solution: Register the annotation, by mentioning it in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node Required for
/assign
/priority backlog /triage accepted
/lifecycle frozen
/assign
/unassign Unassigning my self as PR is already raised by PR raised for this issue


This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --In the document , it would be helpful to link to the . Why is this needed I was studying for the CKA exam, and was practicing only using the pages to search for info about CertificateSigningRequests. The doc came up readily, but the was not so easily discoverable via a search using only the search interface. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted


There's million users which have no direct internet access from the workplace other than downloading from HTTP/HTTPS websites for security reasons. Others do not have chocolatey installed or cannot copy/paste curl commands from an external website to their local workstation, also for security reasons. Currently the HTTP link to download kubectl is inside a curl command. It could be possible to provide a more explicit HTML link, for clarity.
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
We could have the kubectl install pages link to Historically, we had this guide to installing kubectl before existed. Now that is a thing, we can link to it. would that suit you? /retitle Task page for installing kubectl should explain how to find direct download link /kind feature /language en
This was originally filed about
I did read that page and I can see that there's already a direct download link for This is under a slightly misleading heading; the text is headed: so maybe we'd like to change the heading as well? I still recommend linking to the list of binaries you can download. The existing link does assume amd64 architecture; on the other hand, AMD processors (and Intel clones) are the market leader. /priority awaiting-more-evidence
Thank you yes the misleading text is probably the main problem - but the list of binaries can also be very useful as the organizations who prevent direct internet access are often the ones who don't run the latest version of any tool :) The idea is to make it as clearer as possible as it's gonna be the first option for many as opposite to run curs or package managers which aren't so common on Windows.
OK, so: which fix do you advocate ? We should recommend one so that someone picking up this work knows what approach to take.
Hey I'd like to work on this. Based on the discussion, here are my suggestions: Let's update the header title to specify a direct download or curl option. We should add new paragraphs describing a direct download option for all supported architectures. /assign


The CNCF on cloud native security defines security controls and practices that are appropriate to different lifecycle phases 404 link
/language en
/assign
/retitle Broken link to CNCF white paper in "Cloud Native Security" page /kind bug Page reported in issue (based on initial title):
/priority backlog /triage accepted


The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.