Issue / Limitation:

The current implementation of the Helm chart prevents the unattended-setup from being called when the overrides_config is defined.

This is basically not wrong, because we do not want to override our predefined configuration. However, this causes the issue that the default admin is not getting created, and this will prevent the deployment from being fully-automated.

if [ ! -f /data/warpgate.yaml ]; then
  warpgate -c /data/warpgate.yaml  unattended-setup --data-path /data
  ...
fi

Another thing I am not happy with when not calling the unattended setup, is that we lose the auto-generated keys and certificates. This is also a potential enhancements, so that we call the unattended-setup anyway to take care of a few things for us, then when done, we replace the generated config with ours, but this is currently out of scope.

Possible solution:

We can simply add an else to do any steps which are currently missing because of not executing the unattended setup. Though, no missing steps come to my mind except creating the admin user.

I will provide a PR for that.