-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathautoscaler.yaml
More file actions
65 lines (56 loc) · 1.5 KB
/
autoscaler.yaml
File metadata and controls
65 lines (56 loc) · 1.5 KB
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
---
# Metrics service to check conditions for scaling up or down the cluster
metrics:
# Prometheus integration
prometheus:
url: "http://127.0.0.1:8080"
upCondition: "placeholder"
downCondition: "placeholder"
headers: {}
# Infrastructure service to interact with the cloud provider (GCP, AWS, etc.)
infrastructure:
# GCP integration
gcp:
projectId: "placeholder"
zone: "placeholder"
migName: "placeholder"
credentials_file: "placeholder"
# Target to control when scaling down the cluster
target:
# Elasticsearch target service
elasticsearch:
url: "https://localhost:9200"
user: "${ELASTICSEARCH_USER}"
password: "${ELASTICSEARCH_PASSWORD}"
sslInsecureSkipVerify: true
shardRebalancing:
enabled: true
aliases:
- "image-v9"
maxReplicas: 5
minReplicas: 1
# Notifications service to send alerts to the team
notifications:
# Slack integration
slack:
webhookUrl: "placeholder"
# General configuration for the autoscaler
autoscaler:
debugMode: true
defaultCooldownPeriodSec: 10
scaledownCooldownPeriodSec: 10
retiryIntervalSec: 10
minSize: 1
maxSize: 2
scaleUpThreshold: 1
# For advanced custom scaling configuration, when you want a different minSize and maxSize nodes for specific moments
advancedCustomScalingConfiguration:
- days: "2,3,4"
hoursUTC: "5:00:00-8:00:00"
minSize: 1
maxSize: 2
scaleUpThreshold: 2
- days: "6,7"
minSize: 3
maxSize: 4
scaleUpThreshold: 1