CAST AI provides cluster-specific savings recommendations and cost monitoring within minutes from connecting your Kubernetes cluster.
To do so, it uses a read-only agent that connects, reads, and analyzes your setup. This article describes how the CAST AI agent works, where to find it, and how to use it.
The CAST AI agent is a component that connects your Kubernetes cluster to our platform to enable automation, cost monitoring, and optimization features.
It is read-only and follows the principle of least privilege. That means its access to your data is strictly limited, and it can’t change your cluster configuration without your explicit permission.
The agent code is open-source. You can see it in CAST AI's GitHub repository. In addition, the team regularly releases updates of the agent.
You can remove the CAST AI agent and all its legacy resources anytime.
The agent needs minimal cluster access to deliver meaningful insights. Once connected, it gathers information on how much storage, memory, and CPU units your cluster needs to run efficiently.
Here are the things the agent can access:
- Main resources such as nodes, pods, and deployments required for running the Available Savings Report.
- Environment Variables: pods, deployments, stateful sets, daemon sets.
CAST AI doesn’t access any sensitive data of the user. That means that:
- It doesn’t have access to secrets, config maps, or sensitive environment variables (e.g. containing secrets).
- Before starting the analysis process, it removes environment variables considered sensitive by their name (passwords, tokens, keys, secrets).
No matter the type of resources your Kubernetes cluster stores, the agent can’t see its contents or access them.
Note: CAST AI is ISO 27001-certified and holds the SOC 2 Type II certification.
Start by connecting to the CAST AI Console via HTTPS. This process uses auth0.com as a secure authentication method and CloudFlare WAF to address TLS and DDoS.
The platform uses Identity Aware Proxy to establish a central authorization layer for all applications accessed by HTTPS. That’s why you can use an application-level access control model instead of network-level firewalls.
Finally, JWT (JSON Web Token) enables passing the identity of the authenticated users between an identity provider and CAST AI.
Note: The CAST AI Console interacts with AWS EKS API (and APIs of other cloud providers) also via HTTPS (GET, CONNECT, PUT, TRACE).
When you connect your cluster for the first time, the agent will create the following elements:
The content of the YAML file is available before the execution of the script so that you can review it easily.
Only metadata about node workload configuration from the Kubernetes scheduler during the process is sent over. Also, the agent accesses YAML files from a node configuration called Snapshots.
Once you connect your cluster to the CAST AI Console, the platform can analyze your setup and provide insights – check the Available Saving report.
If you are happy with the recommendations, you can implement them automatically. Find out more about Rebalancing.
Once you connect your cluster, you also get free access to the cost monitoring feature and container security report.
Updated 9 days ago