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.

Sign up for GitHub

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

Jump to bottom

Update Autoscaling Docs #4493

Open
1 of 2 tasks
steveperry-53 opened this issue Jul 26, 2017 · 28 comments
Open
1 of 2 tasks

Update Autoscaling Docs #4493

steveperry-53 opened this issue Jul 26, 2017 · 28 comments
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. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. 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 •
edited by reylejano
Loading

This is a...

  • Feature Request
  • Bug Report

Study the different kinds of autoscaling in Kubernetes: Pod, Cluster, DNS Service, other? Do we have the right topics? Are they positioned correctly in the table of contents? Should topics on the different kinds of autoscaling be isolated from each other, or should the be part of a coherent set? Put all autoscaling topics into the appropriate templates: Concept, Task, or Tutorial. Edit to comply with our style guide. Check for accuracy. Here are some of the existing topics:
Horizontal Pod Autoscaling Walkthrough
Horizontal Pod Autoscaling
Autoscale the DNS Service in a Cluster
Cluster Management
@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
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@steveperry-53
Copy link
Contributor Author

/remove-lifecycle rotten
/lifecycle frozen
/reopen

@k8s-ci-robot k8s-ci-robot reopened this Mar 21, 2018
@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 Mar 21, 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 Aug 25, 2019

If anyone's picking this up, consider adding generic glossary terms to explain vertical and horizontal scaling as concepts (separate from HorizontalPodAutoscaler & VerticalPodAutoscaler).

@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Sep 10, 2019
@sftim sftim mentioned this issue Sep 27, 2019
Closed
@sftim
Copy link
Contributor

sftim commented Oct 17, 2019

Relevant PR: #17004

@sftim
Copy link
Contributor

sftim commented Feb 20, 2020

Also see #19207

@sftim
Copy link
Contributor

sftim commented Feb 20, 2020

/sig autoscaling

@k8s-ci-robot k8s-ci-robot added the sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. label Feb 20, 2020
@sftim
Copy link
Contributor

sftim commented Oct 7, 2020

/remove-label team/google
/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Oct 7, 2020
@k8s-ci-robot
Copy link
Contributor

@sftim: The label(s) /remove-label team/google cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash

In response to this:

/remove-label team/google
/triage accepted

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sftim sftim removed the team/google label Oct 7, 2020
@sftim
Copy link
Contributor

sftim commented Mar 9, 2021

Also see #26962

@sftim
Copy link
Contributor

sftim commented Aug 10, 2021

Interested on working on this? Ask in Slack (channel #sig-docs), reply here with questions, or jump in and open a PR. All of those are great ways to help.

This was referenced Nov 30, 2021
Merged
Merged
@sftim
Copy link
Contributor

sftim commented Dec 4, 2021

/kind cleanup

@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Dec 4, 2021
@sftim
Copy link
Contributor

sftim commented Jan 21, 2022

Also see #31451

@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 8, 2023
@tengqm
Copy link
Contributor

tengqm commented Feb 8, 2023

@sftim Do you think we are in good shape regarding this reorg?

@sftim
Copy link
Contributor

sftim commented Feb 8, 2023

The docs for HPA are better than in 2017, but IMO still not that reader-friendly.

@sftim
Copy link
Contributor

sftim commented Apr 13, 2023

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 13, 2023
@sftim
Copy link
Contributor

sftim commented Oct 25, 2023

#43685 has a more specific request on this.

This was referenced Nov 25, 2023
Closed
Open
@sftim sftim mentioned this issue Feb 18, 2024
Merged
@sftim
Copy link
Contributor

sftim commented Mar 25, 2024

Also see kubernetes/autoscaler#6646

@sftim
Copy link
Contributor

sftim commented Mar 25, 2024

@MaciekPytel FYI - this is the umbrella issue for documenting autoscaling better

@sftim
Copy link
Contributor

sftim commented May 6, 2024

Also see #45802

@sftim
Copy link
Contributor

sftim commented May 6, 2024

/remove-kind cleanup

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. and removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels May 6, 2024
@sftim
Copy link
Contributor

sftim commented Jul 31, 2024

Also see #47331

@sftim
Copy link
Contributor

sftim commented Nov 20, 2024

Also see #48779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Docs Longterm issues
Status: Triage Accepted
SIG Docs k/website Board
Status: No status
Milestone
No milestone
Development

No branches or pull requests
8 participants
@zacharysarah @tengqm @steveperry-53 @k8s-ci-robot @sftim @chenopis @fejta-bot @k8s-triage-robot