Operator Walkthrough

Build Your Binary, Then Deploy It

This docs route is focused on the actual product flow: use the guided wizard to generate your deployment binary, download the resulting artifact, and run that binary in the target environment.

Use the Wizard

Configure the deployment binary through the guided web flow.

The guided wizard is the source of truth for flavor, modules, target architecture, policy gates, and build output.

Download the Artifact

Pull the binary and evidence from the completed build.

Once the build completes, operators use the build detail page to fetch the binary and supporting artifacts.

Deploy the Binary

Run the downloaded executable with the matching deployment profile.

The generated binary owns the deployment step. It runs the existing bootstrap engine using the rendered profile.

Step 1: Use the Guided Wizard

Start in the browser and let the wizard define the binary you want to produce.

Choose your Kubernetes flavor

Pick the target environment and whether the deployment is connected or disconnected.

Select modules

Add the platform components you want embedded into the binary such as GitOps, identity, and monitoring.

Configure deployment settings

Set networking, storage, authentication, and resource options for the generated artifact.

Review policy gates and build

Confirm the configuration, start the build, then monitor logs and progress until the artifact is ready.

What the wizard controls

The wizard drives the generated profile and build payload. That means deployment mode, included modules, and output behavior come from the wizard selections rather than a separate manual bootstrap document.

Open the Guided Wizard

Step 2: Build and Download

After the wizard starts the job, the build monitor and build detail pages take over.

Open the completed build from the dashboard or the build monitor when the job finishes.

Review the evidence page and verify the artifact set includes the binary, SBOM, signatures, and evidence bundle you need.

Download the generated binary to the target host or transfer package using your approved process.

Open Builds

Step 3: Deploy the Downloaded Binary

Choose the bootstrap profile that matches the mode your binary was built for.

Prepare the binary

chmod +x ./<downloaded-binary>

connected

Use when the wizard produced a connected deployment without local Gitea.

sudo ./<downloaded-binary> bootstrap --profile connected

onprem

Use when the wizard included Gitea for a local on-prem GitOps setup.

sudo ./<downloaded-binary> bootstrap --profile onprem

onprem-disconnected

Use when the wizard was built in disconnected mode for air-gapped deployment.

sudo ./<downloaded-binary> bootstrap --profile onprem-disconnected

What the binary does at runtime

It extracts embedded resources and artifacts into temporary directories.

It runs the bootstrap engine with the rendered profile and included artifacts.

In disconnected mode, it can carry the resources needed for air-gapped deployment.

Deployment Notes

The docs route now follows the product journey instead of explaining how to stand up StrataDeploy itself.

Use the guided wizard to define the artifact. Use the completed build page to retrieve the binary and evidence. Use the generated binary to perform the actual deployment.

For disconnected environments, transfer the downloaded binary into the target environment first, then run it there with the disconnected bootstrap profile.

The next expansion from here would be adding module-specific pages under `/docs/modules/*`, which matches the documentation paths already defined in the module catalog.