Component(s)
opamp
Is your feature request related to a problem? Please describe.
Hello.
OpAMP bridge configuration does not support setting an insecure endpoint. When the endpoint is set as ws://opamp-server.opentelemetry.svc.cluster.local:4320/v1/opamp apparently it tries a secure connection anyway, and the bridge shows bad handshake error messages in its logs.
Describe the solution you'd like
Either fix the bridge behaviour to really use unsecure connections when using ws:// endpoints or add configuration options to skip TLS checking, for example:
spec:
endpoint: ws://opamp-server.opentelemetry.svc.cluster.local:4320/v1/opamp
tls:
insecure: true
Or:
spec:
endpoint: wss://opamp-server.opentelemetry.svc.cluster.local:4320/v1/opamp
tls:
insecure_skip_verify: true
Describe alternatives you've considered
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Component(s)
opamp
Is your feature request related to a problem? Please describe.
Hello.
OpAMP bridge configuration does not support setting an insecure endpoint. When the endpoint is set as
ws://opamp-server.opentelemetry.svc.cluster.local:4320/v1/opampapparently it tries a secure connection anyway, and the bridge shows bad handshake error messages in its logs.Describe the solution you'd like
Either fix the bridge behaviour to really use unsecure connections when using
ws://endpoints or add configuration options to skip TLS checking, for example:Or:
Describe alternatives you've considered
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.