Expose alb.ingress.kubernetes.io/ssl-policy as a configurable value

charts/registry/templates/ingress.yaml hardcodes several ALB annotations (listen-ports, ssl-redirect, target-type, etc.) and exposes inboundCidrs as a values-driven extensibility point, but there's no way to set alb.ingress.kubernetes.io/ssl-policy. Without it, the AWS Load Balancer Controller falls back to its own legacy default (ELBSecurityPolicy-2016-08), which can cause TLS handshake failures with some client-side security proxies/brokers expecting a more modern policy (e.g. ELBSecurityPolicy-TLS-1-2-Ext-2018-06).

Workaround: manually annotate the live Ingress object outside of Helm.

Suggested fix: add an optional global.ingress.sslPolicy value, following the same pattern as inboundCidrs.

Check charts/registry/templates/ingress.yaml, where the ALB annotations are defined, and confirm that alb.ingress.kubernetes.io/ssl-policy is not currently configurable. Then inspect the chart values file (such as charts/registry/values.yaml) for the existing inboundCidrs/global.ingress pattern and add a parallel global.ingress.sslPolicy option. Run helm template or helm lint to render the chart and verify the ingress manifest includes the ssl-policy annotation when the value is set. Done means Helm users can configure SSL policy via values instead of manual ingress edits.

由索引模型根据 Issue 内容生成。