Update static tls (BoringSSL) tracing feature flag default to true and announce BoringSSL support #1678
Conversation
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
…d announce BoringSSL support Signed-off-by: Dom Del Nano <ddelnano@pixielabs.ai>
Member
Author
|
cc @pixie-io/stirling for visibility |
vihangm
approved these changes
Aug 17, 2023
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.
Summary: Update static tls (BoringSSL) tracing feature flag default to true and announce BoringSSL support
Relevant Issues: #692
Type of change: /kind feature
Test Plan: This tls tracing has been enabled since v0.14.3's release last month (#1625) and the metrics for internal clusters have been validated
Changelog Message: