Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kubex.ai/llms.txt

Use this file to discover all available pages before exploring further.

The policy settings in this group are related to optimizing auto scaling groups.

​
Minimum Scale Group Size

DescriptionThis setting defines the minimum allowed number of EC2 instances to be recommended for an ASG.
Use Case 
Values/UnitsAn integer indicating the minimum scale group size.
Dependencies 
Example 

​
- Maximum Increase

DescriptionThis setting defines the maximum allowed increase percentage for the recommended minimum group size, based on the existing minimum group size.
Use Case 
Values/UnitsPercentage of the existing minimum group size.
Dependencies 
Example 

​
- Maximum Decrease

DescriptionThis setting defines the maximum allowed decrease percentage for the recommended minimum group size, based on the existing minimum group size.
Use Case 
Values/UnitsPercentage of the existing minimum group size.
DependenciesThis setting cannot result in the group falling below the “Minimum Scale Group Size”.
Example 

​
Maximum Scale Group Size

DescriptionThis setting defines the maximum allowed number of EC2 instances to recommend for an ASG.
Use Case 
Values/UnitsAn integer indicating the maximum group size.
Dependencies 
Example 

​
- Headroom for Maximum Group Size

DescriptionThis setting defines the maximum group size increase percentage to recommend, on top of the existing maximum group size.
Use Case 
Values/UnitsPercentage of the “Maximum Scale Group Size” value.
Dependencies 
Example 

​
- Maximum Increase

DescriptionThis setting defines the maximum allowed increase percentage for the recommended maximum group size, based on the existing maximum group size.
Use Case 
Values/UnitsPercentage of the existing maximum group size.
Dependencies 
Example 

​
- Maximum Decrease

DescriptionThis setting defines the maximum allowed decrease percentage for the recommended maximum group size, based on the existing maximum group size.
Use Case 
Values/UnitsPercentage of the existing maximum group size.
Dependencies 
Example 

​
Sizing Strategy

DescriptionThis setting defines the strategy to use when sizing EC2 or VM instances, within an ASG or VM Scale Set.
For “CPU and Memory” and “CPU only” options, the settings, listed below, indicated as “Custom…” are pre-defined in the extension. You can select “Custom” and then use the settings below to change the predefined values.
Use Case 
Values/UnitsSelect “CPU and Memory”, “CPU Only”, or “Custom”.
DependenciesIf “CPU and Memory” or “CPU Only” is selected, the corresponding limits are based on the “Sizing Limit” setting below and the corresponding scoring strategy is based on the “Sizing Strategy” below.
If “Custom” is selected, then the advanced settings below, are used.
Example 

​
- Custom Sizing Input Workloads

You can overide some of these policy settings. Overrides are independent of the “Sizing Strategy” pick list; i.e. regardless of the value selected here the override, if provided will be applied when the analyses are run. See Scale Group Overrides for details of options and for configuring overrides.
DescriptionThis setting defines the workload types to use for determining the optimal instance type for an ASG or VM Scale Set. This setting is used when “Custom” is selected for “Sizing Strategy”.
Use Case 
Values/UnitsA colon-separated list of workload types.
Dependencies 
ExampleCPU_CINT2006Rate_Utilization;Raw_Mem_Utilization

​
- Custom Sizing Output Workloads

DescriptionThis setting defines the workload types to use for displaying recommendation workload charts. This setting is used when “Custom” is selected for “Sizing Strategy”.
Use Case 
Values/UnitsA colon-separated list of workload types.
Dependencies 
ExampleCPU_Util_Predicted_Day; Mem_Utilization_As_Pct

​
- Custom Sizing Backfill Workloads

[CRB-53279] When analyzing the list of ASG candidates, Kubex uses the representative memory workload: ASG parent (ECS/EKS), busiest child, ASG, and workload days policy setting. If the ASG does not have memory data , the simulation does the following:
  • The ASG sizing extension uses memory constraints when running the simulation;
  • Fall back memory that is defined through this policy setting is used;
  • The simulation accounts for memory even if memory usage data is not available for ASG
DescriptionThis setting defines the workload types to use for backfilling resource utilization metrics. This setting is used when “Custom” is selected for “Sizing Strategy”.
Use Case 
Values/UnitsA colon-separated list of workload types.
DependenciesThe specified list of workloads must be the same as those defined for the -Custom Sizing Input Workloads.
ExampleUse the Transform_CloudECS tag if available. It is published for ASGs that are children of ECS, otherwise use Mem_Cloud
Mem Utilization As Pct, !Mem Cloud

​
- Custom Sizing Backfill Parent Workloads

DescriptionThis setting defines the workload types to use for backfilling parent resource utilization metrics. This setting is used when “Custom” is selected for “Sizing Strategy”.
Use Case 
Values/UnitsA colon-separated list of workload types.
DependenciesThe specifed list of workloads must be the same as those defined for the -Custom Sizing Input Workloads.
ExampleMem Utilization As Pct, !Transform_CloudECS

​
- Custom Sizing Scoring

DescriptionThis setting defines the scoring strategy to use when sizing EC2 or VM instances, within an ASG or VM Scale Set. This setting is used when “Custom” is selected for “Sizing Strategy”.
Use Case 
Values/UnitsA colon-separated list of scoring strategies.
Dependencies 
Example 

​
- Custom Sizing Limits

DescriptionThis setting defines the scoring limit to use when sizing EC2 or VM instances, within an ASG or VM Scale Set. This setting is used when ‘Custom’ is selected for ‘Sizing Strategy’.
Use Case 
Values/UnitsA colon-separated list of scoring limits.
Dependencies 
Example70;70

​
Sizing Limit - Scoring Strategy

DescriptionThis setting defines the scoring strategy to use when sizing EC2 or VMs instances, within an ASG or VM Scale Set.
Use Case 
Values/UnitsSelect one of the following scoring strategies:
  • Average
  • Peak
  • Sustained
See Scoring Strategy Setting on page 1 for details.
DependenciesThis setting is used when either “CPU and Memory” or “CPU Only” is selected for “Sizing Strategy”
ExampleSustained

​
CPU Sizing Limit

DescriptionThis setting defines the CPU utilization limit to use when sizing EC2 or VM instances, within an ASG or VM Scale Set.
Use Case 
Values/UnitsA numeric value representing a percentage from 0 to 100.
DependenciesThis setting is used when either “CPU and Memory” or “CPU Only” is selected for “Sizing Strategy”.
Example 

​
Memory Sizing Limit

DescriptionThis setting defines the memory utilization limit to use when sizing EC2 or VM instances, within an ASG or VM Scale Set.
Use Case 
Values/UnitsA numeric value representing a percentage from 0 to 100.
DependenciesThis setting is used when “CPU and Memory” is selected for “Sizing Strategy”.
Example 

​
Worker Size Limit - Cores

DescriptionThis setting allows you to limit the increase of vCPU cores for the current size relative to recommended sizing, for ASG worker nodes. The range is typically 25 to 100%, with the higher percentages allowing a smaller increase. i.e. if set to 25%, the recommended worker node can have 4 times more vCPUs than the current worker node. A value of 100% allows no increase in vCPU allocation.

This setting is mapped as the low limit to Total CPUs and controls the maximum size of the recommended Instance type.
Use CaseFor ASG recommendations it is important to be able to control the maximum instance size in order to avoid using bigger (and more expensive) instances, even though it may appear to be optimal, large instances may introduce issues, if the ASG needs to scale up, rapidly.
Values/UnitsSize limit as a percentage. i.e. 25%
Dependencies 
Example 

​
Worker Size Limit - Memory

DescriptionThis setting allows you to limit the increase the memory for the current size relative to recommended sizing, for ASG worker nodes. The range is typically 25 to 100%, with higher percentages allowing a smaller increase. i.e. if set to 25%, the recommended worker node can have 4 times more memory than the current worker node. A value of 100% allows no increase in memory allocation.

This setting is mapped as the low limit to Total Memory and controls the maximum size of the recommended Instance type.
Use CaseFor ASG recommendations it is important to be able to control the maximum instance size in order to avoid using bigger (and more expensive) instances, even though it may appear to be optimal, large instances may introduce issues, if the ASG needs to scale up, rapidly.
Values/UnitsSize limit as a percentage. i.e. 25%
Dependencies 
Example