1. Service Mesh Operations advanced Multiple choice

    A mesh runs an Envoy sidecar in each of 2400 pods across 500 services. Every proxy is pushed the whole cluster's endpoints and routes and sits at roughly 50 to 150 MB of memory - on the order of 150 to 350 GB fleet-wide. A proposal replaces sidecars with one shared proxy per node. Which fact about the estate should decide it?

    3 min answer service meshenvoyistiomemory
  2. Service Mesh Operations advanced

    A platform runs a service mesh. What are the operational realities teams underestimate?

    2 min answer service-meshoperationscontrol-planeupgrades
  3. Service Mesh Operations advanced Multiple choice

    A team proposes adopting a service mesh for twelve services in one language. Do you support it?

    2 min answer service-meshcomplexitydecision
  4. Service Mesh Operations advanced

    An Envoy-based mesh carries 600 services across 3000 pods. At 09:00 the mesh control plane is lost entirely and cannot be restored for 90 minutes. No application or node has failed. What happens over those 90 minutes, what sets the real deadline, and what would make the mesh ride it out?

    3 min answer service-meshenvoyxdsfail-static
  5. Service Mesh Operations advanced

    You must move the sidecar proxies of 500 services and 2400 pods from mesh version n-2 to n. The control plane supports one version of skew with its data plane and each proxy upgrade is a pod restart. Several services hold gRPC streams open for hours. Plan the migration so that no service sees an unplanned reset and you can stop at any point.

    3 min answer service meshenvoyupgradeversion skew