You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe your use case / problem.
Our organization has a strict compliance requirement that mandate all end-to-end communications with services to be conducted over HTTPS. Presently, we utilize cluster-wide OTLP collectors exposing trace endpoints over TLS. However, there is currently no way to customize TracingService for exporting traces using TLS.
Describe the solution you'd like
An additional field under TracingService that supports TLS. Something similar to
Describe alternatives you've considered
Haven't been able to come up with anything unfortunately. Putting a proxy to handle the TLS negotiation wouldn't be a viable alternative since we require E2E TLS.
The text was updated successfully, but these errors were encountered:
Please describe your use case / problem.
Our organization has a strict compliance requirement that mandate all end-to-end communications with services to be conducted over HTTPS. Presently, we utilize cluster-wide OTLP collectors exposing trace endpoints over TLS. However, there is currently no way to customize TracingService for exporting traces using TLS.
Describe the solution you'd like
An additional field under TracingService that supports TLS. Something similar to
Describe alternatives you've considered
Haven't been able to come up with anything unfortunately. Putting a proxy to handle the TLS negotiation wouldn't be a viable alternative since we require E2E TLS.
The text was updated successfully, but these errors were encountered: