service mesh
A layer of proxies alongside every service that handles traffic between services: routing, retries, TLS and telemetry.
In more detail
It adds features without changing application code, because the proxies handle them. Common meshes include Istio and Linkerd.
Examples
A mesh can split canary traffic between internal services.The course names the platform as the strongest place to set defaults: if the mesh encrypts traffic with mutual TLS and injects a verified identity, no engineer can forget either.Related terms
- traffic splitting — Dividing incoming requests between two versions by percentage.
- reverse proxy — A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
- Consul — A HashiCorp tool for service discovery and a service mesh that gives services identities and encrypted connections.
- mutual TLS — TLS in which both sides present certificates, so the server also proves who the client is.
- sidecar container — A helper container that runs beside the main container in the same pod, such as a proxy, a log shipper or a file refresher.
- NetworkPolicy — A Kubernetes object that controls which pods may send traffic to or receive traffic from which others, by labels, namespaces and IP ranges.
- API gateway — A server that sits in front of one or more services and handles shared concerns such as routing, authentication, rate limits and TLS for every request.
- TLS termination — Ending an encrypted TLS connection at a proxy or gateway, which decrypts the traffic and forwards it on to the service.
Taught in
- The Rollout: A Deployment That Can Stop Halfway — Certified Argo Project Associate (CAPA) Exam Prep
- Canary Releases From Replica Counts — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Sandboxed Pods: RuntimeClass And gVisor — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Encrypting Pod-to-Pod Traffic: mTLS With Istio And Cilium — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
- Port 30080 On Every Node: kube-proxy, Networking And Clients — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Dash Too Many: Segmentation With Network Policy — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Draw The Boundaries: Trust And Data Flow — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Pod Away: Network Attackers And Sensitive Data — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Who Built This Image? Supply Chain And Registries — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Four Alerts, One Incident: Observability And The Mesh — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- A Cluster's First Birthday: PKI And Connectivity — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Forty Minutes Of Yes: Admission Control — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Platform Sprint: Evidence, Order, Proof — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Forty Three Of Sixty: The Mock, And How To Read It — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Audit Day: Final Review — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Gateway API: GatewayClass, Gateway And HTTPRoute — Kubernetes: Production-Grade Container Orchestration
- NetworkPolicy And The Consul Service Mesh Boundary — Kubernetes: Production-Grade Container Orchestration
- Secure Defaults — Application Security & Threat Modeling for Engineers