Which container type is used for the service mesh proxy in SAP BTP, Kyma runtime?

Question

Options

• AAdapter container
• BSidecar container
• CProxy container
• DInit container

• A
  4% (1)
• B
  91% (21)
• C
  4% (1)

Explanation

In SAP BTP, Kyma runtime uses Istio as its service mesh, which injects a sidecar container (specifically Envoy proxy) alongside each application container within the same pod - this is the defining pattern of sidecar-based service meshes, enabling traffic management, mTLS, and observability without modifying application code.

Why the distractors are wrong:

• A. Adapter container - a real Kubernetes pod pattern, but used for normalizing output (e.g., logs/metrics) to a standard interface, not proxying traffic.
• C. Proxy container - not a recognized Kubernetes container pattern name; it's a functional description, not an architectural term.
• D. Init container - runs to completion before app containers start (e.g., for setup tasks) and exits; it cannot serve as an ongoing proxy.

Memory tip: Think "side-by-side" - a sidecar sits beside the main container in the same pod, just like a motorcycle sidecar rides alongside the driver. Istio's Envoy proxy does exactly this in Kyma's service mesh.

No community discussion yet for this question.