You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ When an alert fires, one command should tell you everything: what's failing (fro
4
4
5
5
80% of Kubernetes outages trace to recent changes ([Komodor, 2025](https://komodor.com/blog/komodor-2025-enterprise-kubernetes-report-finds-nearly-80-of-production-outages/)). Yet today, finding them is a slog. Kubectl events expire in an hour. ArgoCD shows syncs, not details. Slack becomes your search engine. Forty-five minutes later: someone found a ConfigMap edit.
6
6
7
-
Our first release fills a gap: a unified change timeline across every resource type—images, ConfigMaps, Secrets, RBAC, HPA, NetworkPolicy, env vars, node events—in a single command. No open-source CLI has this today.
7
+
Our first release fills a gap: a unified change timeline across common Kubernetes resource types—images, ConfigMaps, Secrets, RBAC, HPA, NetworkPolicy, env vars, node events—in a single command. No open-source CLI has this today.
8
8
9
9
<!-- TODO: demo GIF -->
10
10
<!--  -->
@@ -29,7 +29,7 @@ Here's how we're building toward the full vision:
29
29
30
30
| Version | Functionality | Status |
31
31
|---------|---------|--------|
32
-
|**V1**| What changed — unified change timeline across all resource types | Current |
32
+
|**V1**| What changed — unified change timeline across common Kubernetes resource types | Current |
0 commit comments