Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tempo-query: separate tls settings for server and client #4177

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

frzifus
Copy link
Contributor

@frzifus frzifus commented Oct 11, 2024

What this PR does:
This PR extends tempo-query with the possibility to configure tls for server and client individually.

cc @pavolloffay

Which issue(s) this PR fixes:

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

@@ -11,6 +11,7 @@ type Config struct {
Address string `yaml:"address"`
Backend string `yaml:"backend"`
TLSEnabled bool `yaml:"tls_enabled" category:"advanced"`
TLSServerEnabeld bool `yaml:"tls_server_enabled" category:"advanced"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you make some comments for TLSEnabled and TLSServerEnabled ?

@pavolloffay
Copy link
Contributor

@frzifus once this is merged please open a PR to backport it to release-v2.6 branch

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