A civic permitting service should keep calling localhost while a helper container translates those calls to a legacy mainframe adapter. Which pattern is this?
Select an answer to reveal the explanation.
Short Explanation
An ambassador is like a bilingual concierge in the same suite: your app speaks simple localhost, and the concierge translates to the cranky legacy system next door.
Full Explanation
The ambassador pattern places a proxy sidecar beside the application so the app talks to localhost while the sidecar handles protocol or endpoint adaptation. That keeps legacy integration out of the main codebase. Init containers are one-shot setup, not ongoing proxies. DaemonSets and PVCs address node agents and storage, not this outbound adaptation pattern.