Notifications

This CAST AI feature informs you via UI or webhook about key issues affecting the cluster. It also passes other valuable information, such as the daily vulnerability report. This guide outlines the notification types and examples you may see in CAST AI with relevant action points.

Once new items are ready for your view, the bell icon in the top menu will show a mark. You'll be able to view all items in the Notifications Center.

Due to the dynamic nature of Kubernetes clusters, notifications are set to expire automatically in 24 hours.

Notification severity types

CAST AI uses several notification severity types to categorize the severity and importance of messages.

SeverityDescription
CriticalIndicates a severe issue that requires immediate attention and may significantly impact cluster operations.
ErrorSignifies a problem that is causing a malfunction or preventing expected behavior.
WarningAlerts about potential issues or situations that could lead to problems if not addressed.
InfoProvides general information about cluster operations, updates, or status changes.
SuccessConfirms that an operation or process has completed successfully.

Notifications

General CAST AI and Kubernetes Notifications

SeverityNotificationFurther details and suggested action points
CriticalFailed to reconcile the clusterThis can happen, for example, when a CAST AI service account is modified, causing some permissions to be lost.
CriticalNode configuration validation failedNode configuration invalid. Please check the details for more information about the error in the provided JSON object delivered with the notification.
CriticalNode deletion failedThe process of deleting nodes failed due to expired or removed credentials. Please check your credentials and try again.
CriticalCluster controller not respondingCAST AI cluster-controller is not running in the cluster.
CriticalCAST AI agent is not able to connect to APICAST AI agent is not able to send data to API. Please check status of agent pods and trigger reconciliation.
WarningOutdated cluster controllerThe auto-update for cluster-controller failed. Check the documentation for information on how to upgrade it manually.
WarningSpot quota exceededSpot instance quota exceeded. Falling back to on-demand instances.
WarningCannot find valid instance types for the given workloadsAutoscaler failed to find matching nodes for your deployments. Please check the deployment manifests for potential conflicts. Contact support if the error persists.
WarningCost anomaly detectedCost anomaly detected. Check cluster report for more details.
InfoDaily Vulnerability ReportThis message contains the list of new vulnerabilities that appeared in a cluster in the last 24 hours.
InfoCluster connection status changeInforms about cluster connection status changes (e.g., connected, disconnected, not responding).
SuccessAutoscaling policy appliedConfirms that a new or updated autoscaling policy has been successfully applied to the cluster.
SuccessCluster reconciledCluster successfully reconciled.

Cloud Provider-Specific Notifications

Cloud ProviderSeverityNotificationFurther details and suggested action points
AWSErrorMissing permission when adding a node to target groupsThe IAM Role used by the CAST AI system cannot add a node to one or more target groups due to missing permissions. Check and update the IAM role permissions.
AzureErrorMissing permission when adding VMSS IP address to a backend poolAzure Role used by CAST AI system is not allowed to add a VMSS IP to a backend pool due to missing permissions. Check and update the Azure role permissions.
AzureErrorUnable to create castpoolarm. ARM VMs will not workUnable to create castpoolarm. Please contact support or create castpoolarm manually using Azure CLI. Check the documentation for more details.
AllInfoNew machines available in {CSP}New machines of a given family in {CSP} are available to use in a given region.

🚧

Notice

This list is not exhaustive and may be expanded as new notification types are implemented. The actual content of notifications may vary based on the specific situation and context within your cluster.