Configuring Automation with CRD
Seamlessly setup Automation with flexible CR configuration.
Use a Custom Resource (CR) to configure Automation through flexible configuration. This allows you to seamlessly integrate automation into your existing workflows and manage it using standard Kubernetes practices.
Create Custom Resource (CR)
After the installation of the automation agent, it is important to create a cluster automation configuration, as this step is mandatory:
apiVersion: perfectscale.io/v1
kind: ClusterAutomationConfig
metadata:
name: cluster-automation-config
spec:
automation:
operational:
stopAllAutomation: false # Global kill switch for automation (default: false)
cleanupAllAutomation: false # Stops automation and reverts all changes, restoring original resource specifications and settingsTo help you quickly start using PerfectScale Automation and streamline the optimization process, we provide pre-built Custom Resources (CRs) focused on desired optimization goals. You can easily implement the following CRs and customize them if needed.
âš¡ Recommended adoption path
To minimize waste and achieve optimal savings, we recommend starting with a simple, cluster-level automation focused on cost reduction.
Create a YAML file with the recommended cluster-level automation configuration using the following template:
Apply the created configuration by running the following command (where cluster-automation-config.yaml - the name of your file created in the previous step):
Combining cost savings and performance improvement configuration
The following example of a Cluster-level automation configuration allows you to automate the optimization of the entire cluster, enhancing its performance while maintaining optimal costs.
Create a YAML file with the cluster-level automation configuration using the following template:
Apply the created configuration by running the following command (where cluster-automation-config.yaml - the name of your file created in the previous step):
Let's explore additional examples of automation configurations that offer more granular and flexible control over Automation:
Automation configuration defaults
Some automation configuration settings have predefined defaults. If you don’t specify a value, PerfectScale will automatically apply the default for that field. Below is the list of configurations and their default values.
stopAllAutomation
false
cleanupAllAutomation
false
automationMode
Enabled
workloadLabelSelectors
nil
wasteMaxAutomationFrequency
Deployment: 30m
Rollout: 30m
CronJob: 30m
Job: 30m
DaemonSet: 4h
StatefulSet: 24h
fixResiliencyMaxAutomationFrequency
30m
maintenanceWindowIgnoredForResiliency
false
maintenanceWindowIgnoredMinResiliencyLevel
""
maintenanceWindow
workloadMinWasteUSDPerMonth
5
cpuManagement
request:
IncreaseEnabled: false DecreaseEnabled: true MinimumCores: -1 // no limit MaximumCores: -1 //no limit limit: KeepLimit: true maxCpuRequestIncreaseIterations: Daily: 3 Weekly: 6
memoryManagement
request:
IncreaseEnabled: false DecreaseEnabled: true MinimumGiB: -1 // no limit MaximumGib: -1 //no limit limit: IncreaseEnabled: false DecreaseEnabled: false MinimumGiB: -1 // no limit MaximumGib: -1 //no limit maxMemoryIncreaseIterations: Daily: 3 Weekly: 6
Last updated
Was this helpful?