Skip to content

Conversation

@davinkevin
Copy link

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

This change introduces a new flag in the TLSConfig to leverage both CACert provided by end-users and System certificates from the host.

Until now, it was not possible to do both at the same time, leading to complex configuration when cert chains are too long (k8s size limits for configMaps) or when we share certificates with other application using an "additive system" (as the opposite of the code before this PR).

Verification

I tested the code locally, but I'm open to more testing as my client was built into mimir, so maybe not good enough.

NOTE I've opened a PR as this change is so small, it would be simpler to discuss around a PR than an issue. If it's ok for you, then I'll modify the changelog and other mandatory items.

Thank you in advance.

…same time

Signed-off-by: Davin Kevin <davin.kevin@gmail.com>
@davinkevin davinkevin force-pushed the feat-support-ca-and-host-ca branch from fff3ca6 to 78e7d2f Compare January 8, 2026 08:20
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.

2 participants