nextcloud
Feature: Allow configuring SSL for the default NGINX config file
Description of the change
Allow setting properties in the values.yaml for NGINX which update the default configuration to use SSL.
Benefits
This will make it easier to setup SSL on the NGINX instance, as currently the only option is to copy the filled-in config file from the config map and adding the necessary settings, then disabling the default file and pasting it in the custom one.
The example configuration from NGINX I think should be enough for most use cases. This change will make it easy to setup mTLS inside the cluster without needing a server mesh or other such systems.
Possible drawbacks
Added complexity to the default file and values.yaml, but it should be decent to manage.
Additional information
See how Grafana's Loki does it for their NGINX gateway as an example of the values.yaml properties.
I understand the idea of mTLS, but would it be better to use direct an servicemesh like linkerd or istio to get mTLS between the pods.
Those solutions lead to an increase in resource consumption and they are too heavy to get only for the benefit of mTLS.
I also run an environment where I don't have one already deployed so I am trying to avoid doing it only for Nextcloud.