4.9 (233) · $ 21.50 · In stock
Describe the feature request In a couple of situations Istio's default configuration exposes internal mesh-machinery headers outside of the mesh; either to callers or callees. Ingress Gateway Response header x-envoy-upstream-service-time
How to get more from OpenShift Service Mesh monitoring
Istio - Weaving the Service Mesh - InfoQ
Blog: Istio - An Open Platform Service Mesh
Host Header Limitation/Advice · Issue #9107 · istio/istio · GitHub
Request Headers Route Rule with composite services does not work · Issue #1380 · istio/istio · GitHub
C Service mesh and Istio fundamentals - Microservices Security in Action
Header matching by VirtualService does not work in mesh pod-to-pod communication with holdApplicationUntilProxyStarts · Issue #29215 · istio/ istio · GitHub
Step by Step Guide to install Istio Service Mesh in Kubernetes - DEV Community
GitHub - tnscorcoran/openshift-servicemesh
Concern over leaking sensitive information in headers X-Envoy-Peer-Metadata and X-Envoy-Peer-Metadata-Id · Issue #35283 · istio/istio · GitHub
Ingress Routing & Traffic Management in OpenShift Service Mesh - Rcarrata's Blog
Istio - Weaving the Service Mesh - InfoQ
Strip internal mesh-machinery headers when sending requests/responses out of mesh · Issue #17635 · istio/istio · GitHub