• Home
• internal mesh
• Strip internal mesh-machinery headers when sending requests/responses out of mesh · Issue #17635 · istio/istio · GitHub

Strip internal mesh-machinery headers when sending requests/responses out of mesh · Issue #17635 · istio/istio · GitHub

4.8 (794) · $ 4.00 · 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

istio-samples/mesh-expansion-gce/scripts/vm-install-istio.sh at master · GoogleCloudPlatform/istio-samples · GitHub

Connect external https services from istio mesh, with certificate provided by the service · Issue #15451 · istio/istio · GitHub

Blog: Istio - An Open Platform Service Mesh

Istio Service Mesh: The Step by Step Guide

Unable to remove server header · Issue #13861 · istio/istio · GitHub

Getting started with OpenTelemetry for Istio Service Mesh

Istio: Canary Deployments, Dynamic Routing & Tracing

Istio - Weaving the Service Mesh - InfoQ

GitHub - istio/istio: Connect, secure, control, and observe services.

Istio - Weaving the Service Mesh - InfoQ

Istio ingress still forwarding request to a pod that got marked terminated 9mins ago · Issue #44985 · istio/istio · GitHub

Request Headers Route Rule with composite services does not work · Issue #1380 · istio/istio · GitHub