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

Question

Options

• AProxy container
• BInit container
• CSidecar container
• DAdapter container

• A
  3% (1)
• B
  8% (3)
• C
  87% (34)
• D
  3% (1)

Explanation

SAP BTP Kyma runtime uses Istio as its service mesh, which injects an Envoy proxy as a sidecar container (C) alongside your application container within the same Pod - this is the defining pattern of a sidecar: a helper container that augments the main container without being part of it. "Proxy container" (A) is not a real Kubernetes container type; it describes a role, not a kind. "Init container" (B) runs to completion before app containers start (used for setup tasks like DB migrations) and terminates - it cannot proxy live traffic. "Adapter container" (D) is a conceptual pattern from multi-container Pod design but is not a distinct Kubernetes type and is not used for service mesh proxies.

Memory tip: Think of a sidecar on a motorcycle - it rides alongside the main vehicle (your app) and shares its journey (the Pod's lifecycle and network namespace), just as the Envoy proxy rides alongside your app intercepting all traffic.

No community discussion yet for this question.