Skip to main content

Add-ons

An add-on is a capability AstroPulse installs and runs on your cluster: you pick it and its settings, and AstroPulse installs a version it has tested, keeps it healthy, and offers its upgrades. Each one is installed once per cluster from the cluster's Add-ons tab, and checked with a dry run first. Pick one below by what it gives you, then install it.

Add-ons: install, configure, keep healthy

In the console​

Open a cluster from the cluster list and its Add-ons tab. Installed add-ons are grouped by category, each with its Version, Health, Availability and Status. Install Add-on offers the ones the cluster can run; the steps are in Install add-ons.

Open zoom view

A cluster's Add-ons tab: installed add-ons grouped by category, with version, health and status

A cluster's Add-ons tab: installed add-ons grouped by category, with version, health and statusA cluster's Add-ons tab: installed add-ons grouped by category, with version, health and status
Add-ons at a glance, every one healthy

You should see​

Each installed add-on with its Health checks passing and its Status Deployed. Open one that isn't healthy to see which check fails and why.

Open zoom view

A cluster's Add-ons tab listing an add-on with its health check passing and its status Deployed

A cluster's Add-ons tab listing an add-on with its health check passing and its status DeployedA cluster's Add-ons tab listing an add-on with its health check passing and its status Deployed

Choose an add-on​

The add-ons are grouped by the category the catalog gives each one, as the console groups them. Gives you is the add-on's own description.

Add-onGives youNeeds
Platform
Astro AgentSecurely connects this cluster to AstroPulse. Required to manage it.Nothing: every cluster has it
Networking
IngressRoutes outside traffic to your appsAny cluster
DNS AutomationKeeps DNS records in sync with your appsA DNS zone in Route 53, Cloud DNS or Azure DNS, and access to it
GatewayExposes model endpoints securelyKubernetes 1.30 or newer, and Certificates
Security
CertificatesIssues and renews TLS certificatesKubernetes 1.33 or newer
Vulnerability ScanningFinds known vulnerabilities in running imagesA connected Astro Agent
Autoscaling
Node AutoscalingAdds and removes nodes as demand changesAmazon EKS, created or registered; not EKS Auto Mode
Workload AutoscalingScales apps on demand, down to zeroKubernetes 1.34 or newer
Observability
Cost VisibilityShows usage and cost per appA connected Astro Agent
Accelerator MetricsTracks GPU usage per appNVIDIA GPU nodes to report on
Serving
Model ServingServes AI models on your clusterKubernetes 1.32 or newer, and Certificates
Scheduling
Workload QueueingQueues jobs fairly within quotasKubernetes 1.30 or newer

Automatic HTTPS is not an add-on of its own: Ingress, DNS Automation and Certificates together give an app a public name and a trusted certificate with no manual step.

What a given cluster can install, and why one is not available there, is on the Add-on step of the console's Install Add-on and in astroctl infra k8s addons catalog <cluster>.

Where add-ons live​

An add-on belongs to the cluster, not to an application: it is listed on the cluster's Add-ons tab, not under Applications. Most run in a namespace of their own. An add-on that calls your cloud uses the cluster's own cloud identity, never a key in a manifest: Cloud access for add-ons.

Next​