Skip to content

fix: Add ability to disable service.commonHost

As documented in #127 (closed) we are currently unable to change or disable the service.commonName. This makes it so users are unable to use Nginx Mergeable Ingress and creates a TLS issue as described in #127 (closed). This MR adds the ability to disable the commonName so that no commonName is sent to the helm chart. This allows users to use the Nginx Mergeable Ingress but does not fix the inability to set a custom service.commonName.

Merge request reports