Skip to content
API Reference

Before Installing Redbelt

Version: unreleased · Docs: 3c6ab9f2Download Markdown

Self-hosted Redbelt runs on infrastructure your organization controls. Reading these public instructions does not enroll a deployment or authorize an installer download.

Use the signed customer release and instructions supplied for your deployment. A local build or successful lab installation does not establish that a customer release has been certified or made available. If Redbelt has not supplied an authorized installer and deployment configuration, request them before proceeding; do not substitute the repository’s developer scripts.

The current customer-linux-starter profile targets Ubuntu 24.04 on amd64, with KVM available for sandbox isolation. A VM needs working nested virtualization. The profile minimums are 16 vCPUs, 32 GiB RAM and 500 GiB storage. These are configuration minimums, not a guarantee of capacity for every workload. Leave headroom for backups, upgrades, temporary files and concurrent sandbox work. A cloud VM running this Linux profile does not imply a separate cloud installer.

Ask your deployment administrator for the authorized operator executable, its independently trusted verification instructions, a private customer configuration, and a time-limited installation key. The configuration identifies your deployment, release channel, trusted signing public keys, intended administrator, application HTTPS origin and infrastructure target. Do not guess identifiers, trust keys or credentials.

Arrange DNS and TLS for the application origin, storage and an independently recoverable backup destination. The administrator must confirm the intended Kubernetes target and secret custody. Permit the required outbound access to Redbelt’s control plane, identity provider and selected model/integration providers. Restricted networking needs an explicit supported configuration; self-hosting does not mean the product operates without those dependencies.

  1. Verify the operator artifact using the trusted checksum/signature instructions supplied with that exact release.
  2. Store the customer configuration privately. Keep installation keys out of command arguments, URLs, source files and screenshots.
  3. Review the target host, available resources, DNS, TLS, backup custody and planned maintenance window with the administrator.
  4. Read installation and first use and recovery before running a command that changes the host.

For an already resolved installation specification, redbeltctl preflight --spec /etc/redbelt/install.yaml reports prerequisite checks. A failed check blocks installation. Preflight does not certify a release or prove first sign-in will succeed.