Containers & Orchestration

The foundational declarative resources used to orchestrate containers, manage networking, and handle configuration in Kubernetes.

Managing container health and traffic routing using liveness, readiness, and startup probes.

The foundational network guarantees of Kubernetes, where every Pod gets a unique IP and can communicate without NAT.

Defining minimum guaranteed resources and maximum caps to prevent noisy neighbor problems and node starvation.

Optimizing container builds by structuring Dockerfiles to maximize cache hits, reduce build times, and minimize the final image footprint.

Defining and managing long-running background services, dependencies, and restart policies using the Linux init system.

Deploying helper containers alongside a primary application container within the same Pod to augment its functionality without modifying its code.

The Linux kernel features that provide containers with their own independent network stacks, interfaces, and routing tables.

The standardized directory and file layout required to package, configure, and deploy applications as Helm charts on Kubernetes.

The Linux kernel feature that limits, accounts for, and isolates the resource usage (CPU, memory, disk I/O) of a collection of processes.

The standard specification for explicitly defining which pods are allowed to communicate with each other, enforcing a zero-trust network model within a cluster.

The automated process of inspecting container images for known vulnerabilities (CVEs) and cryptographically verifying their origin to prevent supply chain attacks.