Update perfectscale-autoscaler chart with new package version v1.0.10

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

@@ -0,0 +1,63 @@
+apiVersion: perfectscale.io/v1
+kind: ClusterAutomationConfig
+metadata:
+  name: cluster-automation-config
+spec:
+  automation:
+    operational:
+      stopAllAutomation: false
+    workloadTypes:
+      Deployment:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                keepLimit: false
+            memoryManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: true
+                decreaseEnabled: true
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                keepLimit: false
+            memoryManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: true
+                decreaseEnabled: true
+      #  You should consider if you want to enable StatefulSets automation.
+      #  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+      #  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+      StatefulSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                keepLimit: false
+            memoryManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: true
+                decreaseEnabled: true

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

@@ -23,4 +23,4 @@ spec:
                 decreaseEnabled: true
               limit:
                 increaseEnabled: true
-                decreaseEnabled: true
+                decreaseEnabled: true

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

@@ -0,0 +1,63 @@
+apiVersion: perfectscale.io/v1
+kind: ClusterAutomationConfig
+metadata:
+  name: cluster-automation-config
+spec:
+  automation:
+    operational:
+      stopAllAutomation: false
+    workloadTypes:
+      Deployment:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false
+      #  You should consider if you want to enable StatefulSets automation.
+      #  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+      #  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+      StatefulSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false

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

@@ -23,4 +23,21 @@ spec:
                 decreaseEnabled: true
               limit:
                 increaseEnabled: false
-                decreaseEnabled: false
+                decreaseEnabled: false
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false

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

@@ -0,0 +1,33 @@
+apiVersion: perfectscale.io/v1
+kind: ClusterAutomationConfig
+metadata:
+  name: cluster-automation-config
+spec:
+  automation:
+    operational:
+      stopAllAutomation: false
+      workloadLabelSelectors:
+        # This means that if the workload has perfectscale.io/automation-disabled:true label,
+        # it will not be automated, regardless of the other labels.
+        - allowAutomation: false
+          key: perfectscale.io/automation-disabled
+          value: "true"
+        # This means that if the workload has team:dev label,
+        # it will be automated, unless it has perfectscale.io/automation-disabled:true label.
+        # Workloads without this labels will not be automated.
+        - allowAutomation: true
+          key: team
+          value: "dev"
+    workloadTypes:
+      Deployment:
+        operational:
+          automationMode: "Enabled"
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+      #  You should consider if you want to enable StatefulSets automation.
+      #  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+      #  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+      StatefulSet:
+        operational:
+          automationMode: "Enabled"

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

@@ -0,0 +1,44 @@
+apiVersion: perfectscale.io/v1
+kind: NamespaceAutomationConfig
+metadata:
+  name: your-namespace-automation-config
+spec:
+  automation:
+    workloadTypes:
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                keepLimit: false
+            memoryManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: true
+                decreaseEnabled: true
+      #  You should consider if you want to enable StatefulSets automation.
+      #  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+      #  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+      StatefulSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                keepLimit: false
+            memoryManagement:
+              request:
+                increaseEnabled: true
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: true
+                decreaseEnabled: true

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

@@ -0,0 +1,44 @@
+apiVersion: perfectscale.io/v1
+kind: NamespaceAutomationConfig
+metadata:
+  name: your-namespace-automation-config
+spec:
+  automation:
+    workloadTypes:
+      DaemonSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false
+      #  You should consider if you want to enable StatefulSets automation.
+      #  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+      #  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+      StatefulSet:
+        operational:
+          automationMode: "Enabled"
+          restrictions:
+            cpuManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                keepLimit: true
+            memoryManagement:
+              request:
+                increaseEnabled: false
+                decreaseEnabled: true
+              limit:
+                increaseEnabled: false
+                decreaseEnabled: false

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

@@ -0,0 +1,25 @@
+apiVersion: perfectscale.io/v1
+kind: WorkloadAutomationConfig
+metadata:
+  name: your-workload-automation-config
+spec:
+  targetRef:
+    kind: DaemonSet
+    name: ds-name
+  automation:
+    operational:
+      automationMode: "Enabled"
+      restrictions:
+        cpuManagement:
+          request:
+            increaseEnabled: true
+            decreaseEnabled: true
+          limit:
+            keepLimit: false
+        memoryManagement:
+          request:
+            increaseEnabled: true
+            decreaseEnabled: true
+          limit:
+            increaseEnabled: true
+            decreaseEnabled: true

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

@@ -0,0 +1,25 @@
+apiVersion: perfectscale.io/v1
+kind: WorkloadAutomationConfig
+metadata:
+  name: your-workload-automation-config
+spec:
+  targetRef:
+    kind: DaemonSet
+    name: ds-name
+  automation:
+    operational:
+      automationMode: "Enabled"
+      restrictions:
+        cpuManagement:
+          request:
+            increaseEnabled: false
+            decreaseEnabled: true
+          limit:
+            keepLimit: true
+        memoryManagement:
+          request:
+            increaseEnabled: false
+            decreaseEnabled: true
+          limit:
+            increaseEnabled: false
+            decreaseEnabled: false

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

@@ -0,0 +1,28 @@
+#  You should consider if you want to enable StatefulSets automation.
+#  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+#  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+apiVersion: perfectscale.io/v1
+kind: WorkloadAutomationConfig
+metadata:
+  name: your-workload-automation-config
+spec:
+  targetRef:
+    kind: StatefulSet
+    name: sts-name
+  automation:
+    operational:
+      automationMode: "Enabled"
+      restrictions:
+        cpuManagement:
+          request:
+            increaseEnabled: true
+            decreaseEnabled: true
+          limit:
+            keepLimit: false
+        memoryManagement:
+          request:
+            increaseEnabled: true
+            decreaseEnabled: true
+          limit:
+            increaseEnabled: true
+            decreaseEnabled: true

charts/psc-autoscaler/examples/workload-config-sts-savings.yaml

@@ -0,0 +1,28 @@
+#  You should consider if you want to enable StatefulSets automation.
+#  You might want a human eye while restarting production databases, in general, pods with persistent volume are more fragile.
+#  As well, if your StatefulSet runs on dedicated nodes, reducing workload resources will not help to reduce the cost
+apiVersion: perfectscale.io/v1
+kind: WorkloadAutomationConfig
+metadata:
+  name: your-workload-automation-config
+spec:
+  targetRef:
+    kind: StatefulSet
+    name: sts-name
+  automation:
+    operational:
+      automationMode: "Enabled"
+      restrictions:
+        cpuManagement:
+          request:
+            increaseEnabled: false
+            decreaseEnabled: true
+          limit:
+            keepLimit: true
+        memoryManagement:
+          request:
+            increaseEnabled: false
+            decreaseEnabled: true
+          limit:
+            increaseEnabled: false
+            decreaseEnabled: false