Java on Kubernetes, for real this time.
Brewlet lets teams ship Java applications as OCI artifacts without a Dockerfile, OS base image, or bundled JVM. A node-resident JVM runs the application inside a Kubernetes-managed sandbox, so runtime patching and resource management stay with the platform while developers ship only their applications.
At a high level, Brewlet uses a node provisioner to install the runtime, a
containerd shim to execute Java payloads, and a Kubernetes RuntimeClass to route
workloads. An operator and the JavaApplication API provide a higher-level
deployment experience.
| Location | Owns |
|---|---|
brewlet/brewlet |
Brewlet monorepo: CLI, OCI support, runtime, shim, and node provisioner |
kubernetes/ |
Operator, admission webhooks, APIs, CRDs, manifests, and Helm chart |
maven-plugin/ |
Maven build and publishing integration |
specs/ |
Architecture contracts and enhancement proposals |
integration-tests/ |
Cross-component end-to-end harness and fixture applications |
brewlet/site |
brewlet.sh, user documentation, workshop, and brand assets |
brewlet/.github |
Organization profile and shared community health files |
The implementation components share one revision and coordinated CI in the monorepo. The website and organization community files remain independently published.
