Tag feed

#sre

893 posts277 followers

Explore Hashnode

Alternatives

Trending tags this week

APabhishek pareekabhishek-pareek.hashnode.dev22h ago · 6 min read

Surviving A Complete ETCD Outage, Part 1: Snapshots, And Getting Them Back When the Cluster Is Gone

ETCD is the single source of truth for a Kubernetes cluster. Every Node, Pod, Secret, ConfigMap, CRD, and RBAC rule lives there. Lose etcd on all control plane nodes and you have lost the cluster - th

0

APabhishek pareekabhishek-pareek.hashnode.dev22h ago · 10 min read

Surviving A Complete ETCD Outage, Part 2: Restoration

In Part 1 we got a verified ETCD snapshot back onto an Ansible control host, even with the cluster fully down. I've come across many a blog posts describing ETCD restoration process on a single node,

0

FFerferztyle.me2d ago · 18 min read

Kubernetes resource requests and limits explained: scheduling, throttling, and OOMKill

This is part of the Platform engineering with Go series: a growing collection of posts on Kubernetes, Go tooling, and infrastructure automation. View all posts in the series The 3am incident nobody t

0

Jjasmineparkjas-blogs.hashnode.dev2d ago · 6 min read

What wakes you at 2am when an enterprise operator deploys your agent

Month one of our enterprise rollout: three 3am pages. None of them were code bugs. None of them were model quality issues. All of them were operational surprises we had not accounted for before the ha

0

GSGeorge Simsdowntherabithole.dev3d ago · 7 min read

How a Process Really Works

As a DevOps/SRE/Platform Engineer you see many varieties of processes in the wild; Microservices writing to a database, a CI pipeline which runs linters and unit tests, the Docker ecosystem itself is

0

NHNweke Henryhenrycloud.hashnode.dev2d ago · 7 min read

I Found a Payment Failure Hidden in 600 Log Lines in 4 Seconds. Here's How. (Week 4)

Here's a scenario every engineer has lived through. Your Prometheus alert fires at 3am. Error rate spiked to 17%. You stare at the metric graph. The line goes up, stays up, comes down. You know someth

0

ASArtem Senenkouptimepage.hashnode.dev4d ago · 9 min read

Building an uptime monitor in Rust: one binary, two databases, 130K checks/sec per core

I spent the last few months building Uptimepage, an open-source uptime monitor and status page written in Rust. This post is the build story: the decisions that shaped it, the parts I rewrote, and the

0

ANAlex Nyamburablog.lxmwaniky.me5d ago · 14 min read

Jenkins, Docker, and Cloud Run: Building a Pipeline That Actually Deploys

A few weeks ago, I wrote about how I built a zero-collision URL shortener in Go using a 4-round Feistel cipher, Redis caching, and a bunch of SRE patterns. At the end of that post, I listed what was n

1

C

ARAshitha Ravindranepok.hashnode.dev5d ago · 3 min read

Root Cause Analysis in Distributed Systems: Why Looking at One Signal Isn't Enough

If you've ever been on call, you've probably experienced this situation. An alert wakes you up in the middle of the night. One service is producing thousands of errors, dashboards are flashing red, an

0

HJHarsh Jaimanharshjaiman.hashnode.dev5d ago · 16 min read

The $10 Million Incident: Why Every Enterprise Needs a CMDB (Even If Nobody Likes Maintaining It)

It starts as a routine alert at 2:47 AM. One database server stops responding. The on-call engineer acknowledges it, begins investigating, and within fifteen minutes is on a bridge call with six other

0

#sre

Search Hashnode

#sre

Explore Hashnode

Trending tags this week

Surviving A Complete ETCD Outage, Part 1: Snapshots, And Getting Them Back When the Cluster Is Gone

Surviving A Complete ETCD Outage, Part 2: Restoration

Kubernetes resource requests and limits explained: scheduling, throttling, and OOMKill

What wakes you at 2am when an enterprise operator deploys your agent

How a Process Really Works

I Found a Payment Failure Hidden in 600 Log Lines in 4 Seconds. Here's How. (Week 4)

Building an uptime monitor in Rust: one binary, two databases, 130K checks/sec per core

Jenkins, Docker, and Cloud Run: Building a Pipeline That Actually Deploys

Root Cause Analysis in Distributed Systems: Why Looking at One Signal Isn't Enough

The $10 Million Incident: Why Every Enterprise Needs a CMDB (Even If Nobody Likes Maintaining It)