# Changelog All notable changes to the inbuxa chart. Chart versions follow the inbuxa suite: release candidates `27.1.0-rc.N`, then `27.1.0`. Each release says which server, webmail and console images it runs, pinned by digest. ## Unreleased ### Added - The repository: the chart's layout, a values schema that refuses unknown keys, and CI (`helm lint` under Helm 4 and 3, kubeconform against Kubernetes 1.35 to 1.37, kube-linter, helm-unittest). - The server, as three Deployments: `front` (client protocols and web), `mta` (as front, plus outbound delivery) and `core` (everything, exactly one replica). The data store is a value, written as `config.json`; its secrets are Secrets mounted under `/etc/inbuxa/secrets`. - Pods that run as a non-root user with every capability dropped, a read-only root filesystem and the RuntimeDefault seccomp profile. They listen on the standard mail ports through the namespaced sysctl `net.ipv4.ip_unprivileged_port_start`, which Pod Security "restricted" allows. - A `mail` LoadBalancer Service (front and mta, client addresses kept) and an `http` ClusterIP Service (front and core), PodDisruptionBudgets, and spreading across nodes and zones. - `server.seed`: the new store's setup (domain, administrator, blob store, coordinator, roles), applied once on install by a pre-install Job running the server's `--seed`, before any server pod starts. - `server.upgrade`: before an upgrade or rollback rolls out, a Job on the new image asks the server what it does to the store (`--upgrade-plan`). A layout change waits for `upgrade.acknowledgeLayout`. When a layout step can't run with older pods up, the server Deployments are scaled to 0 first, which a rolling update can't do. Then `--upgrade-store` upgrades the store. - `webmail` and `console`, off by default: Deployments, Services, optional autoscalers and PodDisruptionBudgets, read-only root filesystems. The webmail keeps sessions in sealed cookies, so any replica serves any request, and signs in through the server's page. Its app and OAuth client secrets are a Secret the chart makes (kept across upgrades) or `webmail.existingSecret`, mounted as files rather than set in its environment; `webmail.previousAppSecret` reads the old app secret during a rotation. The webmail checks its read-only root at start (`IMMUTABLE`). Every server pod is told both addresses, so it registers them as OAuth clients; the webmail's client secret reaches the server as a mounted file too (`INBUXA_WEBMAIL_CLIENT_SECRET_FILE`), never the environment. - `routes`: the server's, the webmail's and the console's public addresses, each by host name, as Gateway API HTTPRoutes or one Ingress. - The server counts clients by the address the ingress or gateway and the webmail pass on (`INBUXA_HTTP_USE_FORWARDED`), so failed sign-ins and anonymous requests aren't charged to the proxy: without it, enough wrong passwords between all users would ban the ingress for everyone. `server.trustedProxies` lists the proxies when the pod network isn't a private range. Needs server 27.1-rc.32; older servers ignore it. - Certificates for the mail ports (`server.certificates`): TLS Secrets (`secrets`, or `certManager` to have the chart ask cert-manager for one) mounted in every server pod and reread within about two minutes of a renewal, with no restart; and `acmeHosts`, which routes the server's own ACME HTTP-01 challenges for the mail names to it. Needs server 27.1-rc.33. - Mail out from a known address (`server.egress`): with `expectedAddresses` and `checkUrl` set, a Job placed like the mta pods asks which address it leaves from after each install and upgrade, and records the answer on the mta Deployment as an event, a Warning when it isn't one of the expected addresses. It never fails an install. Its token may create events and nothing else. `podLabels` on each server group, for an egress gateway that selects the mta pods. - Mail in through a load balancer that sends PROXY protocol v2 (`server.services.mail.proxyProtocol`, off by default): the mail Service sends each port to a second listener in the pods that takes the client's address from the PROXY header, believed only from `trustedNetworks`, the load balancer's own addresses. It needs `externalTrafficPolicy: Local`, and server 27.1-rc.32. - A pre-flight check before each server pod starts (`server.check`, on by default): an init container runs `inbuxa --check`, which opens the data store, writes, reads and deletes a small object in the blob store, and connects to NATS. A pod that can't use one stays in `Init:Error`, and its status names the part and why. The server container keeps its last log lines as its termination message too. Needs server 27.1-rc.33: an older server doesn't know `--check`. - `tools/docs-pages.py --out