cloudtaser-cli preflight

Reads requirements.json from a component's Codeberg release and probes the target cluster to verify each requirement is satisfied.

Requirements are classified as: - ENV-REQUIRE: hard requirements that must pass for the component to function - ENV-COMPAT: soft requirements that may degrade functionality if not met

Exit codes: 0: all ENV-REQUIRE checks pass (ENV-COMPAT warnings do not affect exit code) 1: one or more ENV-REQUIRE checks fail

The requirements.json file is automatically downloaded from the component's Codeberg release assets. Use --file to check against a local file instead.

Usage

cloudtaser-cli preflight [flags]

Examples

# Check requirements for cloudtaser-operator v0.13.1
  cloudtaser-cli preflight --component cloudtaser-operator --version v0.13.1

  # Check with a local requirements.json file
  cloudtaser-cli preflight --component cloudtaser-ebpf --version v0.9.0 --file ./requirements.json

  # Check with JSON output for automation
  cloudtaser-cli preflight --component cloudtaser-operator --version v0.13.1 --json

  # Check including vault requirements
  cloudtaser-cli preflight --component cloudtaser-wrapper --version v0.8.0 --secretstore-address https://vault.example.com:8200

Flags

Flag	Type	Default	Required	Description
--component	string	(empty)	yes	component name (e.g., cloudtaser-operator)
--file	string	(empty)	no	use local requirements.json instead of downloading from Codeberg release
--help, -h	bool	false	no	help for preflight
--json	bool	false	no	output as JSON
--kubeconfig	string	(empty)	no	path to kubeconfig file
--namespace	string	cloudtaser	no	Kubernetes namespace to check PSA level
--secretstore-address	string	(empty)	no	secret store address for vault-api/engine/auth checks (env: CLOUDTASER_SECRETSTORE_ADDRESS, VAULT_ADDR)
--timeout	duration	20m0s	no	maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)
--version	string	(empty)	yes	version tag (e.g., v0.13.1)

All commands