Brewlet workshops

Brewlet has two distinct user journeys. Choose the workshop for your role, or complete both to exercise the platform handoff end to end.

Workshop	Audience	Outcome
Part 1: Enable a cluster	Kubernetes platform and operations teams	A cluster with ready Brewlet nodes, the brewlet RuntimeClass, an approved JDK inventory, and a documented developer handoff
Part 2: Build and deploy a workload	Java application developers	A JAR published as a runnable OCI image and running on the Brewlet-enabled cluster

Recommended format

For a shared session, pair one Ops participant with one Dev participant:

1. Ops completes Part 1 and gives the Dev participant the handoff values.
2. Dev completes Part 2 without needing cluster-admin access.
3. Both participants inspect the running workload and its selected JDK.

Use a disposable cluster for the workshop. Brewlet node provisioning is privileged and changes the node's containerd configuration.

Released tools and example source

The Ops workshop installs the released chart and CLI directly. The Dev workshop uses the example application from the matching release tag:

git clone --depth 1 --branch v0.1.0 https://github.com/brewlet/brewlet.git
cd brewlet

No participant needs to build Brewlet's platform components or Maven plugin from source.

Maintainer verification

The numbered E2E tiers are the project qualification suite, not the primary student path. Maintainers can run the coordinated host-side checks with:

make check-all

Cluster-backed capabilities remain available through integration-tests/e2e/run.sh; see the integration-test runbook. The website deployment also runs scripts/verify-release-artifacts.sh to confirm that the documented CLI, Maven plugin, chart, and component images are publicly downloadable.