Verification register Compute & Web Infra
Current reading
Readiness band and full integer triple
AI-assisted assembly · derived results
Readiness band
Mature
Primary summary from verified readiness
- Confidence
- 59% · fresh
- Computed at
- 2026-08-20T10:56:23.21572+00:00
- Claimed
- 90
- Reported
- 86
- Verified
- 77
- Gap
- +13
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed leads verified
Evidence strength Critical
Decision
What the current evidence supports
Human editorial judgment · 2026-08-20
Adopt with guardrails
- Why
- Gateway API is GA and is Kubernetes' own explicitly designated Ingress successor (confirmed by ingress-nginx's 2026 retirement/archival), with broad cross-vendor conformant coverage — but conformance gaps for specific vendors and the recency of some GA resources warrant verifying the chosen implementation's conformance tier rather than assuming uniform behavior.
- Next
- Standardize new Kubernetes ingress/routing work on Gateway API (HTTPRoute) via a fully 'Conformant' implementation (e.g., GKE, Istio, Cilium, NGINX Gateway Fabric, Traefik); verify each vendor's conformance tier before depending on newer resources (TCPRoute/UDPRoute, BackendTLSPolicy) or on controllers still only 'Partially Conformant' (AWS ALB Controller, EKS, Envoy Gateway, Gloo Gateway); prioritize migrating any remaining ingress-nginx deployments, since that project is now archived.
Constraints
Blockers
No named blocker is present in the current public projection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 5
- Tier 1
- 0
- Tier 2
- 0
- Tier 3
- 5
- Supports
- 4
- Contradicts
- 1
- Context
- 0
- Latest observed
- 2026-08-20
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Initial public reading
- 2026-08-20 Reading moved from mature to mature.