Container Images
Release 3 platform binaries (Go services and workers) are published to Docker Hub under the dendra organization.
During development, Kubernetes deployments pin images by digest in dendra-k0s.
The registry links below are the source for pulls and tags.
Web applications and documentation sites (main app, public site, docs site, RPC API docs, and similar) are hosted on Render as static or web services. They are not distributed as Docker images.
Release 3 Binaries
Section titled “Release 3 Binaries”| Image | Docker Hub | Binaries | Source repository |
|---|---|---|---|
dendra/dendra-api-services | dendra-api-services | dendra-api-server, dendra-job-scheduler | dendra-api-services |
dendra/dendra-job-workers | dendra-job-workers | dendra-backend-worker, dendra-extract-worker, dendra-load-worker | dendra-job-workers |
The API server and job scheduler share one image. Each Deployment selects the binary via container command. Worker binaries share the same job-workers image the same way.
Deployment
Section titled “Deployment”The tahoe cluster (Release 3 dev environment on Jetstream2 k0s) references these images in resources/dendra/ manifests. Digests are updated there when rolling out a new build.
For local development, each source repository documents how to build images from its docker/ directory. See the Docker section in the dendra-api-services and dendra-job-workers READMEs.