Serve complete TLS certificate chain by appending ca.crt #8038
+20
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
Envoy Gateway previously served only the leaf certificate from
tls.crtand ignored
ca.crtwhen building the served TLS certificate chain.This PR:
ca.crtto the served certificate chain when presentWhy this is needed
Incomplete certificate chains can cause client-side verification
and OCSP-related issues. This change aligns Envoy Gateway behavior
with common TLS expectations and cert-manager style secrets.
Backward compatibility
tls.crtalready contains the full chainFixes #7804