Java service for Kubernetes on Wodby
Build and run Java applications on Kubernetes with Wodby.
This repository defines the Wodby service manifests and operational
configuration for Java.
Start with a boilerplate
Use one of the boilerplates exposed by this service to start with compatible
build configuration and Wodby CI:
The Spring Boot service, based on this service, exposes the
Spring Boot boilerplate.
Services based on this service
Wodby stacks using this service
Service overview
| Property |
Manifest configuration |
| Service name |
java |
| Type |
Application service |
| Versions |
25 by default, 21 |
| Workloads |
main (Deployment), primary; scalable |
| Containers |
java using wodby/java, build target |
| Endpoints |
java: HTTP 8080 (main) |
| Service links |
DBMS (db), optional, Mail Transfer Agent (sendmail), optional, Redis, optional |
| Application build |
Git source connection enabled; Dockerfile: Dockerfile; boilerplates: Java boilerplate |
| Helm |
chart oci://registry-1.docker.io/wodby/java; version 0.1.0 |
| Configuration |
1 integration slots |
Use this service
Use this service in a custom Wodby stack by referencing java, or use the
Java application stack.
A service is a reusable component and does not deploy by itself. The stack
defines its links, settings, versions, resources, and relationship to the rest
of the application.
Maintain a custom version
- Fork this repository.
- Edit the service manifest and referenced files.
- Import the repository as a Git-backed service.
- Reference the service from a stack manifest.
Keep service, workload, container, endpoint, link, volume, config, and
derivative names stable unless dependent stacks and app-level overrides are
updated at the same time.
Validate the manifests with:
wodby service validate-manifest service.yml --org <org-id>
See the service manifest reference and the managed services index.
Development workspaces
workspace-java prepare downloads the project's dependencies with Maven or the Gradle wrapper.
workspace-java start builds the checkout and runs its jar, then builds again and restarts the
application whenever a file in the checkout changes. A failed build keeps the previous build
running. WORKSPACE_JAVA_WATCH=0 turns watching off and WORKSPACE_JAVA_COMMAND overrides startup.
Dependencies, build tools and the running jar are kept in .wodby-workspace/ in the checkout;
target/, build/ and .gradle/ are excluded from Git status through .git/info/exclude.
Requires a runtime image declaring workspace contract version 1. Ordinary and development option tags must use matching revisions.