Run OpenSMTPD as a reusable Kubernetes application service with Wodby.
This repository defines the Wodby service manifests and operational configuration for OpenSMTPD.
- Django application stack
- Drupal application stack
- FastAPI application stack
- Flask application stack
- Go application stack
- Laravel application stack
- Matomo application stack
- Next.js application stack
- Node.js application stack
- OpenSMTPD application stack
- PHP application stack
- Python application stack
- Rails application stack
- Ruby application stack
- WordPress application stack
| Property | Manifest configuration |
|---|---|
| Service name | opensmtpd |
| Type | Application service |
| Versions | 7 by default |
| Workloads | main (StatefulSet), primary |
| Containers | opensmtpd using wodby/opensmtpd |
| Endpoints | opensmtpd: TCP 25 |
| Volumes | Spool |
| Helm | chart oci://registry-1.docker.io/wodby/opensmtpd; version 0.4.1 |
| Configuration | 1 integration slots |
Use this service through one of the Wodby application stacks listed above, or
reference opensmtpd from a custom Wodby 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.
- 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.