Blog

Notes on what we ship, why we shipped it that way, and the small operational lessons that shape kpulse.

Posts

• Why kpulse exists — the gap between "I just kubectl applied my first thing" and "I have Prometheus, Grafana, and Alertmanager on call".
• The 12 default monitors, and why those thresholds — a reasoned tour of every default kpulse ships with.
• Resolved alerts: the missing half of alerting — why a notification that fires once and then goes silent is half a feature.
• Local-only dev with Tilt: changing kpulse without a release — how the contributor loop works, and why we didn't pick a registry pattern.