This chart bootstraps a scheduled-scaler controller and allows the deployment of ScheduledScaler
resources to your cluster.
For more information read scheduled-scaler overview
- Kubernetes Version: 1.7+
- Kubernetes Cluster Settings:
- "Legacy authorization": "Enabled"
$ helm install scheduled-scaler .
$ helm delete --purge scheduled-scaler
Parameter | Description | Default |
---|---|---|
image.repository |
Scheduled scaler container image | k8srestdev/scaling |
image.tag |
Scheduled scaler container image tag | 0.0.4 |
image.pullPolicy |
Scheduled scaler container image pull policy | Always |
replicaCount |
Number of scheduled-scaler replicas to create (only 1 is supported) | 1 |
sslCerts.hostPath |
TLS certs for secure connections | /etc/ssl/certs |
rbac.create |
install required RBAC service account, roles and rolebindings | true |
resources |
Resource configuration for Scheduled scaler controller pod | {} |
nodeSelector |
Node labels for Scheduled scaler controller pod assignment | {} |
tolerations |
Tolerations for Scheduled scaler controller pod assignment | [] |
affinity |
Affinity Rules for Scheduled scaler controller pod assignment | [] |
By default the chart will install the recommended RBAC roles and rolebindings.
To determine if your cluster supports this running the following:
$ kubectl api-versions | grep rbac
You also need to have the following parameter on the api server. See the following document for how to enable RBAC
--authorization-mode=RBAC
If the output contains "beta" or both "alpha" and "beta" you can may install rbac by default, if not, you may turn RBAC off as described below.
RBAC resources are enabled by default. To disable RBAC do the following:
$ helm install . --name scheduled-scaler --set rbac.create=false