Skip to content

docs(research): 2026-07 market & landscape pass — AI-SRE deep dive, matrix, standards, epic themes - #45

Closed
gnanirahulnutakki wants to merge 1 commit into
devfrom
docs/market-research-2026-07
Closed

docs(research): 2026-07 market & landscape pass — AI-SRE deep dive, matrix, standards, epic themes#45
gnanirahulnutakki wants to merge 1 commit into
devfrom
docs/market-research-2026-07

Conversation

@gnanirahulnutakki

Copy link
Copy Markdown
Member

What

Adds docs/research/MARKET-RESEARCH-2026-07.md — a current (2026) competitive-and-landscape research pass to feed epic creation. Builds on the existing research set (PRs #15/#16/#17) without re-deriving it; goes deep where the prior pass was thin.

Why now

The single biggest change since the last research pass is the 2026 AI-SRE / auto-triage wave. This report characterizes it, positions Sith's Investigation Brain (PR #43) against it, and translates the findings into epic themes.

Contents

  • Competitive landscape with links + real user complaints across every category: local fleet clients (k9s/Lens/Headlamp/Aptakube/Kubevious), GitOps/action layer, fleet/platform incumbents, AI-SRE deep dive (k8sgpt, HolmesGPT, Robusta, Botkube, Komodor, Cleric), IDP/Backstage.
  • One cross-category comparison matrix across the properties that define Sith's wedges.
  • Category framing — fleet client vs AI-SRE vs GitOps action layer vs IDP; is "local-first, cross-cluster-by-default, no-account" a real wedge (yes, with evidence).
  • Standards bibliography with authoritative links: OCM, CNCF landscape, MCP 2026-07-28 spec RC (OAuth 2.1 + RFC 8707), CVE-2026-46519 (enforce-at-execution, not discovery), OpenTelemetry k8s semconv, client-go ExecCredential, SLSA/cosign/SBOM, k8s API conventions.
  • Differentiation & positioning — strongest wedge, risks/objections, what NOT to build.
  • Adversarial verification of six key claims; findings → epic themes mapped to issues E0: OCM substrate and falsification #18Sith implementation roadmap #39.

Key findings

  1. Every sampled 2026 AI-SRE tool is investigate/advise — read-only or action-gated (HolmesGPT read-only; Cleric "gated in ability to make production changes"; Komodor sandboxed-in-SaaS). The safe-action gap and the deterministic-RCA gap are both open.
  2. CVE-2026-46519 (CVSS 8.8) shows a Kubernetes MCP server enforcing controls only at discovery (tools/list), not execution (tools/call) — exactly the bug class Sith's spoke-side re-validation (E4 F4.5) structurally fixes. E7 should adopt MCP-2026 audience-bound tokens + enforce-at-execution as guardrails.
  3. k9s has declined aggregated multi-cluster three-plus times (#3374 closed not-planned, #1430, #1006/#2730); Aptakube monetizes exactly this — the OSS local-no-account cross-cluster slot is empty.

Top recommendation

Promote the Investigation Brain (currently only a spec in #43) to a numbered epic E14 with a deterministic-vs-LLM positioning contract and R1–R6 as its features.

Notes

  • Cited throughout; vendor/competitor-authored sources labelled inline and kept out of load-bearing claims.
  • One unresolved discrepancy flagged in §0: OCM core version read as v1.2.0 this pass vs v1.3.1 in prior research (addon pins v0.10.0 consistent; not load-bearing).
  • Does not merge — for review.

…atrix, standards, epic themes

Current competitive-and-landscape research feeding epic creation. Builds on the
existing research set (PRs #15/#16/#17) without re-deriving it; goes deep where the
prior pass was thin:

- AI-SRE / auto-triage category (k8sgpt, HolmesGPT, Robusta, Botkube, Komodor,
  Cleric): all investigate/advise, read-only or action-gated, LLM-agentic — the
  action gap and the deterministic-RCA gap are both open.
- One cross-category comparison matrix; category framing (fleet client vs AI-SRE
  vs GitOps action layer vs IDP).
- Standards bibliography with authoritative links: OCM, CNCF landscape, MCP
  2026-07-28 RC (OAuth 2.1 + RFC 8707), CVE-2026-46519 (enforce-at-execution),
  OTel k8s semconv, client-go ExecCredential, SLSA/cosign/SBOM, k8s API conventions.
- Differentiation/positioning, risks, what-not-to-build; adversarial verification
  of six key claims; findings mapped to epic themes referencing issues #18-#39.

Key recommendation: promote the Investigation Brain (PR #43 spec) to a numbered
epic (E14) with a deterministic-vs-LLM positioning contract.

Signed-off-by: Gnani Rahul <89947795+gnanirahulnutakki@users.noreply.github.com>
@gnanirahulnutakki

Copy link
Copy Markdown
Member Author

Closing as duplicate — superseded by #44 (same deliverable). This lane was a late-launched duplicate session; standing down.

@gnanirahulnutakki

Copy link
Copy Markdown
Member Author

Reopening to preserve this pass: the consolidated epic backlog was built on this fuller research (449 lines, with the epic-theme mapping). Keeping both #44 and #45 open for reconciliation into one canonical docs/research file at the review step — no research lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant