pragma.vision Your technology observatory

Verification register Compute & Web Infra

Readiness verdict

Cilium / Hubble

A dated reading of what is claimed, reported, and independently verified in the current evidence.

As of
2026-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
95

Public ambition and stated capability

Reported
93

Observed practitioner reporting

Verified
85

Independently supported evidence

Gap
+10

Claimed minus verified

Evidence strength Critical

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Adopt with guardrails

Why
CNCF-graduated, well over 100 production orgs and major enterprises; the main cautions (datapath overhead, K8s-only scope, short default retention) are well-understood and manageable with tuning.
Next
Enable Cilium as CNI with kube-proxy replacement and turn on Hubble with flow export to an existing sink; tune monitorAggregation + event-buffer size, scope L7 visibility to critical namespaces, and budget agent/relay memory.

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
7
Tier 1
1
Tier 2
3
Tier 3
3
Supports
4
Contradicts
2
Context
1
Latest observed
2026-06-25

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revisions

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.