fix(common): default SD_TLS_SKIP_VERIFY to false - #1755
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe shared Helm service-discovery template now defaults ChangesService discovery default
Possibly related PRs
✨ Finishing Touches✨ Simplify code
Comment |
Enabling service-discovery TLS without an explicit override no longer implicitly disables certificate verification (MITM risk). Operators that intentionally skip verification must now set tlsSkipVerify: true.
guimoreirar
force-pushed
the
fix/lerian-common-sd-tls-skip-verify
branch
from
July 28, 2026 13:40
ccbdd3e to
bbef066
Compare
guimoreirar
added a commit
that referenced
this pull request
Jul 28, 2026
Main auto-bumped lerian-common-helm to 1.2.1 on the #1755 merge; update the midaz lock so helm dependency build resolves the file:// dependency.
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
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
Changes the
serviceDiscoveryhelper default forSD_TLS_SKIP_VERIFYfromtruetofalseincharts/lerian-common/templates/_service_discovery.tpl, and bumpslerian-common-helmto1.2.1.Why
With
| default true, any consumer that enables service-discovery TLS without explicitly overridingtlsSkipVerifygetsSD_TLS_SKIP_VERIFY=true, silently disabling certificate verification (MITM risk). Worse, sprig'sdefaulttreats an explicitfalseas empty, so even a consumer that setstlsSkipVerify: falsestill renderedtrue.Now verification is on by default; operators who intentionally skip it must set
tlsSkipVerify: trueexplicitly.Context
Split out of #1741 (midaz productization) per the repo policy of scoping
lerian-commonchanges to their own PR. The midaz PR setsserviceDiscovery.tlsSkipVerify: falsein its values; that becomes effective once this merges and #1741 rebases. midaz is currently the only consumer ofserviceDiscovery.env(none on main), so the blast radius is limited.Backward compatibility
Consumers already setting
tlsSkipVerify: trueare unaffected. Only the implicit default changes.