Force all incoming and outgoing comms to K8S pod via consul's envoy proxy


I want to understand if there is a way to force all incoming and outgoing comms for a pod via consul connect’s envoy proxy sidecar.

Currently, the port of the main container is still accessible via the pod ip.



Hi Kunal,
This is not possible right now. For incoming comms, you need to change the bind address of your application to only be localhost (instead of all interfaces). For outgoing comms, there is no way to force routing through the envoy proxy right now. It’s up to the application to ensure it’s only speaking to the envoy proxy upstream ports.