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
When Trino is not exposed to the outside world, and all traffic is inside a Kubernetes cluster and already encrypted via mTls, the necessity to use certificates is a MAJOR OVERKILL.
Service mesh systems do not add X-Forwarded-Proto http headers for mTls. So, Trino assumes the traffic is insecure, which is not true.
Suggested Solution:
Add a parameter that allows http traffic to Trino, similar to any other data/database platform on the market.
The text was updated successfully, but these errors were encountered:
hakan-77
changed the title
Allow http connection: mTls already secures traffic inside the serice Mesh
Allow http connection: mTls already secures traffic inside the Service Mesh
Oct 11, 2024
Problem:
When Trino is not exposed to the outside world, and all traffic is inside a Kubernetes cluster and already encrypted via mTls, the necessity to use certificates is a MAJOR OVERKILL.
Service mesh systems do not add X-Forwarded-Proto http headers for mTls. So, Trino assumes the traffic is insecure, which is not true.
Suggested Solution:
Add a parameter that allows http traffic to Trino, similar to any other data/database platform on the market.
The text was updated successfully, but these errors were encountered: