The wildduck pod randomly restarts due to the liveliness probe failing. On my k3s instance this is due to redis failing some of the requests. Redis should be available so I have to look into why it is failing this consistently.
The current nodemailer/zonemta-wildduck docker image is not open source and is pretty out-dated. I would love to see if we can create a new docker image running zonemta with wildduck.
There should be a load balancer for haraka that publishes port 25 in the cluster so it is accessible from the outside.
The haraka pod should then also have these two annotations: app.kubernetes.io/instance = haraka app.kubernetes.io/name = haraka
Maybe the actual values has to be specific for the release so multiple instances
Because I had initially copy and pasted the values.yaml from (I think) the template, because to be honest I had no clue what I was doing when I started this project. Now there are a lot of unused values in the values.yaml. Cleaning this up will result in a cleaner and more easy to use file.