Hi friends, we are just setting up Phoenix in our Google VPC. Our compliance policy requires mutual TLS between internal services, and we are trying to figure out how to send traces to Phoenix over grpc with TLS. We found this relevant post: https://github.com/Arize-ai/phoenix/issues/6469, but the solution terminates at the ingress / load balancer layer. Is there a way to terminate TLS at the service layer, not just the ingress / load balancer layer?
It seems likely that Phoenix does not currently support terminating TLS at the service layer itself. According to the GitHub issue, Phoenix is typically deployed behind a reverse proxy that handles TLS termination. The Phoenix server itself does not support configuring certificates and keys for TLS termination directly. Would you like more detail on how to configure Phoenix with a reverse proxy for TLS termination, or any other aspect of setting up Phoenix in your environment? Sources: - GitHub Issue #6469
馃挕聽Hint: Mention RunLLM in the thread for followups.
Currently this is not supported. Would you like to open a feature request?
Hi Roger, thanks for the reply! Yes I can open a feature request. Wonder if there this has come up a lot?
Hi Roger Y., is it easy to decouple the ENV_PHOENIX_TLS_ENABLED flag for grpc and http? For our use case, we actually don't need the http requests to phoenix encrypted, since we terminate TLS at the Ingress / load balancer. I tried out the grpc requests with TLS encryption, and it worked great btw!
ok i see. can you file a ticket for us to track. i can fix today or tomorrow
