README.md

Autoscaling Special Interest Group

Covers development and maintenance of components for automated scaling in Kubernetes. This includes automated vertical and horizontal pod autoscaling, initial resource estimation, cluster-proportional system component autoscaling, and autoscaling of Kubernetes clusters themselves.

The charter defines the scope and governance of the Autoscaling Special Interest Group.

Meetings

• Regular SIG Meeting: Mondays at 14:00 UTC (biweekly/triweekly). Convert to your timezone.
  • Meeting notes and Agenda.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

• Marcin Wielgus (@mwielgus), Google

Contact

• Slack
• Mailing list
• Open Community Issues/PRs

Subprojects

The following subprojects are owned by sig-autoscaling:

• addon-resizer
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/autoscaler/master/addon-resizer/OWNERS
• cluster-autoscaler
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/autoscaler/master/OWNERS
• cluster-proportional-autoscaler
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-incubator/cluster-proportional-autoscaler/master/OWNERS
• cluster-proportional-vertical-autoscaler
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-incubator/cluster-proportional-vertical-autoscaler/master/OWNERS
• horizontal-pod-autoscaler
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/api/master/autoscaling/OWNERS
    • https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/podautoscaler/OWNERS
• scale-client
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/client-go/master/scale/OWNERS
• vertical-pod-autoscaler
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/autoscaler/master/OWNERS

GitHub Teams

The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.

Team Name	Details	Description
@kubernetes/sig-autoscaling-api-reviews	link	API Changes and Reviews
@kubernetes/sig-autoscaling-bugs	link	Bug Triage and Troubleshooting
@kubernetes/sig-autoscaling-feature-requests	link	Feature Requests
@kubernetes/sig-autoscaling-misc	link	General Discussion
@kubernetes/sig-autoscaling-pr-reviews	link	PR Reviews
@kubernetes/sig-autoscaling-proposals	link	Design Proposals
@kubernetes/sig-autoscaling-test-failures	link	Test Failures and Triage

Concerns

• autoscaling of clusters,
• horizontal and vertical autoscaling of pods,
• setting initial resources for pods,
• topics related to monitoring pods and gathering their metrics (e.g.: Heapster)

Demo and Presentation Guidelines

If you want to demo at SIG Autoscaling, we have some guidelines:

• Demos should talk about open-source projects relevant to Kubernetes autoscaling, such as:

  • Prototypes for features to be added to Kubernetes
  • Projects that fill gaps in our infrastructure that we might want to address
  • Alternative approaches to what we do now that we may want to research

• Demos and presentations should be geared towards a techincal audience.

• Demos and presentations should not talk about company history or background, except to provide context for a usecase or issue:

  • "We're a retail company, and people don't shop as much during at 3am, so we generally see patterns of traffic around times" is acceptable.

  • Giving a company elevator pitch is not acceptable.

• Non-demo presentations should focus on usecases and issues. A good rule of thumb is that content should be relevant in some form to a design doc or KEP's motivation or background sections. If it's not, it probably doesn't belong in the presentation.

• Demos and presentations should not pitch products. If you want to talk about a product that's recently been open-sourced, focus on it from the perspective of why it's useful to the community.