Simplified and Cost-Efficient GKE Node Management with NAP:
Secure your spot!
LogoLogo
PerfectScale.ioStart for FreeYour Account
  • Kubernetes Optimization
  • Getting started
    • How to onboard a cluster
    • Onboarding clusters programmatically
    • Onboarding with ArgoCD
    • Updating PerfectScale Agent resources
    • Re-onboarding a cluster
  • Enable automation
    • Automation setup instruction
    • Including a cluster, namespace or workload to the Automation
      • Configuring Automation for a cluster
      • Configuring Automation for a namespace
      • Configuring Automation for a workload
    • Excluding a namespace or workload from the Automation
    • Automation customization
    • Verifying Automation status
    • Exploring Automation KPIs
    • Self-healing mechanism for unschedulable pods
    • Disable automation
    • Troubleshooting
    • Automation with GitOps
  • Cloud billing integration
    • Connecting AWS CUR
    • Connecting Azure Cost Management
  • Clusters' metrics overview
  • Podfit | vertical pod right-sizing
    • Understanding 'At Risk' indicators
    • LimitRange and ResourceQuota
  • Infrafit | node right-sizing
  • Configure alerts
    • Alerts acknowledgement
  • Trends monitoring
  • Revisions history log
  • Product overview
    • How to monitor PerfectScale Agent
    • PerfectScale data collected
    • PerfectScale Autoscaler Objects' Events
    • Outbound Request Ports used by the Exporter and Autoscaler
    • PerfectScale Weekly Report
    • Product architecture
  • Customizations
    • Alerting
      • Resiliency alerts
      • Financial alerts
    • Pricing
      • Custom Pricing configuration
      • AWS CUR configuration
      • Azure Cost Management configuration
    • Ticketing & Bug Tracking
    • Communication & Messaging
      • Slack Integration
        • How to configure slack_token
        • How to configure routings
      • MS Teams Integration
        • How to configure teams_webhook
      • Datadog Alerts Integration
    • Label customizations
    • Grouping
    • Observability
    • Podfit labels
    • Optimization Policy customization
  • Administration
    • Cluster settings
    • User management
    • Roles and permissions
    • Subscription details
    • Help Center
  • PerfectScale trial
    • How to find your allocated vCPU?
  • PerfectScale Prometheus Exporter
  • Security
    • MFA
    • SSO
    • ps-agent RBAC Permissions
    • psc-autoscaler RBAC Permissions
    • ps-exporter via Proxy Configuration
  • Public API
  • Help PerfectScale to improve
  • Go to your account
Powered by GitBook
LogoLogo

© PerfectScale 2025

On this page
  1. Enable automation

Verifying Automation status

Verify the status of Automation to ensure it is running properly

PreviousAutomation customizationNextExploring Automation KPIs

Last updated 4 months ago

Visit the screen to verify the Automation status of each cluster. This section provides a dedicated column that displays the cluster's Automation status and the number of automated workloads. For more detailed information on specific workloads, navigate to , where you can check the Automation status of individual workload(s).

Overview
Status
I
Description

Active

Once the configuration is completed, automation will be indicated as successfully enabled.

Limited by Rule

When one or more resources have reached your configured size constraint in CRD, the recommendations can't be executed. The indicator will also be displayed in the . Learn more about resource allocation constraints .

Delayed

If the defined CRD causes time constraints, the execution of recommendations will be postponed.

Disabled

The merged CRD will disable automation for the workload. For example, if the cluster-level configuration enables automation while the namespace-level configuration disables it, the namespace-level configuration takes precedence, resulting in disabled automation for the particular workloads within the cluster.

Stopped

PerfectScale will forcibly stop the automation. For example, to prevent your environment from recursive resource increases, such as those resulting from memory leaks.

here
Zoom-in recommendation panel
Podfit
maintenance window