-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[cmd/opampsupervisor] Conditionally use TLS config #35363
[cmd/opampsupervisor] Conditionally use TLS config #35363
Conversation
bdb6986
to
00256ef
Compare
d5741d0
to
9635840
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is working well for me (tested both ws and wss against BPOP), seems good after Florian's comment is addressed.
@tigrannajaryan PTAL when you get a chance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dpaasman00!
) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Fixes an issue where TLS would be used despite the opamp server using `ws` or `http` protocols. Before a TLS config would always get created, causing the connection to always use TLS settings. This change first checks which protocol we're using before creating a TLS config. **Link to tracking Issue:** <Issue number if applicable> Fixes open-telemetry#35283 **Testing:** <Describe what testing was performed and which tests were added.> Removed `tls.insecure_skip_verify: true` from e2e test configs which were using `ws` protocol since they are no longer needed. **Documentation:** <Describe the documentation added.>
@dpaasman00 Is this addressed i am still getting the same tls handshake error while using ws protocol 2024/10/24 07:23:38 Failed to connect to the server: tls: first record does not look like a TLS handshake |
Description:
Fixes an issue where TLS would be used despite the opamp server using
ws
orhttp
protocols.Before a TLS config would always get created, causing the connection to always use TLS settings. This change first checks which protocol we're using before creating a TLS config.
Link to tracking Issue: Fixes #35283
Testing:
Removed
tls.insecure_skip_verify: true
from e2e test configs which were usingws
protocol since they are no longer needed.Documentation: