jiebi/CodeConvo huggingface dataset:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: has a feature-state shortcode: this shortcode doesn't track when the feature went beta. Proposed Solution: Change that line to: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /help /language en /priority backlog /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: has a feature-state shortcode: Change that line to: <!--Kubernetes Version:--/help /language en /priority backlog /good-first-issue </details
/assign
This is a clean up issue <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be changed Look at Make sure that all the version constraints in the page make sense and related to the list of Kubernetes versions that are for documentation. There is a shortcode in the page that expects a value in the page front matter. ~Replace that shortcode with English text that explains in words what versions the reader should have. (to save you having to check: you can only configure a startup probe if you have Kubernetes v1.16 or later and if you have enabled the )~ Remove that shortcode. Why is this needed doesn't clearly tell readers about the version of Kubernetes they need to be running and the feature gate(s) they might need to enable. Comments /help /kind cleanup If you're looking at this, you might also want to tackle issue
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a clean up issue <!-- See for guidance on writing an actionable issue description. --Look at (to save you having to check: you can only configure a startup probe if you have Kubernetes v1.16 or later and if you have enabled the ) doesn't clearly tell readers about the version of Kubernetes they need to be running and the feature gate(s) they might need to enable. /help /kind cleanup Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
/language en /lifecycle frozen
/assign I'll probably be back with questions - where's better to post/ask, here on the issue, or in Slack?
Should I just add the info for Startup probes?
I see that they came last with the feature gate in 1.16 onwards, checking now re: Liveness and Readiness but I guess they're earlier than the supported doc versions. Still would be nice to mention though - as a reader with maybe a bit less context I would get confused if the page title mentions 3 kinds of probes and the docs only talk about version requirements for one type of probe.
Also at this point for the feature flag since it went beta in 1.18 and GA in 1.20 the text would be something like: Kubernetes v1.16 and v1.17 require the to be set. Startup probes are enabled by default in Kubernetes v1.18 onwards.
IMO it's OK to focus on documenting for v1.21, the current documentation version. If we want to backport the equivalent change to the older documentation, that's an option too. For example, if you want to revise https://v1- to explain the feature gate, that's OK (but also not a priority).
how do I go about editing the old version of the docs? Or is there a how-to/readme somewhere? I've submitted a PR for the current version/file with the text I suggested: Do you know btw when Liveness and Readiness probes went alpha/beta/GA? I found Liveness probes introduced but haven't found Readiness probes yet. Anyways given that it's all the way in 2014 I think it's safe to omit specific versions. I updated the text to read: lmk what you think
Since I opened this issue, several Kubernetes releases have come out and I didn't update the issue text to clarify it. I have now.
If all PRs were this simple Actually it turns out some of them really are :)
Ref: The page is centered around Docker examples and needs a rewrite in light of the Dockershim removal. /triage accepted /milestone 1.24
/sig node
Hi, I would like to work on this but I may need a little help. When we say "rewrite in light of the Dockershim removal", does it just means removing the Docker references on the page ( i.e removing "" on this page) or something more is expected.
Thanks for taking this on. In my opinion, there are two issues to deal with here. The first is easy. Change "Docker image" to "container image". I believe the second instance refers to a legacy Docker feature called . I think it is safe to just remove that sentence.
Thankyou :) I'll make a PR by tomorrow /assign
Hello team. Recently I noticed that this page: shows wrong command. Instead of it should be I believe the fix should go into this file Please review. Thank you
/assign
- -- -- -- -- -- -- -Also see this:
should this issue and its corresponding PR be closed?
closed his prior PR, and opened . IMO it would be good to keep this issue open until the error in K8s Docs has been resolved. /kind bug
Okay
/triage accepted
The 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]:
Should the PR be opened in Kuberenetes/website?
/remove-lifecycle stale
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
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Currently, the documentation for starting a new localization instructs only to use the language code. However, some of the languages for which the website is currently localized also have the country code, due to Docsy specificities and because the language is written differently in the places where it is spoken. Document a general guideline of when and how a language should also contain the country code attached to it when localizing Kubernetes documentation, so new locales follow the country code standard when it makes sense to do so. Why is this needed To make sure that previous decisions made by localization teams are documented in in our page. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This is a follow-up issue to discussion on . /assign /cc
/triage accepted
I was reading this page to learn about an addon that the installation page mentions as indispensable, i.e. the CNI addon. Strangely it isn't even mentioned on the page.
/retitle Mention network plugins in “Kubernetes Components” It does make sense to mention network plugins as an example of an add-on. /triage accepted /language en /priority backlog
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
/remove-lifecycle rotten
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing 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
/reopen This is still a valid issue.
Reopened this issue. <detailsIn response to : /reopen This is still a valid 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
/lifecycle frozen
Page to be modified: What needs to be : A section about Network Plugins under Addons Where can you find more information about Network Plugins on our docs: Does that sound right? If yes, we can open this up for contributions as a good-first issue. I understand there are several other higher-priority issues, but I also think this is low-hanging fruit that can be completed easily.
/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: There is an error in the command to Install Docker CE for Ubuntu 16.04+ Proposed Solution: Update the command whicht tells to Install Docker CE for Ubuntu. The command sais: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0ubuntu-$(lsbrelease -cs) But it should be: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0~ubuntu-$(lsbrelease -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) so it should be only 1 character of ~ instead of 2 ~~ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: identified for Kubernetes Secrets should indicate that the secrets stored in YAML files must be protected. Proposed Solution: Add Risk Bullet: If a Base64 encoded secret is shared, it should be considered Compromised. For Example: Checking into source control, placing on a document share, or emailing All of these expose your secret to everyone who has access. Base64 is considered so secrets encoded as Base64 require additional controls to ensure only authorized users/systems can access them. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Add the bullet above under the following section:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
issue solved.
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Following a series of acquisitions it looks like that article is no longer published. I couldn't find a current URL for it. Proposed Solution: Update the link to point at and mention in the text that this is archived from the original. Page to Update: Additional Information: To edit via GitHub web interface: /kind bug /priority backlog /language en /triage accepted /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Update the link to point at and mention in the text that this is archived from the original. To edit via GitHub web interface: /priority backlog /language en /triage accepted /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I would like to take this one. This will be my first time contributing to repo, so I might take a while.
/assign
Fixed in /close
Closing 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
This is a Bug Report <!--Required Information--Problem: The link for under in is incorrect. It is redirecting to the instead of that it should redirect to the . As given in the , the (line 195) shows the heading is changed to from . Proposed Solution: should redirect to the instead of Page to Update:
/language en /sig docs /sig storage
I would like to work on it. /assign
/triage accepted A fixup/clarification is welcome.
/assign
The issue is fixed 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 Translate /docs/concepts/workloads/controllers/jobs-run-to-completion/ into Japanese. Why is this needed This page has not been translated. Comments /language ja
/assign
…
8/3PR
masterPR
dev-1.17-ja.3master
dev-1.17-ja.3() dev-1.17-ja.2: dev-1.17-ja.3:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: In , There are some redirection rules with wildcard(``). Expectation: Netlify redirects to Reality: gives Instead, Netlify redirects (literally) to (literally) Expectation: Netlify redirects to Reality: Netlify redirects to (with trailing slash) which is not a valid anchor URL (because of the trailing slash). Proposed Solution: File to Update:  <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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 would like to give this a try /assign
how can I test these redirect things after I made the changes? Do I have to make a PR to get the netlify link to test the things?
Are you working on this issue?
Ya I was trying but couldn't figure out how can I test these redirects after making the changes
Thanks, I will unassign myself. Please consider commenting before. It helps others to know about the progress of issue. /unassign
/assign
It was my bad.
I think the problem is with the link itself. Here may be is the splat. Maybe that's why it's unable to redirect. If I change the redirect to something like below without the .md it works fine And for this link , the splat is get/ and hence it redirects to This can be resolve if we remove the trailing slash from this link So, where are all these links present if we want to modify the link itself?
What a great research! I think so.
To do tests, you should changes on  file, a PR, and the redirection rules on the deploy preview: https://deploy-preview-xxxxx--kubernetes-io-main- And regarding your research, I suggest to make changes like these: and test on the deploy preview of the PR you will post. I did some searching and found these: content/en/blog/posts/2016-08-00-Kubernetes-Namespaces-Use-Cases- content/en/blog/posts/2016-12-00-Statefulset-Run-Scale-Stateful-Applications-In-
I have made the PR. Let me know if I have to do some more changes or anything
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: No resource or content is getting showcased under 'Helpful Resources' heading in . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--!
/sig docs /priority backlog /language en
can I work on this issue? /assign
What might we do to fix this issue? do you have an idea? (it's OK if you don't)
3 kind of solutions are coming to my mind- 'Helpful resources' heading, if it's not adding any value here. some resources that are helpful to understand more about release process. Like- can also add things like this
I think would be great fit , here we can find detailed information about the roles within the release team, processes, and other essential aspects of managing Kubernetes releases.
/triage accepted It's definitely not right to keep the section empty does sound like an approach to me.
Upon some inspection, We don't have a heading on any other page. Should we remove it for consistency?
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Translate tasks/configure-pod-container/configure-pod-configmap/ into Japanese. Why is this needed This page has not been translated. Comments /language ja
/assign
/close
Closing 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
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments
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 es /kind feature
hey i want to work for it can you plz assign this to me!!
Thanks for participating into the Kubernetes Website project. The Spanish translation team would like to facilitate your contribution's journey, so please share your goals and/or skills in order to assist you better. We also encourage new contributors to participate in their native speaking language.
/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 some outdated descriptions in Why is this needed fix missing link to /releases update events Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
This is a Bug Report Problem: The following page writes: As discussed in issue , the use of "privileged" in the phrase "create a privileged Pod" is not standard usage and causes confusion because the pod is not created with the privileged flag (as ). This means that commands such as fail with and reading some process information may fail with . Proposed Solution: As far as what the actual clarification should be instead of the word "privileged", I'm not sure. I think a subject matter expert should opine on that. My guess is it should be something along the lines of: Page to Update: FYI
/assign
/sig cli /language en /triage accepted /remove-kind bug /priority backlog
/unassign PR is an attempt to resolve this issue, but the PR has been closed and this issue is not resolved yet. Please take a look discussions and suggestions in the PR before self-assign. :)
/good-first-issue /assign
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 : /good-first-issue /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The PR for this issue has already been raised earlier.