System requirements
Prepare compute, operating systems, data services, storage, trust, time and target hosts before running the installer.
RC
Exact release scope. This page documents the reviewed v0.0.1 source at fcc5871. Check release status before enabling a gated capability.
Control-plane requirements
| Dependency | Minimum contract | Why |
|---|---|---|
| Linux / Kubernetes platform | A supported Compose host or existing Kubernetes platform | Runs the API, workers and optional in-cluster agent |
| PostgreSQL | External, durable and backed up | System of record for identity, settings, runs, audit and projections |
| Artifact storage | Durable filesystem or S3-compatible | Logs, command evidence, reports, bundles and integrity metadata |
| Secrets protection key | Base64-encoded 32-byte key with managed key ID | Protects persisted secret material; stored separately from backups |
| Registry | Public or private, immutable digest support | API, agent, tool, Kubernetes and add-on artifacts |
| DNS, TLS and time | Approved names, trust chain and synchronized clock | Authentication, agent negotiation, signatures and leases |
Cluster node baseline
| Area | Supported v0.0.1 baseline |
|---|---|
| Operating systems | Ubuntu 22.04 / 24.04; Debian 11 / 12; RHEL, Rocky or AlmaLinux 8 / 9; CentOS Stream 9 |
| Kernel | Linux 5.4 or newer |
| kubeadm host | Compatible glibc Linux, unique hostname/MAC/product_uuid, open required ports |
| Control-plane node | At least 2 CPU and 2 GiB RAM upstream minimum; use workload-appropriate enterprise sizing |
| Access | root or approved sudo policy, deterministic SSH host trust, no interactive-only prompts |
| Network | Full approved node connectivity, explicit pod/service CIDRs and selected Calico transport |
Installer and operator workstation
- ✓Bash and the release-declared command dependencies are present
- ✓Helm is available only when using the Helm path; use the release-supported client version
- ✓Access to the signed release bundle and approved registry/mirror exists
- ✓No secret is placed in shell history, Git, values files, command-line arguments or support bundles
- ✓The operator can reach health endpoints and the chosen backup target
Authoritative upstream prerequisites
Kubernetes kubeadm installation prerequisitesHelm installation and binary verificationThese sources explain upstream prerequisites. They do not widen ClusterPilot's release-scoped support matrix.