DEV Community: Neeraja Khanapure

Not in any textbook — learned this from a 3am page:

Neeraja Khanapure — Tue, 30 Jun 2026 11:31:56 +0000

LinkedIn Draft — Workflow (2026-06-30)

Not in any textbook — learned this from a 3am page:

On-call burnout is an alert design problem, not a schedule problem

Every team I've seen fight burnout by rotating people faster. The actual fix is almost always the same: the alerts are wrong.

Alert quality spectrum:

Noisy ◀─────────────────────────── ▶ Actionable

[cpu > 80%]  [pod restart]  [error budget burn]  [customer impact]
     │              │               │                    │
 ignore me      maybe?         investigate!          wake me up

Where it breaks:
▸ Alerts without a named owner and a runbook produce paralysis, not action — especially at 2am.
▸ Flapping alerts are the fastest path to alert blindness — engineers learn to dismiss pages before reading them.
▸ Cause-based alerts (disk full) and symptom-based alerts (latency spike) need different urgency and routing.

The rule I keep coming back to:
→ Before any alert ships: Who acts on it? What do they do? What's the cost of 30 minutes of inaction? If you can't answer all three, it's not ready.

How I sanity-check it:
▸ Weekly alert review ritual: tag every last-week page as actionable / noisy / redundant. Kill the bottom two categories.
▸ PagerDuty/OpsGenie grouping + escalation policies — reduce interrupt rate without hiding real incidents.

Reliability is a product feature. The engineers who treat it that way are the ones who get asked into the room.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/on-call-burnout-is-an-alert-design-problem-not-a-schedule-problem

Hiring managers: engineers who think about this in interviews are the ones worth calling back.

sre #observability #reliability #devops

One insight that changed how I design systems:

Neeraja Khanapure — Fri, 26 Jun 2026 11:33:43 +0000

LinkedIn Draft — Insight (2026-06-26)

One insight that changed how I design systems:

Feature flags are ops infrastructure, not a product team tool

Most platform teams treat feature flags as a product/A-B testing concern and miss the most operationally valuable use case: instant rollback for any backend change, without a redeployment. The teams with the lowest incident MTTR almost all have the same secret — they can disable any code path in 30 seconds.

Feature flag as ops tool:

New backend change ships ──▶ [flag: new_auth_flow = true]
                                        │
                              Incident detected (T+12min)
                                        │
                              [flag: new_auth_flow = false]
                                        │
                              Recovery complete (T+13min)

vs. traditional rollback:    Recovery complete (T+75min)

The non-obvious part:
→ A feature flag that can disable a code path in 30 seconds is worth more than any runbook during an active incident. It converts a deployment rollback — with its pipeline, merge, and propagation delays — into a config change. Most platform teams own the infra for this and never tell product teams it exists.

My rule:
→ Every significant backend change ships behind a flag for at least 2 weeks post-deploy. Flags are cheap. Incidents are not. Make flags a deployment requirement, not an option.

Worth reading:
▸ Martin Fowler — Feature Toggles pattern (martinfowler.com/articles/feature-toggles.html)
▸ LaunchDarkly / Unleash — flag lifecycle management and audit logging best practices

https://neeraja-portfolio-v1.vercel.app/insights/feature-flags-are-ops-infrastructure-not-a-product-team-tool

If this resonated, share it with one person on your team who'd benefit. That's how good thinking spreads.

devops #sre #observability #platformengineering

Something I keep explaining in architecture reviews:

Neeraja Khanapure — Tue, 23 Jun 2026 11:42:02 +0000

LinkedIn Draft — Workflow (2026-06-23)

Something I keep explaining in architecture reviews:

Secrets management: designing for rotation, not just storage

Most orgs solve 'where do we store secrets securely.' The teams that get paged at 2am are the ones who never solved 'how do we rotate them without downtime.'

Storage-only design:        Rotation-aware design:

Secret ──▶ Vault            Secret ──▶ Vault ──▶ Agent Injector
              │                                        │
         Pod (env var)                           Pod (file mount)
              │                                        │
         Restart to           Auto-reload ◀────── Lease renewer
         get new value        (zero downtime)

Where it breaks:
▸ Secrets as env vars require pod restarts on rotation — making rotation a deployment event with blast radius.
▸ Vault leases expiring in long-running jobs produce auth errors that look like app bugs, not infra failures.
▸ Secret sprawl across namespaces means rotation happens in 12 places — and one always gets missed.

The rule I keep coming back to:
→ Design rotation before you design storage. If you can't rotate a secret in under 10 minutes with no downtime, the design isn't production-ready.

How I sanity-check it:
▸ Vault Agent Injector or External Secrets Operator — decouple secret delivery from pod lifecycle.
▸ Monthly secret access log audit — stale consumers are how you discover forgotten service accounts before attackers do.

Reliability is a product feature. The engineers who treat it that way are the ones who get asked into the room.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/secrets-management-designing-for-rotation-not-just-storage

If this triggered a war story, I'd genuinely love to hear it.

security #devops #kubernetes #sre

This is what separates teams that scale from teams that survive:

Neeraja Khanapure — Fri, 19 Jun 2026 12:36:33 +0000

LinkedIn Draft — Insight (2026-06-19)

This is what separates teams that scale from teams that survive:

Dependency updates are reliability work, not maintenance work

The orgs that get hit hardest by CVEs and supply chain incidents have one thing in common: they batch dependency updates into quarterly sprints. By then, the update is a 6-version jump, the changelog is 200 lines, and the 'quick upgrade' becomes a multi-day incident waiting to happen.

Batch update model (risky):   Continuous model (safe):

Q1: Skip                      Week 1: +2 deps (auto-PR)
Q2: Skip                      Week 2: +1 dep (auto-PR)
Q3: Skip                      Week 3: +3 deps (auto-PR)
Q4: "Upgrade sprint"          ...
    6-version jumps            Each PR: small diff, fast review
    Breaking changes           Rollback: one PR revert
    3-day debugging session    MTTR if it breaks: 10 min

The non-obvious part:
→ Automated dependency PRs (Renovate/Dependabot) with a 2-week merge SLA cost almost nothing — a 5-minute review per PR. Skipping them accumulates a compounding tax: more conflicts, larger blast radius, slower rollback. The math strongly favors continuous updates.

My rule:
→ Automate dependency PRs. Set a team policy: merge or explicitly defer within 2 weeks. Every skip is a known risk you're consciously accepting — treat it that way.

Worth reading:
▸ Renovate Bot — automerge strategies, scheduling, and grouping (docs.renovatebot.com)
▸ SLSA framework — supply chain integrity levels and provenance (slsa.dev)

https://neeraja-portfolio-v1.vercel.app/insights/dependency-updates-are-reliability-work-not-maintenance-work

If you're earlier in your career: bookmark this. It'll make more sense after your first real production incident.

devops #sre #observability #platformengineering

This is the gap between 'it works' and 'it's operable':

Neeraja Khanapure — Tue, 16 Jun 2026 13:16:43 +0000

LinkedIn Draft — Workflow (2026-06-16)

This is the gap between 'it works' and 'it's operable':

Platform engineering: the paved road fails when it paves over developer autonomy

Internal platforms succeed when product teams choose them because they reduce friction — not when they're mandated because someone drew a box on an architecture diagram.

Platform adoption models:

Mandate model:              Product model:

CTO decrees IDP ──▶         Platform team ships ──▶ Reduces deploy time
Teams forced to use │        │                        │
       │            │        ▼                        ▼
Workarounds found   │       Developers adopt      Platform iterates
Shadow IT grows ◀───┘       voluntarily            on real friction

Where it breaks:
▸ Compliance-first platforms get abandoned the moment engineers find a workaround — adoption needs perceived value.
▸ Golden path templates that aren't maintained become the thing everyone forks immediately — N diverged paths.
▸ Platform teams without production on-call exposure build abstractions that look clean and fail badly.

The rule I keep coming back to:
→ Measure platform success by developer time-to-production and incident contribution rate — not by adoption numbers you control.

How I sanity-check it:
▸ Backstage for catalog + portal — but treat it as a product, not a project. Stale catalogs are worse than no catalog.
▸ Quarterly 'friction interviews' with 3-5 product engineers — they'll identify the real bottlenecks faster than any metric.

The best platform teams I've seen measure success by how rarely product teams have to think about infrastructure.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/platform-engineering-the-paved-road-fails-when-it-paves-over-developer-autonomy

Strong opinions on this? Good. I want to hear the pushback.

platformengineering #devops #sre #kubernetes

A Friday systems thinking thread — worth sitting with:

Neeraja Khanapure — Fri, 12 Jun 2026 12:02:50 +0000

LinkedIn Draft — Insight (2026-06-12)

A Friday systems thinking thread — worth sitting with:

Observability debt is invisible until an incident makes it expensive

You can't debug what you can't slice. Teams add dashboards for years and still can't answer the two questions that matter most in an incident: which customers are affected, and which change caused it. The problem is almost never the tool — it's the label strategy.

Observability debt accumulation:

Month 1:  Service A metrics added (no ownership labels)
Month 3:  Service B metrics added (different label schema)
Month 6:  Dashboard count: 47. Useful in incident: 3.
Month 9:  P0 incident. Can't isolate by customer/version.
          Engineer guesses. Guesses wrong. +45min MTTR.

Fix: Define label schema FIRST. Instrument second.

The non-obvious part:
→ The teams that debug incidents fastest don't have more metrics — they have metrics that answer the right questions at the right cardinality. SLI-first instrumentation design is a force multiplier. Most teams instrument first and wonder why dashboards are noisy.

My rule:
→ Define your SLIs, then design labels that let you isolate by (service, env, version, customer tier) without exploding cardinality. Instrument last.

Worth reading:
▸ Brendan Gregg's USE Method + Google's RED Method for SLI-first design
▸ Prometheus label best practices — cardinality anti-patterns (prometheus.io/docs)

https://neeraja-portfolio-v1.vercel.app/insights/observability-debt-is-invisible-until-an-incident-makes-it-expensive

What's the version of this that your org gets wrong? Drop it below.

devops #sre #observability #platformengineering

Something every senior engineer learns the expensive way:

Neeraja Khanapure — Tue, 09 Jun 2026 11:43:08 +0000

LinkedIn Draft — Workflow (2026-06-09)

Something every senior engineer learns the expensive way:

Terraform DAGs at scale: when the graph becomes the hazard

Terraform's dependency graph is elegant at small scale. At 500+ resources across a mono-repo, it becomes the most dangerous part of your infrastructure.

SAFE (small module):              DANGEROUS (at scale):

[vpc] ──▶ [subnet] ──▶ [ec2]     [shared-net] ──▶ [team-a-infra]
                                          │         [team-b-infra]
                                          │         [team-c-infra]
                                          │         [data-layer]
                                  One change → fan-out destroy/create

Where it breaks:
▸ Implicit ordering assumptions survive until a refactor exposes them — usually as an unplanned destroy chain in prod.
▸ Fan-out graphs make blast radius review near-impossible. 'What does this change affect?' has no fast answer.
▸ depends_on papering over bad module interfaces — it fixes the symptom and couples the modules permanently.

The rule I keep coming back to:
→ If a module needs depends_on to be safe, the module boundary is wrong. Redesign the interface — don't paper over it.

How I sanity-check it:
▸ terraform graph | dot -Tsvg > graph.svg — visualize fan-out and cycles before every major refactor.
▸ Gate all applies with OPA/Conftest + mandatory human review on any planned destroy operations.

The difference between a senior engineer and a principal is knowing which guardrails to build before you need them.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/terraform-dags-at-scale-when-the-graph-becomes-the-hazard

Curious what guardrails you've built around this. Drop your pattern below.

terraform #iac #devops #sre

One insight that changed how I design systems:

Neeraja Khanapure — Fri, 05 Jun 2026 11:50:21 +0000

LinkedIn Draft — Insight (2026-06-05)

One insight that changed how I design systems:

CI/CD maturity isn't deploy frequency — it's rollback speed

Most orgs measure pipeline health by how fast they can ship. The metric that actually predicts reliability is how fast they can un-ship. The teams I've seen handle incidents best can rollback any change in under 5 minutes — not because of tools, but because they designed for it.

Pipeline maturity spectrum:

Level 1:  Manual deploys, no rollback plan
Level 2:  Automated deploys, manual rollback (30-60 min)
Level 3:  Automated deploys, scripted rollback (5-15 min)
Level 4:  Progressive delivery + auto-rollback on SLO breach
          (Rollback = automatic, measured in seconds)

Most orgs think they're at L3. Incidents reveal they're at L2.

The non-obvious part:
→ At scale, the teams who deploy most confidently are the ones who've made rollback boring and automatic — not the ones who've made deploys faster. Speed without a safety net is just a higher-velocity path to incidents.

My rule:
→ If your rollback plan starts with 'first, find the last good commit...', you don't have a rollback plan. You have a recovery plan. These are not the same thing.

Worth reading:
▸ Google SRE Book — Release Engineering & Change Management (ch. 8)
▸ Argo Rollouts docs — metric-gated progressive delivery and auto-rollback

https://neeraja-portfolio-v1.vercel.app/insights/cicd-maturity-isnt-deploy-frequency-its-rollback-speed

If you're a manager reading this — it's worth asking your team where they are on this.

devops #sre #observability #platformengineering

Not in any textbook — learned this from a 3am page:

Neeraja Khanapure — Tue, 02 Jun 2026 12:27:30 +0000

LinkedIn Draft — Workflow (2026-06-02)

Not in any textbook — learned this from a 3am page:

Kubernetes cost spikes: the usual suspects and how to find them fast

Cloud bills spike in Kubernetes for the same reasons every time. None of them are visible in the default dashboards — and most of them are invisible until month-end.

Cost leak sources (ranked by surprise factor):

1. Unset resource requests   → scheduler packs nodes → OOM → over-provision
2. Autoscaler scale-down lag → zombie nodes after traffic spike
3. Log pipelines w/o sample  → 40% of bill, 0% of dashboards
4. Idle namespaces           → dev clusters running 24/7
5. Spot interruption gaps    → fallback to on-demand, never reverted

Where it breaks:
▸ Missing resource requests let the scheduler over-pack nodes — when pods OOM, you over-provision to compensate.
▸ Cluster autoscaler adds nodes faster than it removes them. Spot interruptions leave zombie capacity for hours.
▸ Logging agents (Fluentd/Filebeat) on every node with no sampling become the largest line item nobody owns.

The rule I keep coming back to:
→ Every workload needs requests AND limits. Review autoscaler scale-down thresholds monthly. Sample logs at source, not at the sink.

How I sanity-check it:
▸ Kubecost or OpenCost — per-namespace/team attribution. Without this, no one feels accountable for the number.
▸ KEDA for event-driven workload scaling — eliminates idle replicas without sacrificing responsiveness.

The best platform teams I've seen measure success by how rarely product teams have to think about infrastructure.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/kubernetes-cost-spikes-the-usual-suspects-and-how-to-find-them-fast

Strong opinions on this? Good. I want to hear the pushback.

kubernetes #finops #devops #platformengineering

Something I wish someone had told me five years earlier:

Neeraja Khanapure — Fri, 29 May 2026 11:56:59 +0000

LinkedIn Draft — Insight (2026-05-29)

Something I wish someone had told me five years earlier:

Zero-downtime deployments: what 'zero' actually requires most teams don't have

Most teams say they do zero-downtime deploys and mean 'we haven't gotten a complaint in a while.' Actually measuring it reveals the truth: connection drops, in-flight request failures, and cache invalidation spikes during rollouts that nobody's tracking because nobody defined what zero means.

What 'zero downtime' actually requires:

✓ Health checks reflect REAL readiness (not just 'process started')
✓ Graceful shutdown drains in-flight requests (SIGTERM handling)
✓ Connection draining at the load balancer (not just the pod)
✓ Rollback faster than the deploy (< 5 min, automated)
✓ SLI measurement during the rollout window (not just after)

Missing any one of these = not zero downtime. Just unmonitored downtime.

The non-obvious part:
→ The most common failure mode is passing health checks before the app is actually ready — DB connections not pooled, caches not warm, background workers not started. The pod is 'Ready' and the app is still initializing. Users see errors. Nobody's dashboard shows it because nobody's measuring error rate during the rollout window.

My rule:
→ Define 'zero downtime' with a measurable SLI: error rate < 0.1% during any 5-minute deploy window. Validate this in staging before calling it done. Measure it in production on every release.

Worth reading:
▸ Kubernetes deployment strategies — rolling, blue/green, canary with traffic splitting
▸ AWS ALB / GCP Cloud Load Balancing — connection draining configuration and health check tuning

https://neeraja-portfolio-v1.vercel.app/insights/zero-downtime-deployments-what-zero-actually-requires-most-teams-dont-have

If you're a manager reading this — it's worth asking your team where they are on this.

devops #sre #observability #platformengineering

One insight that changed how I design systems:

Neeraja Khanapure — Fri, 22 May 2026 11:33:09 +0000

LinkedIn Draft — Insight (2026-05-22)

One insight that changed how I design systems:

Runbook quality decays silently — and that decay kills MTTR

Runbooks that haven't been run recently are wrong. Not outdated — wrong. The service changed. The tool was deprecated. The endpoint moved. Nobody updated the doc because nobody reads it until 3am. And at 3am, a wrong runbook is worse than no runbook — it sends engineers down confident paths that dead-end.

Runbook decay curve:

Quality
  │▓▓▓▓▓▓▓▓▓▓
  │         ▓▓▓▓▓
  │              ▓▓▓▓
  │                  ▓▓▓▓▓
  │                       ▓▓▓░░░░░░░
  │                             ░░░░░░░░ ← "last validated 8 months ago"
  └────────────────────────────────────▶
  Write   Month 1  Month 3  Month 6  Month 9

The non-obvious part:
→ The highest-leverage runbook improvement isn't better writing — it's a validation date and a quarterly review reminder. A runbook with 'last validated: 2 weeks ago' that's 70% accurate is worth more than a beautifully written one from 8 months ago that's 40% accurate.

My rule:
→ Every runbook gets a 'last validated' date. Anything older than 3 months is assumed broken until proven otherwise. Review is part of the on-call rotation, not optional.

Worth reading:
▸ PagerDuty Incident Response guide — runbook standards and validation cadence
▸ Post-incident review template: 'Did the runbook help, mislead, or was it missing?' (standard question)

https://neeraja-portfolio-v1.vercel.app/insights/runbook-quality-decays-silently-and-that-decay-kills-mttr

What's the version of this that your org gets wrong? Drop it below.

devops #sre #observability #platformengineering

A hard-earned rule from incident retrospectives:

Neeraja Khanapure — Tue, 19 May 2026 11:42:11 +0000

LinkedIn Draft — Workflow (2026-05-19)

A hard-earned rule from incident retrospectives:

Incident RCA without a data-backed timeline is just a story you told yourself

Most post-mortems produce lessons that don't stick. The root cause is almost always the same: the timeline was built from memory, not from data.

Memory-based timeline:     Data-backed timeline:

T+0  "Deploy happened"     T+0:00  Deploy (Argo event)
T+?  "Errors started"      T+0:07  Error rate +0.3% (Prometheus)
T+?  "Someone noticed"     T+0:12  P95 latency 340ms→2.1s (trace)
T+?  "We rolled back"      T+0:19  Alert fired (PD)
                           T+0:31  Rollback complete (Argo)

Where it breaks:
▸ Log timestamps across services diverge by seconds without NTP — your timeline is wrong before you begin.
▸ Correlation between a deploy event and a metric spike gets missed when dashboards lack deployment markers.
▸ Contributing factors vanish from the narrative because they're hard to prove — and the same incident repeats.

The rule I keep coming back to:
→ Build the timeline from data only before the RCA meeting begins. If you can't source an event, mark it 'unverified' — not assumed.

How I sanity-check it:
▸ OpenTelemetry trace IDs as the timeline spine — they cross service boundaries with sub-millisecond precision.
▸ Grafana annotations on every deploy, config change, and scaling event — visible on every dashboard automatically.

Systems that are hard to debug were designed without the debugger in mind. Build observability in, not on.

Deep dive: https://neeraja-portfolio-v1.vercel.app/workflows/incident-rca-without-a-data-backed-timeline-is-just-a-story-you-told-yourself

This is where most runbooks stop — what's your next step after this?

sre #reliability #observability #devops