Skip to content

fix(charts): ingress ssl policy - #1720

Open
omrishiv wants to merge 2 commits into
agentic-community:mainfrom
omrishiv:fix/ingress-ssl-policy-1661
Open

fix(charts): ingress ssl policy#1720
omrishiv wants to merge 2 commits into
agentic-community:mainfrom
omrishiv:fix/ingress-ssl-policy-1661

Conversation

@omrishiv

@omrishiv omrishiv commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Issue #, if available:

Closes: #1661

Description of changes:

Adds an overrideable field to change the default ssl policy for the registry ingress

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Add optional global.ingress.sslPolicy that renders
alb.ingress.kubernetes.io/ssl-policy on the registry ingress,
following the same pattern as inboundCidrs. Leaving it unset preserves
the AWS Load Balancer Controller default (ELBSecurityPolicy-2016-08);
operators can set a modern policy (e.g.
ELBSecurityPolicy-TLS-1-2-Ext-2018-06) to avoid TLS handshake failures
with clients requiring newer TLS.

Closes agentic-community#1661
…alues

Add documented (empty) global.ingress.inboundCidrs and
global.ingress.sslPolicy keys to the registry subchart values so the
knobs are discoverable for standalone (non-umbrella) deploys. Empty
defaults are falsy and leave both annotations omitted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant