Availability Tiers

Available?

This feature is only available for the application manifest source type image and platform-managed clusters. For non-platform-managed clusters (BYOC/BYOA), ask the administrator to configure.

The platform offers various tiers, each with its own thresholds and configurations applied to the application during deployment or runtime. These configurations include automatic resource quota management to placement strategies. They are specific to the application resource of image source type. For other source types, the application owner needs to consider these factors when creating helm charts or YAML manifests for deployment on their own cluster or registering the cluster.

Custom tiers can also be registered, but this requires contacting the platform administrator to add the custom tier for a specific organization. The standard tiers (basic/standard/premium) are global and available for all organizations. Choosing the right tier ensures reliable application performance.

Here are the details of the standard tiers:

Basic Tier

container:
    maxSize: 3
    minSize: 1
horizontalAutoScaling:
    cpuUtilizationPercentage: 80
    enabled: false
    maxReplicas: 3
    memoryUtilizationPercentage: 80
    minReplicas: 1
multiZoneDeployment: false
name: basic
placementPreference: soft
priorityLevel: low
resources:
    cpu:
        maximum: 200m
        minimum: 100m
    memory:
        maximum: 256Mi
        minimum: 128Mi
verticalAutoScaling:
    enabled: false

Standard Tier

container:
    maxSize: 3
    minSize: 3
horizontalAutoScaling:
    cpuUtilizationPercentage: 80
    enabled: false
    maxReplicas: 3
    memoryUtilizationPercentage: 80
    minReplicas: 3
multiZoneDeployment: false
name: standard
placementPreference: soft
priorityLevel: high
resources:
    cpu:
        maximum: 200m
        minimum: 100m
    memory:
        maximum: 4Gi
        minimum: 1Gi
verticalAutoScaling:
    enabled: false

Premium Tier

container:
    maxSize: 9
    minSize: 3
horizontalAutoScaling:
    cpuUtilizationPercentage: 80
    enabled: true
    maxReplicas: 9
    memoryUtilizationPercentage: 80
    minReplicas: 3
multiZoneDeployment: true
name: premium
placementPreference: hard
priorityLevel: critical
resources:
    cpu:
        maximum: "4"
        minimum: "1"
    memory:
        maximum: 8Gi
        minimum: 4Gi
verticalAutoScaling:
    enabled: false

As a developer, start with the tier of your choice and perform testing. If you need to adjust the thresholds for certain configurations, work with the platform administrator to create custom tiers as required. Keep in mind that most of the tier configurations are tied to the underlying infrastructure, so ensure that your cluster is properly configured to avoid application failures. This feature is only available if you bring your own cluster or account. For clusters managed by the platform, custom settings will be available based on the platform's capabilities.

astroctl

astroctl availability tiers

astroctl availability tiers basic -ojson