blob: 9239aa64cee39698f1aa345a6a12576eeb8955a6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
# SIG Autoscaling Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Scope
Covers development and maintenance of Kubernetes 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.
### In scope
- Autoscaling-related API objects, such as the HorizontalPodAutoscaler and
VerticalPodAutoscaler
- Autoscaling-related tools, such as the cluster autoscaler,
single-component scaling tools (e.g. pod-nanny), and
cluster-proportional scaling tools
- Ensuring API interfaces (the scale subresource) are available and usable
to enable other SIGs to write autoscalable objects, and enable people to
interact with those interfaces.
[Link to SIG section in sigs.yaml][sigs.yaml]
#### Code, Binaries and Services
- Components and utilities that take automated action to scale a component
on the cluster (e.g. the horizontal-pod-autoscaler or addon-resizer
subproject)
- Components and utilities that take automated action to scale the cluster
itself (e.g. the cluster-autoscaler subproject)
- Special parts of client-go for interacting with with the scaling
interfaces used by the HPA (e.g. the scale-client subproject)
#### Cross-cutting and Externally Facing Processes
- Reviewing implementations of the scale subresource to ensure that
autoscaling behaves properly
- Coordinating with SIG Instrumentation to ensure that metrics APIs are
suitable for autoscaling on.
- Coordinating with SIG Scheduling to make sure scheduling decisions can
interact well with the cluster autoscaler
- Coordinating with SIG Cluster Lifecycle on integration between the
cluster autoscaler and cluster API
- Coordinating with SIG Node around Kubelet requirements for vertical
scaling of pods
### Out of scope
- Testing general cluster performance at scale (this falls under the
purview of [SIG Scalability]).
- Owning metrics APIs (this falls under the purview of [SIG
Instrumentation]). SIG Autoscaling should collaborate with [SIG
Instrumentation] to ensure that metrics APIs are suitable for using in
autoscaling.
## Roles and Organization Management
This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].
### Deviations from [sig-governance]
- SIG Autoscaling does not have chairs as a separate entity from tech
leads. The tech leads have the responsibility of chairs.
### Subproject Creation
SIG Technical Leads
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L305
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[SIG Scalability]: https://github.com/kubernetes/community/blob/master/sig-scalability
[SIG Instrumentation]: https://github.com/kubernetes/community/blob/master/sig-instrumentation
|
