Conversation
- Potentially separate CA bundle from cert-manager secret
dmeatriy
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The following improvements were made to the internal TLS support:
now during the installation one can choose whether to use the CA bundle from a dedicated secret (
tlsInternal.ca.bundled = false, default) or use the one provided by cert-manager as part of the certificate secrets.DNS names can now be configured by providing a list of values (
<service-name>.tlsInternal.certificate.dnsNames, defaults to{<service-name>.<namespace>.svc.cluster.local})the certificate encoding can now be configured (
tlsInternal.certificates.privateKey.encoding)replaced
busyboxwith theenvoyimage, sincebusyboxmight not be allowlisted.