Hello .*, a short update for those who may also be interested in running postfix in k8s: we have a very minimal postfix setup in k8s running:
kubectl logs mx1-54b44b9b4b-z7nlt postfix/postlog: starting the Postfix mail system Oct 25 14:25:23 router2 postfix/postfix-script[68]: starting the Postfix mail system Oct 25 14:25:23 router2 postfix/master[1]: daemon started -- version 3.9, configuration /etc/postfix Some notes on early deployment: The maps/hashes that make a lot of sense on VMs/servers for avoiding reloading postfix, do not make much sense in the k8s/container context. By design, processes/containers can be unavailable. You will often run more than one instance of the container if you need HA. Instead of reparsing something, a container can be fully restarted. To be able to run in dual stack mode, the container is configured to run on an Internet facing, public machine using the "hostNetwork: true" setting. The above postfix runs with TLS enabled with receiving certificates from the cert manager. Automatic restart on certificate change is not yet implemented. The next step is to integrate postfix w/ dovecot for sasl/user relay and local mail storage. As soon as the helm chart is a little bit less hacky, I'll also share it here for others to use. BR, Nico p.s.: It seems that postfix on Alpine Linux by default does not have btree or sdbm support: Oct 25 14:52:38 router2 postfix/tlsmgr[74]: warning: btree:/var/lib/postfix/smtpd_scache is unavailable. unsupported dictionary type: btree Oct 25 15:05:01 router2 postfix/tlsmgr[75]: warning: sdbm:/var/lib/postfix/smtpd_scache is unavailable. unsupported dictionary type: sdbm -- Sustainable and modern Infrastructures by ungleich.ch
signature.asc
Description: PGP signature
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
