You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the original configuration, the tls section was explicitly defined with a specific host (workflow.example.com) and a secret name (host-domain-cert). This meant that the Ingress resource would always include this TLS configuration unless it was manually overridden or commented out. However, this approach had a downside: if a custom certificate was being used (e.g., managed externally), or if TLS wasn’t needed, there was no clear way to disable it without modifying the template or values file. Additionally, this setup could unintentionally trigger tools like cert-manager to generate certificates for the listed hosts, even if that wasn’t desired.
In the updated configuration, the tls section is set to an empty list ([]) by default, with the previous configuration commented out as an example or reference. This change ensures that, by default, no TLS configuration is applied unless explicitly overridden in the values.yaml file or via Helm command-line arguments (e.g., --set).
The text was updated successfully, but these errors were encountered:
Hey
Can't open PR for minor changes.
In the original configuration, the tls section was explicitly defined with a specific host (workflow.example.com) and a secret name (host-domain-cert). This meant that the Ingress resource would always include this TLS configuration unless it was manually overridden or commented out. However, this approach had a downside: if a custom certificate was being used (e.g., managed externally), or if TLS wasn’t needed, there was no clear way to disable it without modifying the template or values file. Additionally, this setup could unintentionally trigger tools like cert-manager to generate certificates for the listed hosts, even if that wasn’t desired.
In the updated configuration, the tls section is set to an empty list ([]) by default, with the previous configuration commented out as an example or reference. This change ensures that, by default, no TLS configuration is applied unless explicitly overridden in the values.yaml file or via Helm command-line arguments (e.g., --set).
The text was updated successfully, but these errors were encountered: