@christoffers please amend your commit to use conventional commit:

https://www.conventionalcommits.org/en/v1.0.0/

@christoffers I mean the commit message. Sorry for not being clear.

Requesting changes for three functional issues in the new chart path: preserve existing ingress annotation values during upgrades, route SSH to the separate Service when configured, and ensure the ACME setup provisions the Traefik TLS secret. Helm lint and both default and Traefik rendering otherwise pass.

Requesting changes because the update still leaves four functional regressions: legacy values without ingress.nginx still fail at ingress.yaml:29, separate SSH routes to the main Service, single-host Traefik ACME emits an empty Certificate dnsNames, and default values now opt every installation into Traefik/TLS/ACME with placeholder settings. Helm lint succeeds after substituting the build-time chart version; targeted renders reproduce each issue.

Requesting changes for three remaining regressions: legacy reused values without ingress.nginx still fail during rendering; the defaults combine disabled Traefik mode with className: traefik; and enabled ACME adds an issuer annotation when TLS is disabled and no Issuer is rendered. Separate SSH routing and Traefik certificate provisioning are fixed, so those related threads were resolved. Helm lint passes; targeted renders reproduce the remaining blockers.

Requesting changes because legacy Helm upgrades remain broken: reused values from the previous chart do not contain ingress.traefik, and the Traefik branch still dereferences that missing map directly. The neutral defaults and TLS/ACME gating issues are fixed.

Requesting changes because legacy ACME-enabled upgrades remain broken: the new Certificate template directly dereferences the absent ingress.traefik map. Helm lint passes, but a targeted render with TLS and ACME enabled and ingress.traefik=null fails at certificate.yaml:1 with a nil-pointer error. The previously resolved certificate host fallback and SSH routing concerns remain fixed.

Requesting changes for one remaining multi-release collision: the default Traefik Middleware name is namespace-global rather than release-qualified, so installing two releases in one namespace makes the second Helm install fail ownership validation. The legacy ACME nil-map failure is fixed. Helm lint and default, Traefik ACME, and legacy-null rendering pass.

Requesting changes because the default Nginx path now renders its apiVersion on the same line as the added comment (# Render nginx resourcesapiVersion: ...), commenting it out and producing an invalid Ingress manifest. Helm lint passes, but comparison with the base render and helm template --set ingress.enabled=true reproduce the regression. The prior Traefik Middleware collision is fixed, and targeted Traefik ACME, legacy-null, separate-SSH, multi-host, and multi-release renders otherwise pass.

Requesting changes for a remaining legacy Kubernetes rendering regression: the new defaults remove ingress.annotations, but the Kubernetes <1.18 compatibility path passes that missing value directly to hasKey. Helm lint and the default Nginx render pass; a targeted Kubernetes 1.17 render with ingress.className reproduces the type error. The prior invalid-manifest newline issue is fixed and its thread was resolved.

Approved. The remaining legacy Kubernetes regression is fixed: Helm lint passes, and targeted renders succeed for Kubernetes 1.17, default Nginx, legacy null values, Traefik ACME, separate SSH, and multi-host routing.

Approved. The latest commit safely initializes ingress annotations for the Kubernetes <1.18 compatibility path. Helm lint passes, and targeted renders succeed for Kubernetes 1.17, default Nginx, legacy null values, Traefik ACME, separate SSH, and multi-host routing.

The final patch resolves the remaining legacy Kubernetes rendering issue. Helm lint passes, along with targeted renders for Kubernetes 1.17, default Nginx, legacy reused values, Traefik ACME, multi-host routing, and separate SSH routing.