Skip to content

Core Playbooks

Scenarios: 25

CORE

Apply Dry Run Server

Preview the preferred `core` installation path without changing the host.

cd productive-k3s-core
bash ./productive-k3s-core.sh apply --dry-run --mode server
CORE

Apply Dry Run Single Node

Preview the legacy all-in-one `single-node` path to understand how it differs from the preferred `server` mode.

cd productive-k3s-core
bash ./productive-k3s-core.sh apply --dry-run --mode single-node
CORE

Apply Server

Run the preferred core-only installation on a supported host.

cd productive-k3s-core
bash ./productive-k3s-core.sh apply --mode server
CORE

Backup Local Cluster

Capture a support-oriented backup snapshot of host and cluster state after bootstrap.

cd productive-k3s-core
bash ./productive-k3s-core.sh backup /tmp/pk3s-core-backup-01
CORE

Bundle Info And BOM

Inspect what the `core` CLI bundle is, which runtime files it carries, and which component versions it pins.

bash ./productive-k3s-core.sh bundle info --json
bash ./productive-k3s-core.sh bom --json
CORE

Exported Installer K3sup Ubuntu24

Validate the self-contained exported base installer on Ubuntu 24.04 with `PRODUCTIVE_K3S_ENGINE=k3sup`.

cd productive-k3s-core
make -C ./tests test-exported-stack-installer-k3sup-ubuntu24
CORE

Exported Installer RKE2 Ubuntu24

Validate the self-contained exported base installer on Ubuntu 24.04 with `PRODUCTIVE_K3S_DISTRO=rke2`.

cd productive-k3s-core
make -C ./tests test-exported-stack-installer-rke2-ubuntu24
CORE

Preflight Basic

Run the standard host compatibility check from a local `productive-k3s-core` checkout before attempting any installation.

cd productive-k3s-core
bash ./productive-k3s-core.sh preflight
CORE

Preflight Strict JSON

Run host preflight in a CI- or automation-friendly mode where warnings also fail the run and output is machine-readable.

cd productive-k3s-core
bash ./productive-k3s-core.sh preflight --strict --json-output
CORE

RKE2 Core Ubuntu24

Run the dedicated Ubuntu 24.04 VM profile that bootstraps `productive-k3s-core` with `PRODUCTIVE_K3S_DISTRO=rke2`.

cd productive-k3s-core
make -C ./tests test-rke2-core
CORE

RKE2 Full Ubuntu24

Run the dedicated Ubuntu 24.04 full VM profile for `PRODUCTIVE_K3S_DISTRO=rke2`.

cd productive-k3s-core
make -C ./tests test-rke2-full
CORE

Stack Base Backup

Capture a backup while enabling stack-aware addon hooks through `PRODUCTIVE_K3S_STACK_NAME=base`.

cd productive-k3s-core
PRODUCTIVE_K3S_STACK_NAME=base ./productive-k3s-core.sh backup '/tmp/pk3s-base-stack-backup'
CORE

Stack Base Cleanup Apply

Apply the destructive cleanup path for `base`.

bash ./productive-k3s-core.sh stack cleanup base --apply --yes --confirm-clean
CORE

Stack Base Cleanup Plan

Review the destructive cleanup scope for `base` without applying it.

bash ./productive-k3s-core.sh stack cleanup base --plan
CORE

Stack Base Longhorn And Rancher Checks

Run the typical Longhorn and Rancher post-install checks for the `base` stack.

bash ./utils/inspect-longhorn.sh
bash ./utils/inspect-longhorn-volumes.sh
bash ./utils/inspect-rancher.sh
bash -lc sudo\ k3s\ kubectl\ get\ pods\ -n\ longhorn-system\ -o\ wide
bash -lc sudo\ k3s\ kubectl\ get\ pods\ -n\ cattle-system\ -o\ wide
bash -lc sudo\ k3s\ kubectl\ rollout\ status\ deploy/rancher\ -n\ cattle-system\ --timeout=60s
CORE

Stack Base Registry Checks

Validate registry behavior after `base` is installed.

bash ./productive-k3s-core.sh validate --strict --docker-registry-test
bash -lc curl\ -kI\ https://registry.home.arpa/v2/
bash -lc curl\ -k\ https://registry.home.arpa/v2/_catalog\ \|\ jq
bash ./utils/list-registry-images.sh --json
CORE

Stack Export Base

Export a packaged stack artifact into a self-contained installer bundle.

cd productive-k3s-core
bash ./productive-k3s-core.sh stack export --tgz /tmp/base-stack.tgz --output /tmp/base-installer
CORE

Stack Install Base

Install the default `base` stack on top of a cluster already created with `apply --mode server`.

cd productive-k3s-core
bash ./productive-k3s-core.sh stack install base
CORE

Stack Validate After Install

Re-run stack-aware validation after `stack install base`.

cd productive-k3s-core
bash ./productive-k3s-core.sh stack validate base --strict
CORE

Stack Validate Base

Validate the explicit `base` stack before or after installation.

cd productive-k3s-core
bash ./productive-k3s-core.sh stack validate base --strict
CORE

Validate Local Cluster

Run the standard post-apply validator against the local cluster.

cd productive-k3s-core
bash ./productive-k3s-core.sh validate --strict