container orchestrator
A system that decides where containers run and keeps them running, restarting, scaling and replacing them automatically.
In more detail
Kubernetes is the most widely used container orchestrator. Orchestrators restart containers that fail their health checks, send traffic only to containers that report ready, and stop a container by asking it to shut down before forcing it after a grace period.
Example
Kubernetes is the most widely used container orchestratorRelated terms
- liveness probe — A health check that answers only whether a process is alive enough to keep running; if it keeps failing, the orchestrator, such as Kubernetes, restarts it.
- readiness probe — A check that decides whether a pod should receive traffic right now; failing it removes the pod from its Service without restarting it.
- container — A running program that has been fenced off from the rest of the computer so it only sees its own files, network and processes.
- Kubernetes — An open-source system that runs and manages containers across a cluster of machines.
- Turborepo — A build tool for JavaScript monorepos that runs package tasks in dependency order, in parallel, and skips work whose inputs have not changed.
- SIGTERM — The signal that politely asks a process to finish its work and exit.
- terminationGracePeriodSeconds — The pod setting for how long Kubernetes waits after sending SIGTERM before killing the container with SIGKILL, 30 seconds by default.
- exit code — A number a process returns when it finishes: 0 means success, anything else means something went wrong.
- graceful shutdown — Stopping a service in an orderly way: finish current work, close connections, then exit.
Taught in
- Health Checks — Modern .NET Core, C# & Enterprise Microservices
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- Unified Build Pipelines: Caching & Dependency Graphs — Production Full-Stack Engineering
- Health Probes & Graceful Shutdown: Kubernetes Lifecycles — Production Full-Stack Engineering
- Context Cancellation and Timeouts — Concurrent Systems Programming with Go
- Parsing Arguments with flag — Concurrent Systems Programming with Go
- Serving HTTP with net/http Server — Concurrent Systems Programming with Go
- Graceful Shutdown on SIGTERM — Concurrent Systems Programming with Go
- Shipping in Scratch and Distroless Images — Concurrent Systems Programming with Go
- Containerizing and Testing the Final Build — Concurrent Systems Programming with Go
- Close Phase & Signal Dispatch: Sockets & Teardown — Node.js Internals & Backend Services
- Global Error Trapping: uncaughtException & Exits — Node.js Internals & Backend Services
- Cluster Architecture: node:cluster & Zero-Downtime — Node.js Internals & Backend Services
- Production Hardening: Graceful Shutdown & Docker — Node.js Internals & Backend Services