[k8s] helm charts

[volker-raschek]

Hi folks,
in the past weeks I have been working on a helm chart for postfixadmin as well as the fetchmail job. For this I packaged postfixadmin as a separate container image, because major changes were necessary.

Furthermore I adapted the fetchmail.pl script, because it was missing the option for a port. The script is also deployed via its own container and then started as a kubernetes cron job.

I would ask the community here to look at the changes and lead back in the long run. As a note, postfixadmin I currently only support as an apache image to avoid the configuration overhead in helm. Both images, postfixadmin and fetchmail, are available for ARM architecture to run on Raspberry Pis for example.

Here are the images and helm charts:

• postfixadmin image source code

• postfixadmin image

• postfixadmin chart source code

• postfixadmin chart

• fetchmail image source code

• fetchmail image

• fetchmail chart source code

• fetchmail chart

[DavidGoodwin]

Hello - thank you for the contribution? I've no experience of helm, but am curious why the 'official' docker image couldn't have been used?
( https://github.com/postfixadmin/docker )

[volker-raschek]

I think there are two main differences:

Your image supports only certain environment variables. The image from me replaces all variables with the prefix POSTFIXADMIN_ in the configuration. This works for all config parameters, except for nested configurations.

https://github.com/volker-raschek/postfixadmin-docker/blob/master/entrypoint.sh#L51

At this point, though, I'd like to play the ball back and prefer if this could be solved directly by the application. This would significantly minimize the complexity in the entrypoint.sh script and make the configuration of the container more flexible.

Next, config['setup_password'] expects a bcrypt hash from a salt. The user must be able to pass the salt value via plain text. This is not the case with your image. The user has to create the hash himself and provide it as environment variable. This annoyed me personally, so I now solve this in the entrypoint.sh script.

https://github.com/volker-raschek/postfixadmin-docker/blob/master/entrypoint.sh#L43

This was also the reason to understand how the password was generated in an older version of postfixadmin. Unfortunately I could not recreate this with linux commands #538

[DavidGoodwin]

setup password stuff - postfixadmin/docker#48

I like this bit -

# create config.local.pgp with vaules from env with POSTFIXADMIN_ prefix
POSTFIXADMIN_ENV_VARS=($(env | sort | grep --perl-regexp '^POSTFIXADMIN_.*'))

and the subsequent generation of config.local.php ....