tezvyn:

Docker & Kubernetes

Containers, Helm, orchestration, service mesh

292 bites

More in Docker & Kubernetes — page 8

Docker & Kubernetes2 min read

Describe the relationship between containerd and runc in starting a container.

Tests the OCI runtime split and lifecycle ownership. A great answer states containerd handles image pull, storage, and API lifecycle, then invokes runC to spawn the isolated process.

Docker & Kubernetes2 min read

How do containers enforce CPU and memory limits via cgroups?

WHAT IT TESTS: Knowledge that cgroups enforce limits in the kernel, not Docker. ANSWER OUTLINE: Cover CPU CFS quota and shares, memory limits and OOM, and runtime cgroup config. RED FLAG: Confusing cgroups with namespaces or saying Docker throttles.

Name three Linux namespaces and explain what each one isolates.
Docker & Kubernetes2 min read

Name three Linux namespaces and explain what each one isolates.

WHAT IT TESTS: Kernel primitives behind container isolation. ANSWER OUTLINE: Name three of PID, Network, Mount, UTS, IPC, User, Cgroup, Time; say what each hides; cite CLONE_NEW* or /proc/pid/ns.

How do Docker images and containers differ and relate?
Docker & Kubernetes2 min read

How do Docker images and containers differ and relate?

This tests your grasp of the immutable template versus mutable runtime boundary. A good answer: an image is a read-only layered template with code and dependencies; a container is a runnable instance with a writable layer on top.

Docker & Kubernetes3 min read

Docker Content Trust: Signed Image Verification

Docker Content Trust is a cryptographic tamper-evident seal for image tags. It lets you verify who published an image before pulling from any registry. The footgun is that without DOCKER_CONTENT_TRUST=1, unsigned tags pull silently with no warning.

Docker & Kubernetes2 min read

Container Images Are Stacked Deltas

Images stack read-only layers like transparent sheets, one per Dockerfile step, topped by a thin writable layer. This enables cache reuse and fast pulls. The footgun: removing a file in a later layer hides but does not delete it; those bytes still ship.

Docker & Kubernetes2 min read

OLM: Kubernetes' App Store for Operators

OLM is the app store for Kubernetes Operators: it installs, updates, and resolves dependencies declaratively. Use it when managing third-party or custom Operators across clusters.

ResourceQuota: Namespace Resource Budgets
Docker & Kubernetes2 min read

ResourceQuota: Namespace Resource Budgets

ResourceQuota is a namespace budget: it rejects pods once total requests hit the cap. Use it to keep multi-tenant clusters fair. The footgun: it counts requested resources, not real usage, and pods missing requests may be rejected without LimitRange defaults.

ConfigMap decouples config from container images
Docker & Kubernetes2 min read

ConfigMap decouples config from container images

A ConfigMap is a key-value store that injects configuration into pods without rebuilding the image. Use it for feature flags, database hostnames, or any non-secret settings. Editing one does not restart existing pods, so stale config is the common footgun.

EndpointSlice: Splitting the Monolithic Endpoints List
Docker & Kubernetes2 min read

EndpointSlice: Splitting the Monolithic Endpoints List

EndpointSlice shards a service's pod backends into smaller chunks instead of one massive list. This keeps kube-proxy and DNS fast when services scale to thousands of pods. Do not edit them by hand; the controller owns them and will overwrite your changes.

Pod QoS Classes: Guaranteed, Burstable, BestEffort
Docker & Kubernetes2 min read

Pod QoS Classes: Guaranteed, Burstable, BestEffort

Kubernetes QoS classes are eviction priorities, not performance guarantees. Under node pressure, the kubelet kills BestEffort pods first, then Burstable, then Guaranteed. Omitting limits does not grant infinite headroom; it makes your pod die first.

Docker & Kubernetes2 min read

OCI: The USB-C of Containers

OCI is the USB-C of containers: open standards that let any compliant runtime execute any image. It prevents vendor lock-in by decoupling image format from runtime. The footgun is treating "Docker image" as proprietary rather than an OCI-compliant bundle.

Docker & Kubernetes2 min read

Kubebuilder: Build Kubernetes APIs the Canonical Way

Kubebuilder is a framework for scaffolding custom Kubernetes APIs, letting you define your own resources like `MyWebApp`. Use it to extend Kubernetes with declarative APIs, making your app a first-class citizen.

Docker & Kubernetes2 min read

OPA Gatekeeper: Enforce Kubernetes Policies as Code

OPA Gatekeeper is a Kubernetes admission controller using OPA to enforce policies on resources. Use it to mandate labels or block insecure images. The footgun is thinking it's just OPA; Gatekeeper adds K8s-native CRDs, auditing, and mutation capabilities.

Pod Topology Spread: Spreading Pods for High Availability
Docker & Kubernetes2 min read

Pod Topology Spread: Spreading Pods for High Availability

Pod Topology Spread Constraints prevent putting all your pods in one basket. They instruct the scheduler to distribute a service's pods evenly across nodes or zones, improving availability. The main footgun is that it's a soft preference by default.

CSI Volume Cloning: `cp` for Kubernetes Volumes
Docker & Kubernetes2 min read

CSI Volume Cloning: `cp` for Kubernetes Volumes

Think of volume cloning as `cp` for your Kubernetes data. It creates a new, independent volume pre-populated with data from an existing one, offloading the copy operation to your storage provider.

Kubernetes Secrets: Encrypting Data at Rest
Docker & Kubernetes2 min read

Kubernetes Secrets: Encrypting Data at Rest

By default, Kubernetes Secrets are only base64-encoded, not encrypted. Encryption at rest makes the API server encrypt Secret data before saving to etcd, protecting against compromised backups.

Docker & Kubernetes2 min read

Kubernetes Gateway API: The Successor to Ingress

The Gateway API replaces Kubernetes Ingress with a role-oriented model, separating infrastructure from application routing. Use it when different teams need to manage their own traffic rules.

kube-apiserver: The Front Door to Your Kubernetes Cluster
Docker & Kubernetes2 min read

kube-apiserver: The Front Door to Your Kubernetes Cluster

The kube-apiserver is the front door to your Kubernetes control plane. All requests to query or modify the cluster's state must pass through it, from `kubectl` commands to automated controller actions. The footgun is bypassing it to modify `etcd` directly.

Kubernetes' Declarative Model: Desired vs. Actual State
Docker & Kubernetes2 min read

Kubernetes' Declarative Model: Desired vs. Actual State

The declarative model is like telling Kubernetes your destination, not giving it turn-by-turn directions. You define the desired state in a file, and Kubernetes works to make it a reality. This enables self-healing and GitOps.