The server: front, mta and core Deployments, Services, and the new store's seed #16

Merged
jcoffey-dev merged 2 commits from feat/server-deployments into main 2026-11-18 19:36:44 +00:00
2 Commits
Author SHA1 Message Date
jcoffey-dev 7baae02089 server.seed: set the new store up on install
ci / chart (pull_request) Successful in 46s
A pre-install Job runs the server's --seed with the seed from values or
an existing ConfigMap, before any server pod starts: the domain,
administrator, blob store, coordinator and cluster roles the groups
name. Its secrets come from seed.secretMounts, mounted only in the Job.
backoffLimit 0: a run that stopped partway must not apply part of the
seed twice. The Job brings its own config.json, since pre-install hooks
run before the chart's ConfigMap exists.
2026-11-18 11:59:24 -07:00
jcoffey-dev 2bcbf32002 The server: front, mta and core Deployments, mail and http Services
ci / chart (pull_request) Successful in 26s
Three Deployments on one data store (config.json from values, secrets
mounted from Secrets): front for client protocols and web, mta adding
outbound delivery, core running everything with exactly one replica and
a rollout that never runs two.

Pods run non-root, every capability dropped, read-only root, seccomp
RuntimeDefault. They listen on the standard mail ports through the
namespaced sysctl net.ipv4.ip_unprivileged_port_start, which Pod
Security "restricted" allows. SMTP has to stay on 25: the server's
default rules tell inbound mail from submissions by local port 25.

A mail LoadBalancer Service (front and mta, externalTrafficPolicy Local)
and an http ClusterIP Service (front and core), PodDisruptionBudgets and
spreading across nodes and zones.
2026-11-18 11:14:08 -07:00