Chisato · · 3 min read What Is a Runbook? Incident Response Playbooks
A runbook is a step-by-step document for handling a specific operational task or incident, turning tribal knowledge into a repeatable procedure.
Topic
57 posts tagged “DevOps”.
Chisato · · 3 min read A runbook is a step-by-step document for handling a specific operational task or incident, turning tribal knowledge into a repeatable procedure.
Chisato · · 4 min read ConfigMaps store non-sensitive configuration; Secrets store credentials with base64 encoding and tighter access controls. When to use each.
Chisato · · 4 min read A NAT gateway lets private-subnet resources reach the internet outbound while staying unreachable from it, translating private IPs to a public one.
Chisato · · 4 min read Deployments manage interchangeable, stateless pods; StatefulSets give each pod a stable identity and storage. When each one actually belongs.
Chisato · · 5 min read Multi-cloud spreads workloads across public cloud providers; hybrid cloud connects private infrastructure to a public cloud. How they differ and why it matters.
Chisato · · 5 min read A Kubernetes operator encodes operational knowledge into software, automating tasks a human admin would otherwise do by hand for a specific application.
The Lycoris Team · · 4 min read Distributed tracing follows a single request as it crosses service boundaries, using spans and trace IDs to reconstruct the full call path and find where time goes.
Chisato · · 5 min read Exponential backoff spaces retries further apart after each failure so clients stop hammering a struggling service. How it works, and why it needs jitter.
Chisato · · 5 min read Logs, metrics, and traces each answer a different question about a running system — what each captures, and how they work together.
Chisato · · 5 min read Terraform and Ansible solve different infrastructure problems: declarative provisioning versus procedural configuration. When to use each, and when to use both.
Chisato · · 4 min read A monorepo holds all projects in one repository; a polyrepo splits them apart. Trade-offs in tooling, ownership, and CI/CD for each approach.
The Lycoris Team · · 4 min read An SBOM is a complete inventory of every component in a piece of software, including its dependencies. Why it matters for tracking vulnerabilities at scale.
Chisato · · 4 min read Active-active runs every region live and load-balanced; active-passive keeps a standby idle until failover. How each affects cost, consistency, and recovery.
The Lycoris Team · · 3 min read A container registry stores and distributes container images by content-addressed layers, letting Docker and Kubernetes pull only what's changed.
Chisato · · 5 min read SAST scans source code for flaws before it runs; DAST attacks a running application from the outside. How the two testing approaches differ and when to use each.
Chisato · · 4 min read The twelve-factor app is a set of principles for building portable, scalable cloud software. Each factor explained, and why they still hold up today.
Chisato · · 4 min read Ingress and Gateway API both route external traffic into a Kubernetes cluster. Gateway API is the more expressive successor — here's how they differ.
Chisato · · 4 min read Log aggregation collects logs from every service into one searchable system, so debugging a distributed app doesn't mean SSHing into a dozen machines.
Chisato · · 4 min read Kubernetes HPA scales pod replica count; VPA resizes CPU and memory requests per pod. How each autoscaler works and when to use them together.
Chisato · · 6 min read JetBrains patched CVE-2026-63077, an unauthenticated RCE affecting all TeamCity On-Premises versions. Why a CI/CD server is a supply-chain crown jewel.
Chisato · · 4 min read A VPC is an isolated, software-defined network inside a public cloud. How subnets, routing, and security groups fit together to keep resources private.
Chisato · · 4 min read Infrastructure drift is when a system's real-world state diverges from what its infrastructure-as-code declares. Causes, detection, and how to prevent it.
Chisato · · 5 min read A Helm chart bundles a Kubernetes application's manifests into a templated, versioned package you can install, upgrade, and roll back as one unit.
Chisato · · 4 min read Secrets management stores API keys, passwords, and certificates in a dedicated system instead of config files, with access control, rotation, and audit logs.
Chisato · · 4 min read A liveness probe restarts a stuck container; a readiness probe pulls it from traffic without restarting it. How Kubernetes uses each one.
Chisato · · 4 min read Infrastructure as code defines servers, networks, and services in version-controlled files instead of manual setup. How IaC works and why teams use it.
Chisato · · 4 min read Docker images are stacks of read-only layers cached by content hash. How layer order affects build speed, cache hits, and final image size.
Chisato · · 4 min read Horizontal scaling adds more machines; vertical scaling adds more power to one machine. How each works, their limits, and when to use which.
The Lycoris Team · · 4 min read Object, block, and file storage organize data differently and suit different workloads. How each one works and how cloud providers implement them.
Chisato · · 4 min read An API gateway and a reverse proxy both sit in front of your services, but a gateway adds API-specific logic a plain proxy doesn't. Here's the difference.
Chisato · · 5 min read A database migration is a version-controlled script that changes a schema incrementally. How migration tools track state and apply changes safely.
Chisato · · 4 min read Immutable infrastructure replaces servers instead of patching them in place — every change ships as a new, versioned artifact. How it works and why.
Chisato · · 4 min read The circuit breaker pattern stops a service from hammering a failing dependency, failing fast instead and giving the downstream system room to recover.
Takina · · 4 min read A feature flag is a runtime switch that turns functionality on or off without a deploy, used for gradual rollouts, A/B tests, and instant kill switches.
Chisato · · 3 min read The sidecar pattern runs a helper container alongside your app in the same pod, adding logging, proxying, or security without touching app code.
Chisato · · 4 min read GitOps uses a Git repository as the single source of truth for infrastructure state, with an automated agent reconciling the live system to match it.
Chisato · · 4 min read An SLI measures reliability, an SLO sets an internal target for it, and an SLA is the contractual promise built on top. Here's how the three fit together.
Chisato · · 4 min read Chaos engineering deliberately injects failures into production-like systems to find weaknesses before real outages do. How it works in practice.
Chisato · · 4 min read Edge computing runs code and stores data near where it's generated instead of in a centralized data center, cutting latency and bandwidth costs.
Chisato · · 4 min read Observability is the ability to understand a system's internal state from its external outputs — built from logs, metrics, and traces working together.
Chisato · · 4 min read A cron job runs a command automatically on a fixed schedule defined by a five-field expression. How cron syntax works and where it's still used today.
Chisato · · 4 min read Blue-green deployments switch traffic all at once between two environments; canary deployments shift it gradually. How each works and when to use them.
Chisato · · 5 min read A reverse proxy sits in front of servers, forwarding client requests and hiding backend topology. TLS termination, caching, and load balancing explained.
Chisato · · 4 min read A service mesh is a dedicated infrastructure layer that handles service-to-service traffic, retries, and encryption without changing app code.
Chisato · · 4 min read One faulty CrowdStrike update blue-screened 8.5 million Windows machines and grounded flights. A teardown of how a config file became a global outage.
Chisato · · 5 min read Pods, Deployments, and Services are the three Kubernetes objects every beginner must understand. What each one does and how they fit together.
The Lycoris Team · · 4 min read Monoliths ship faster early; microservices buy independent scaling and team autonomy at the cost of distributed complexity. How to choose.
Chisato · · 5 min read Docker builds and runs containers; Kubernetes orchestrates fleets of them. What each tool does, how they work together, and when Compose is enough.
Chisato · · 5 min read Stop deploying by hand. Learn how to set up continuous integration and deployment with GitHub Actions — tests on every push, deploys on every merge.
The Lycoris Team · · 5 min read Platform engineering transforms DevOps into a product mindset, giving developers self-service golden paths so they can ship without becoming Kubernetes experts.
The Lycoris Team · · 4 min read Apache Kafka is a distributed event-streaming platform built on a durable, append-only log. How topics, partitions, and consumers power real-time pipelines.
The Lycoris Team · · 4 min read Terraform lets you declare cloud infrastructure as code and provision it reproducibly across AWS, GCP, and Azure. How plan/apply, state, and modules work.
The Lycoris Team · · 5 min read Supply chain attacks exploit your dependencies, not your code. Learn SBOMs, SLSA, and Sigstore to defend against them before a CVE drops.
Chisato · · 2 min read Docker packages your app and everything it needs into one portable container. Learn the core concepts and ship your first containerized app in minutes.
The Lycoris Team · · 4 min read Serverless means deploying code without managing servers — the platform scales it and you pay per use. How it works and where it fits.
Chisato · · 5 min read eBPF runs sandboxed programs inside the Linux kernel without recompiling it. How it works and why it reshaped observability, networking, and security.
Chisato · · 6 min read Kubernetes (K8s) is the open-source system for deploying, scaling, and managing containers. A plain-English definition, core concepts, and when to use it.