CVEs with a blast radius
A CVE page lists the images, deployments and clusters it touches, with EPSS and fix advice, so the question is “which workloads” rather than “how many CVEs”.
PrioritizationCONSTELLATION / KUBERNETES SECURITY EARLY ALPHA
Constellation is a Kubernetes-native security platform. See what is running, know what is exposed, control what is allowed and prove what happened, from one console installed in your own clusters.
Constellation is in early alpha and not production-ready. Interfaces can change without notice. We are looking for teams who will evaluate it in a lab and tell us what they find. Screens are from an AlphaBravo test environment.
Clusters, workloads, images, nodes and platform components, discovered continuously and linked together.
INVENTORY · DISCOVERY · HEALTH02 / KNOWImage, workload, node and repository scans, ranked by severity, exploit likelihood and exposure.
CVE · KEV · EPSS · SBOM03 / CONTROLAdmission rules before deployment, runtime baselines and network policy after it.
ADMISSION · RUNTIME · NETWORK04 / PROVEFramework-mapped checks, exemptions with expiry, and an audit log you can verify.
EVIDENCE · AUDIT · ACCESSFROM IMAGE TO EVIDENCE
Select a stage. Each shows the console screen and the specifics behind it, including what is on by default and what you have to turn on.
Start from what is actually deployed. The discoverer records each cluster’s workloads, images, nodes and platform, and the dashboard rolls them up into a risk score and the counts that need action.


Scanner workers inventory images with Syft and match them with Trivy and Grype. Nodes, the Kubernetes platform, repositories and AWS Lambda functions are scanned too.


Findings are ranked by a risk score that combines CVSS, the EPSS exploit probability, the CISA Known Exploited list and exposure. Accepting a risk needs a reason and an expiry.


A validating webhook checks pods and the controllers that create them. Privileged, host-network and host-PID workloads are rejected by default. Simulate a manifest before you deploy it.
An agent on every node sees process execs and file access with eBPF and inspects pod traffic. Each workload learns a baseline; drift raises an alert, and blocking is opt-in per workload.


Live cluster objects are checked every 6 hours and mapped to framework controls. Exemptions carry a reason and an expiry, and every change lands in a hash-chained audit log you can verify.


IN PRACTICE
Security, platform and audit teams look at the same findings, the same policies and the same record.
A CVE page lists the images, deployments and clusters it touches, with EPSS and fix advice, so the question is “which workloads” rather than “how many CVEs”.
PrioritizationRun a manifest or a live resource through admission rules without changing anything. Keep rules in monitor mode until the warnings are what you expect.
SimulationEach workload learns its normal processes. Freeze the baseline to alert on drift, then enforce it for the workloads that are ready.
BaselinesCandidate network policies come from the flows Constellation saw. Approve, apply, demote and roll back, with every step audited.
Policy lifecycleAccepting a risk or exempting a control needs a reason and an end date, and leaves a record in a hash-chained audit log.
ExemptionsScanners run from pre-loaded databases or internal mirrors, and the KEV and EPSS feeds can point at your own copies.
Offline scanningWORKS WITH ASTRONOMER
Constellation is a curated application in Astronomer’s catalog. Install it on the clusters Astronomer manages through its GitOps path, with admission policies that stay strict for tenant namespaces.
Constellation + Astronomer

STRAIGHT ANSWERS
No. It is in early alpha: APIs and data formats can change without notice, and there are no stability, security or support guarantees. Evaluate it on non-production clusters and tell us what you find. #
In your own Kubernetes cluster, installed with a Helm chart. It needs Kubernetes 1.27 or later and stores its data in PostgreSQL, bundled or your own. A Docker Compose demo is available for a first look at the console. #
The runtime agent only detects and alerts by default, and no network policy is applied until someone approves it. The admission webhook does reject privileged, host-network and host-PID pods by default outside its own namespace, so exempt the system namespaces you trust first. It fails open if it is unavailable. #
No. Constellation maps its checks to framework controls and keeps the evidence and audit trail. A mapped check supports a control; it does not certify a cluster. #
No. Constellation runs on its own. If you already use Astronomer, you can install Constellation from its catalog. #
NEXT STEP
Tell AlphaBravo what you run today. We will show you the workflows that matter to your team.