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.
| Severity | Description |
|---|---|
| Critical | Indicates a severe issue that requires immediate attention and may significantly impact cluster operations. |
| Error | Signifies a problem that is causing a malfunction or preventing expected behavior. |
| Warning | Alerts about potential issues or situations that could lead to problems if not addressed. |
| Info | Provides general information about cluster operations, updates, or status changes. |
| Success | Confirms that an operation or process has completed successfully. |
Notifications
General CAST AI and Kubernetes Notifications
| Severity | Notification | Further details and suggested action points |
|---|---|---|
| Critical | Failed to reconcile the cluster | This can happen, for example, when a CAST AI service account is modified, causing some permissions to be lost. |
| Critical | Node configuration validation failed | Node configuration invalid. Please check the details for more information about the error in the provided JSON object delivered with the notification. |
| Critical | Node deletion failed | The process of deleting nodes failed due to expired or removed credentials. Please check your credentials and try again. |
| Critical | Cluster controller not responding | CAST AI cluster-controller is not running in the cluster. |
| Critical | CAST AI agent is not able to connect to API | CAST AI agent is not able to send data to API. Please check the status of agent pods and trigger reconciliation. |
| Warning | Outdated cluster controller | The auto-update for cluster-controller failed. Check the documentation for information on how to upgrade it manually. |
| Warning | Spot quota exceeded | Spot instance quota exceeded. Falling back to on-demand instances. |
| Warning | Cannot find valid instance types for the given workloads | Autoscaler failed to find matching nodes for your deployments. Please check the deployment manifests for potential conflicts. Contact support if the error persists. |
| Warning | Cost anomaly detected | Cost anomaly detected. Check the cluster report for more details. |
| Error | SSO Connection problem | Detected a problem with the SSO configuration. This can happen due to expired credentials. See SSO for more information. |
| Info | Daily Vulnerability Report | This message contains the list of new vulnerabilities that appeared in a cluster in the last 24 hours. |
| Info | Cluster connection status change | Informs about cluster connection status changes (e.g., connected, disconnected, not responding). |
| Success | Autoscaling policy applied | Confirms that a new or updated autoscaling policy has been successfully applied to the cluster. |
| Success | Cluster reconciled | Cluster successfully reconciled. |
Cloud Provider-Specific Notifications
| Cloud Provider | Severity | Notification | Further details and suggested action points |
|---|---|---|---|
| AWS | Error | Missing permission when adding a node to target groups | The 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. |
| Azure | Error | Missing permission when adding VMSS IP address to a backend pool | Azure 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. |
| Azure | Error | Unable to create castpoolarm. ARM VMs will not work | Unable to create castpoolarm. Please contact support or create castpoolarm manually using Azure CLI. Check the documentation for more details. |
| All | Info | New 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.
Updated about 1 month ago