Automation customization

All restrictions are compared to the original spec values of the workload

Customize your automation with the following settings:

timeConstraints:
          wasteMaxAutomationFrequency: "30m" # Applies recommendations to decrease resources every 30 minutes
          fixResiliencyMaxAutomationFrequency: "30m" # Applies recommendations to increase resources every 30 minutes
          maintenanceWindow:
            monday:
              - "00:00-23:59"
            tuesday:
              - "00:00-23:59"
            wednesday:
              - "00:00-23:59"
            thursday:
              - "00:00-23:59"
            friday:
              - "00:00-23:59"
            saturday:
              - "00:00-23:59"
            sunday:
              - "00:00-23:59"
          maintenanceWindowIgnoredForResiliency: false # Indicates if the maintenance window constraints are ignored for resiliency
restrictions:
    workloadMinWasteUSDPerMonth: 5 # Activates automation only if monthly waste exceeds a set threshold (for example, $5)
    cpuManagement:
      request:
        increaseEnabled: true/false   # default false
        decreaseEnabled: true/false   # default true
        minimumCores: 0.5             # default unset, to override to unset, use -1
        maximumCores: 8               # default unset, to override to unset, use -1
      limit:
        keepLimit: true/false         # default true
    memoryManagement:
      request:
        increaseEnabled: true/false  # default false
        decreaseEnabled: true/false   # default true
        minimumGib: 1                  # default unset, to override to unset, use -1
        maximumGib: 16                 # default unset, to override to unset, use -1
      limit:
        increaseEnabled: true/false  # default false
        decreaseEnabled: true/false  # default false
        minimumGib: 2                  # default unset, to override to unset, use -1
        maximumGib: 31                 # default unset, to override to unset, use -1
        memoryLeakDetection:
          maxMemoryIncreaseIterations:
            daily: 4                  # default 3
            weekly: 7                 # default 7

Operational constraints

spec:
  automation:
    operational:
      timeConstraints:
        wasteMaxAutomationFrequency: "30m" # Applies recommendations to decrease resources every 30 minutes
        fixResiliencyMaxAutomationFrequency: "30m" # Applies recommendations to increase resources every 30 minutes
        maintenanceWindow:
          sunday: [00:00-23:59]
        maintenanceWindowIgnoredForResiliency: false # Indicates if the maintenance window constraints are ignored for resiliency

🗑️ wasteMaxAutomationFrequency

maxAutomationFrequency field is deprecated as of autoscaler version v1.0.16. If maxAutomationFrequency is present and wasteMaxAutomationFrequency is not specified, maxAutomationFrequency will override wasteMaxAutomationFrequency.

This optional field defines the maximum frequency at which automated actions can be executed to apply recommendations when waste is detected, and resource reduction is needed.

If no wasteMaxAutomationFrequency is specified, PerfectScale defaults to values based on the type of workload:

Deployment: "30m" Rollout: "30m" DaemonSet: "4h" StatefulSet: "24h" CronJob: "30m" Job: "30m"

🚨 fixResiliencyMaxAutomationFrequency

maxAutomationFrequency field is deprecated as of autoscaler version v1.0.16.

This optional field defines the maximum frequency at which automated actions can be executed to apply recommendations when resiliency risks are detected, and resource increase is needed.

If no fixResiliencyMaxAutomationFrequency is specified, PerfectScale defaults to values based on the type of workload:

Deployment: "30m" Rollout: "30m" DaemonSet: "4h" StatefulSet: "24h" CronJob: "30m" Job: "30m"

🕙 Maintenance window

The maintenance window defines the timeframe for PerfectScale to implement the recommendations.

The maintenance window is particularly helpful in minimizing the impact of changes on business operations and provides a structured approach to system updates and changes.

Time is indicated in UTC.

Example 1 The automation actions are scheduled daily between 00:00 and 23:59 UTC:

timeConstraints:
          maintenanceWindow:
            monday:
              - "00:00-23:59"
            tuesday:
              - "00:00-23:59"
            wednesday:
              - "00:00-23:59"
            thursday:
              - "00:00-23:59"
            friday:
              - "00:00-23:59"
            saturday:
              - "00:00-23:59"
            sunday:
              - "00:00-23:59"

Example 2 Excluding a specific day from automation maintenanceWindow.

timeConstraints:
          maintenanceWindow:
            monday:
              - "00:00-00:00"
            tuesday:
              - "00:00-00:00"
            wednesday:
              - "00:00-00:00"
            thursday:
              - "00:00-00:00"
            friday:
              - "00:00-00:00"

To exclude a specific day(s) from an automation maintenanceWindow, set the timeframe to 00:00-00:00 (e.g., Monday-Friday in the example above).

In the example above, the maintenanceWindow does not specify a timeframe for Saturday and Sunday. As a result, these days default to a 00:00-23:59 window.

🙅 maintenanceWindowIgnoredForResiliency

In some cases, you may want Automation to override the maintenance window to ensure that critical resiliency issues, such as CPU throttling or OOM occurring outside the maintenance window, are properly addressed by immediate resource increase.

maintenanceWindowIgnoredForResiliency: true

This field indicates whether the maintenance window constraints should be ignored for resiliency. When set to true, maintenance window constraints could be ignored, while false (default) means that maintenance window constraints are enforced.

💡cpuManagement: keepLimit

In general, we recommend removing CPU limits when possible. Doing so can improve the performance and efficiency of your workloads by allowing them to use available CPU resources more freely.

However, be aware that removing misconfigured CPU limits can increase memory consumption in many cases. This requires adjusting both memory requests and limits to ensure optimal performance and efficient use of resources.

We highly recommend that removing CPU limits always be combined with enabling increase allowed memory settings. This allows the system to automatically adjust memory resources to meet the increased demands, maintaining the stability and performance of your workloads.

🔄 maxMemoryIncreaseIterations

maxMemoryIncreaseIterations sets the maximum allowed number of daily and weekly memory limit increase iterations.

max_memory_increase_iterations is a mandatory field. Make sure it exists and doesn't equal to 0.

Once the number of daily or weekly memory increase iterations reaches the maximum value, to prevent potential memory leaks, PerfectScale Automation will stop recursive memory increase.

In order to notify the customer, PerfectScale will raise a relevant indicator and create an Alert.