Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Cluster Management Docs #4504

Closed
1 of 2 tasks
steveperry-53 opened this issue Jul 26, 2017 · 8 comments · Fixed by #24415
Closed
1 of 2 tasks

Update Cluster Management Docs #4504

steveperry-53 opened this issue Jul 26, 2017 · 8 comments · Fixed by #24415
Labels
language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@steveperry-53
Copy link
Contributor

steveperry-53 commented Jul 26, 2017

This is a...

  • Feature Request
  • Bug Report

Either delete or prune this topic: Cluster Management. Much of the content is specific to cloud providers and does not belong in the Kubernetes docs. It might be that the rest of the content is covered by existing Task topics, or could be covered with a couple new Task topics.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 1, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 31, 2018
@tengqm
Copy link
Contributor

tengqm commented Feb 1, 2018

/remove-lifecycle rotten
/lifecycle frozen

Do we want to completely kill the vendor specific contents or set up a quarantine saying that "these contents are vendor specific, they are here only for reference, they are supposed to be maintained by the vendor, for more precise information go vendor/k8s page" ?

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Feb 1, 2018
@steveperry-53 steveperry-53 removed this from Small Projects in Doc Writing and Editing Oct 17, 2018
@sftim
Copy link
Contributor

sftim commented Jun 3, 2019

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jun 3, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Sep 10, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

Do we want to completely kill the vendor specific contents or set up a quarantine saying that "these contents are vendor specific, they are here only for reference, they are supposed to be maintained by the vendor, for more precise information go vendor/k8s page" ?

We mainly want to remove them; see the (recently added) content guide

@sftim
Copy link
Contributor

sftim commented Jun 3, 2020

Relevant to issue #20232

@sftim
Copy link
Contributor

sftim commented Oct 7, 2020

/triage accepted
/remove-priority backlog
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants