Skip to content

Commit d3551eb

Browse files
author
github-actions
committed
Update perfectscale-autoscaler chart with new package version v1.0.10
1 parent bda0e52 commit d3551eb

15 files changed

+400
-4
lines changed

‎charts/psc-autoscaler/examples/cluster-config-cost-saving-performance-improvement-with-DS-and-STS.yaml

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: ClusterAutomationConfig
3+
metadata:
4+
name: cluster-automation-config
5+
spec:
6+
automation:
7+
operational:
8+
stopAllAutomation: false
9+
workloadTypes:
10+
Deployment:
11+
operational:
12+
automationMode: "Enabled"
13+
restrictions:
14+
cpuManagement:
15+
request:
16+
increaseEnabled: true
17+
decreaseEnabled: true
18+
limit:
19+
keepLimit: false
20+
memoryManagement:
21+
request:
22+
increaseEnabled: true
23+
decreaseEnabled: true
24+
limit:
25+
increaseEnabled: true
26+
decreaseEnabled: true
27+
DaemonSet:
28+
operational:
29+
automationMode: "Enabled"
30+
restrictions:
31+
cpuManagement:
32+
request:
33+
increaseEnabled: true
34+
decreaseEnabled: true
35+
limit:
36+
keepLimit: false
37+
memoryManagement:
38+
request:
39+
increaseEnabled: true
40+
decreaseEnabled: true
41+
limit:
42+
increaseEnabled: true
43+
decreaseEnabled: true
44+
# You should consider if you want to enable StatefulSets automation.
45+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
46+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
47+
StatefulSet:
48+
operational:
49+
automationMode: "Enabled"
50+
restrictions:
51+
cpuManagement:
52+
request:
53+
increaseEnabled: true
54+
decreaseEnabled: true
55+
limit:
56+
keepLimit: false
57+
memoryManagement:
58+
request:
59+
increaseEnabled: true
60+
decreaseEnabled: true
61+
limit:
62+
increaseEnabled: true
63+
decreaseEnabled: true

‎charts/psc-autoscaler/examples/cluster-config-cost-saving-performance-improvement.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ spec:
2323
decreaseEnabled: true
2424
limit:
2525
increaseEnabled: true
26-
decreaseEnabled: true
26+
decreaseEnabled: true

‎charts/psc-autoscaler/examples/cluster-config-cost-saving-with-DS-and-STS.yaml

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: ClusterAutomationConfig
3+
metadata:
4+
name: cluster-automation-config
5+
spec:
6+
automation:
7+
operational:
8+
stopAllAutomation: false
9+
workloadTypes:
10+
Deployment:
11+
operational:
12+
automationMode: "Enabled"
13+
restrictions:
14+
cpuManagement:
15+
request:
16+
increaseEnabled: false
17+
decreaseEnabled: true
18+
limit:
19+
keepLimit: true
20+
memoryManagement:
21+
request:
22+
increaseEnabled: false
23+
decreaseEnabled: true
24+
limit:
25+
increaseEnabled: false
26+
decreaseEnabled: false
27+
DaemonSet:
28+
operational:
29+
automationMode: "Enabled"
30+
restrictions:
31+
cpuManagement:
32+
request:
33+
increaseEnabled: false
34+
decreaseEnabled: true
35+
limit:
36+
keepLimit: true
37+
memoryManagement:
38+
request:
39+
increaseEnabled: false
40+
decreaseEnabled: true
41+
limit:
42+
increaseEnabled: false
43+
decreaseEnabled: false
44+
# You should consider if you want to enable StatefulSets automation.
45+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
46+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
47+
StatefulSet:
48+
operational:
49+
automationMode: "Enabled"
50+
restrictions:
51+
cpuManagement:
52+
request:
53+
increaseEnabled: false
54+
decreaseEnabled: true
55+
limit:
56+
keepLimit: true
57+
memoryManagement:
58+
request:
59+
increaseEnabled: false
60+
decreaseEnabled: true
61+
limit:
62+
increaseEnabled: false
63+
decreaseEnabled: false

‎charts/psc-autoscaler/examples/cluster-config-cost-saving.yaml

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,21 @@ spec:
2323
decreaseEnabled: true
2424
limit:
2525
increaseEnabled: false
26-
decreaseEnabled: false
26+
decreaseEnabled: false
27+
DaemonSet:
28+
operational:
29+
automationMode: "Enabled"
30+
restrictions:
31+
cpuManagement:
32+
request:
33+
increaseEnabled: false
34+
decreaseEnabled: true
35+
limit:
36+
keepLimit: true
37+
memoryManagement:
38+
request:
39+
increaseEnabled: false
40+
decreaseEnabled: true
41+
limit:
42+
increaseEnabled: false
43+
decreaseEnabled: false

‎charts/psc-autoscaler/examples/label-based-configuration.yaml

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: ClusterAutomationConfig
3+
metadata:
4+
name: cluster-automation-config
5+
spec:
6+
automation:
7+
operational:
8+
stopAllAutomation: false
9+
workloadLabelSelectors:
10+
# This means that if the workload has perfectscale.io/automation-disabled:true label,
11+
# it will not be automated, regardless of the other labels.
12+
- allowAutomation: false
13+
key: perfectscale.io/automation-disabled
14+
value: "true"
15+
# This means that if the workload has team:dev label,
16+
# it will be automated, unless it has perfectscale.io/automation-disabled:true label.
17+
# Workloads without this labels will not be automated.
18+
- allowAutomation: true
19+
key: team
20+
value: "dev"
21+
workloadTypes:
22+
Deployment:
23+
operational:
24+
automationMode: "Enabled"
25+
DaemonSet:
26+
operational:
27+
automationMode: "Enabled"
28+
# You should consider if you want to enable StatefulSets automation.
29+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
30+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
31+
StatefulSet:
32+
operational:
33+
automationMode: "Enabled"

‎charts/psc-autoscaler/examples/namespace-daemon-stateful-sets-resilience-and-savings.yaml

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: NamespaceAutomationConfig
3+
metadata:
4+
name: your-namespace-automation-config
5+
spec:
6+
automation:
7+
workloadTypes:
8+
DaemonSet:
9+
operational:
10+
automationMode: "Enabled"
11+
restrictions:
12+
cpuManagement:
13+
request:
14+
increaseEnabled: true
15+
decreaseEnabled: true
16+
limit:
17+
keepLimit: false
18+
memoryManagement:
19+
request:
20+
increaseEnabled: true
21+
decreaseEnabled: true
22+
limit:
23+
increaseEnabled: true
24+
decreaseEnabled: true
25+
# You should consider if you want to enable StatefulSets automation.
26+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
27+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
28+
StatefulSet:
29+
operational:
30+
automationMode: "Enabled"
31+
restrictions:
32+
cpuManagement:
33+
request:
34+
increaseEnabled: true
35+
decreaseEnabled: true
36+
limit:
37+
keepLimit: false
38+
memoryManagement:
39+
request:
40+
increaseEnabled: true
41+
decreaseEnabled: true
42+
limit:
43+
increaseEnabled: true
44+
decreaseEnabled: true

‎charts/psc-autoscaler/examples/namespace-daemon-stateful-sets-savings.yaml

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: NamespaceAutomationConfig
3+
metadata:
4+
name: your-namespace-automation-config
5+
spec:
6+
automation:
7+
workloadTypes:
8+
DaemonSet:
9+
operational:
10+
automationMode: "Enabled"
11+
restrictions:
12+
cpuManagement:
13+
request:
14+
increaseEnabled: false
15+
decreaseEnabled: true
16+
limit:
17+
keepLimit: true
18+
memoryManagement:
19+
request:
20+
increaseEnabled: false
21+
decreaseEnabled: true
22+
limit:
23+
increaseEnabled: false
24+
decreaseEnabled: false
25+
# You should consider if you want to enable StatefulSets automation.
26+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
27+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
28+
StatefulSet:
29+
operational:
30+
automationMode: "Enabled"
31+
restrictions:
32+
cpuManagement:
33+
request:
34+
increaseEnabled: false
35+
decreaseEnabled: true
36+
limit:
37+
keepLimit: true
38+
memoryManagement:
39+
request:
40+
increaseEnabled: false
41+
decreaseEnabled: true
42+
limit:
43+
increaseEnabled: false
44+
decreaseEnabled: false

‎charts/psc-autoscaler/examples/workload-config-daemon-set-resilience-and-savings.yaml

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: WorkloadAutomationConfig
3+
metadata:
4+
name: your-workload-automation-config
5+
spec:
6+
targetRef:
7+
kind: DaemonSet
8+
name: ds-name
9+
automation:
10+
operational:
11+
automationMode: "Enabled"
12+
restrictions:
13+
cpuManagement:
14+
request:
15+
increaseEnabled: true
16+
decreaseEnabled: true
17+
limit:
18+
keepLimit: false
19+
memoryManagement:
20+
request:
21+
increaseEnabled: true
22+
decreaseEnabled: true
23+
limit:
24+
increaseEnabled: true
25+
decreaseEnabled: true

‎charts/psc-autoscaler/examples/workload-config-daemon-set-savings.yaml

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
apiVersion: perfectscale.io/v1
2+
kind: WorkloadAutomationConfig
3+
metadata:
4+
name: your-workload-automation-config
5+
spec:
6+
targetRef:
7+
kind: DaemonSet
8+
name: ds-name
9+
automation:
10+
operational:
11+
automationMode: "Enabled"
12+
restrictions:
13+
cpuManagement:
14+
request:
15+
increaseEnabled: false
16+
decreaseEnabled: true
17+
limit:
18+
keepLimit: true
19+
memoryManagement:
20+
request:
21+
increaseEnabled: false
22+
decreaseEnabled: true
23+
limit:
24+
increaseEnabled: false
25+
decreaseEnabled: false

‎charts/psc-autoscaler/examples/workload-config-sts-resilience.yaml

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# You should consider if you want to enable StatefulSets automation.
2+
# You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
3+
# As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
4+
apiVersion: perfectscale.io/v1
5+
kind: WorkloadAutomationConfig
6+
metadata:
7+
name: your-workload-automation-config
8+
spec:
9+
targetRef:
10+
kind: StatefulSet
11+
name: sts-name
12+
automation:
13+
operational:
14+
automationMode: "Enabled"
15+
restrictions:
16+
cpuManagement:
17+
request:
18+
increaseEnabled: true
19+
decreaseEnabled: true
20+
limit:
21+
keepLimit: false
22+
memoryManagement:
23+
request:
24+
increaseEnabled: true
25+
decreaseEnabled: true
26+
limit:
27+
increaseEnabled: true
28+
decreaseEnabled: true

0 commit comments

Comments
 (0)