Mr.PlanB Logo
    Managed Cloud Kubernetes Ledger 2026
    Ledger
    Managed Cloud Kubernetes Ledger 2026

    Upstream Kubernetes: Cloud Kubernetes Ledger

    Upstream Kubernetes is building toward a standard scheduling and admission layer for accelerators and policy, with a release train that holds its dates.

    Edition October 13, 20266 min read

    Part of the Managed Cloud Kubernetes Ledger (edition 2026-10-13). How the scores work: methodology.

    1. Snapshot

    • Tier: Open-source engine
    • Owner: Cloud Native Computing Foundation (Linux Foundation); open-source project, no single vendor
    • Licence model: Apache-2.0; free, self-operated, no support contract
    • Products scored: Kubernetes releases 1.35 to 1.37 as shipped by the project (API, kubelet, kubeadm, reference controllers); SIG projects named in the notes
    • Latest release: v1.37.0, 2026-08-26 (v1.37.1 on 2026-09-15)
    • Next signal: v1.38.0 planned 2026-12-16
    • Archetype: Reference engine, DIY
    • Evidence grade: A. Dates come from git tags, KEP files and the release schedules read in this run; ops and accel cells for 2016 are not confirmed and carry little weight.

    2. Scorecard

    DimensionScoreDirection
    Capability today46.4 / 100higher is better
    Momentum since end of 2022+8.0 pointshigher is better
    Credibility21.5 / 25higher is better
    Commercial risknot scored (engine: nothing to buy)
    Technical lock-in0.5 / 25lower is better
    Integrator fit16.0 / 20higher is better
    AI leverage5.0 / 20higher is better
    Ledger Index65.5 / 100balanced weights

    3. Capability by domain

    Scores 0 to 5 against fixed anchors; total is weighted to 100.

    Domain (weight)201620192022Today
    Versions, upgrades and support (12)22.52.52.5
    Nodes, autoscaling and compute choice (12)11.51.52
    Networking (10)1.522.53
    Storage and data protection (8)122.53
    Security and compliance (12)1.52.533.5
    Observability and day-2 operations (8)111.52
    Multi-cluster, hybrid and fleet (10)0.511.51.5
    Developer and app platform (8)11.522
    GPU and AI workloads (10)0.51.523.5
    Regions, sovereignty and SLA (10)0000
    Total / 10020.631.838.446.4

    Year by year: 2016: 20.6 · 2017: 20.6 · 2018: 20.6 · 2019: 31.8 · 2020: 31.8 · 2021: 31.8 · 2022: 38.4 · 2023: 38.4 · 2024: 38.4 · 2025: 38.4 · 2026: 46.4

    What moved the score

    YearDomainChangePointsTrigger
    2019Developer and app platform1 → 1.5+0.8CRDs GA in 1.16 (2019-09-18)
    2019GPU and AI workloads0.5 → 1.5+2.0Device plugin API beta since 1.10
    2019Multi-cluster, hybrid and fleet0.5 → 1+1.0Cluster API repository since 2018; not part of the release
    2019Networking1.5 → 2+1.0NetworkPolicy stable since 1.7; EndpointSlice alpha in 1.16
    2019Nodes, autoscaling and compute choice1 → 1.5+1.2Windows node support production-level in 1.14 (2019-03-25)
    2019Security and compliance1.5 → 2.5+2.4RBAC stable in 1.8; Secret encryption alpha since 1.7
    2019Storage and data protection1 → 2+1.6CSI GA in 1.13, local persistent volumes GA in 1.14
    2019Versions, upgrades and support2 → 2.5+1.2kubeadm GA in 1.13 gave a documented upgrade path; still no automatic patching or long support
    2022Developer and app platform1.5 → 2+0.8Ephemeral containers and kubectl debug stable in 1.25
    2022GPU and AI workloads1.5 → 2+1.0Device plugin API stable and DRA alpha, both in 1.26
    2022Multi-cluster, hybrid and fleet1 → 1.5+1.0Cluster API v1.0.0 on 2021-10-06 as a SIG project
    2022Networking2 → 2.5+1.0EndpointSlice stable 1.21, dual-stack GA 1.23, NetworkPolicy endPort stable 1.25
    2022Observability and day-2 operations1 → 1.5+0.8Ephemeral containers stable 1.25 for debugging; structured logging beta since 1.23
    2022Security and compliance2.5 → 3+1.2Bound service account tokens stable 1.22; Pod Security Admission stable and PodSecurityPolicy removed in 1.25
    2022Storage and data protection2 → 2.5+0.8Volume snapshots GA 1.20, volume expansion stable 1.24, generic ephemeral volumes GA 1.23
    2026GPU and AI workloads2 → 3.5+3.0DRA core GA 1.34, CDI in device plugins stable 1.31, DRA device taints and extended resources stable 1.37
    2026Networking2.5 → 3+1.0nftables kube-proxy, traffic distribution and multiple service CIDRs stable in 1.33; no CNI or Gateway API in the release
    2026Nodes, autoscaling and compute choice1.5 → 2+1.2Sidecars stable 1.33, swap stable 1.34, in-place resize stable 1.35, user namespaces 1.36; still no node autoscaling
    2026Observability and day-2 operations1.5 → 2+0.8API server and kubelet tracing stable in 1.34; no managed metrics, cost allocation or upgrade insights
    2026Security and compliance3 → 3.5+1.2KMS v2 1.29, ValidatingAdmissionPolicy 1.30, MutatingAdmissionPolicy and user namespaces 1.36; no image signing or threat detection
    2026Storage and data protection2.5 → 3+0.8VolumeGroupSnapshot and OCI volume source GA in 1.36; no drivers or backup tool shipped

    4. Direction, 2023 to 2026

    Each item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

    DateItemThemeDriver
    2023-12KMS v2 stable, in-tree cloud providers off by defaultD9 SecurityC
    2024-04ValidatingAdmissionPolicy stable; DRA structured parameters alphaD9 SecurityV
    2024-08In-tree cloud provider code removed; nftables kube-proxy betaD11 Ecosystem opennessV
    2024-12DRA structured parameters beta; MutatingAdmissionPolicy alphaD13 AcceleratorsV
    2025-04Sidecar containers and nftables kube-proxy stableD2 Compute and autoscalingC
    2025-08DRA core GA; API server and kubelet tracing stable; node swap stableD13 AcceleratorsM
    2025-11Ingress NGINX retirement announcedD4 NetworkingC
    2025-12In-place pod resize stableD2 Compute and autoscalingC
    2026-04Volume group snapshots, user namespaces, OCI volumes and MutatingAdmissionPolicy stableD9 SecurityC
    2026-08DRA device taints and extended resources stableD13 AcceleratorsM
    • Centre of gravity: Security (3), Accelerators (3), Compute and autoscaling (2)
    • Driver mix: Vision 30%, Customer need 50%, Market window 20%, Upstream 0%, Portfolio 0%

    5. Credibility: 21.5 / 25

    CriterionScoreBasis
    Cadence5Three minors a year; 10 of 11 releases from 1.27 to 1.37 shipped on the date published at cycle start
    Roadmap transparency5Public KEP repository with commit history, sig-release schedules and an official CVE feed
    Say-do420 of 24 stated targets met within 12 months; 16 of 24 on the stated date; sidecars, resize, swap and group snapshots slipped over a year
    Velocity511 to 23 features reach stable in every release; 44 to 70 enhancements per release since 1.27
    Lifecycle stability2.5About 14 months per minor, no long-term support release; upgrade every minor, APIs get removed

    Say-do record, 2023 to 2026: Releases: 10 of 11 on date, 1.29 slipped 8 days. KEPs: 13 tracked, 6 on target, 7 slipped (sidecars 3 minors, in-place resize 5, node swap 4, volume group snapshot 5, OCI volume 2, user namespaces 1, KMS v2 1).

    6. Commercial risk: not scored

    This is an open-source engine: nobody sells it, so there are no commercial terms to score. Its project health is described below.

    Security record of the product itself: None: upstream is not a managed service. Official CVE feed lists 94 items, none in CISA KEV (catalogue 2026.10.08). Latest: CVE-2026-76654 on 2026-09-14.

    7. Technical lock-in: 0.5 / 25 (lower is better)

    CriterionScoreBasis
    Formats0The reference API; workloads use standard Kubernetes objects
    Export path0Nothing to export: runs anywhere, no egress fee, no vendor service
    Stack coupling0No provider IAM, load balancer or storage class required
    Hardware / cloud coupling0Runs on any cloud, bare metal or laptop
    Skills and tooling coupling0.5Standard kubectl; operating etcd and kubeadm yourself needs scarcer skills

    8. Integrator fit: 16.0 / 20

    CriterionScoreBasis
    Partner programme openness4.5Vendor-neutral CNCF conformance programme with 131 listed products for 1.34 and 1.35
    Multi-tenancy and self-service2.5Namespaces, RBAC and quotas only; no organisations, projects or fleet isolation
    API and infrastructure-as-code4Cluster API v1.14 and client libraries; no official Terraform provider
    Skills and certification5CKA exam offered by the Linux Foundation and the largest public documentation and community

    9. AI leverage: 5.0 / 20

    StrandTodayLatest step
    AI workload support3.52026: DRA extended resources and device taints stable 1.37; agent-sandbox 1.0.0 on 2026-08-28
    AI platform stack0none
    AI-assisted operations02023: The project ships no assistant; k8sgpt and kubectl-ai are third-party
    Agent openness1.52016: Documented REST API; no official MCP server (the draft's kubernetes-sigs repository does not exist)

    AI say-do: 3 tracked, 2 GA, 1 pending (DRA consumable capacity slipped from 1.36 to 1.38). The project supplies scheduling primitives for GPUs; it has no assistant and no official MCP server.

    10. Reading

    Upstream Kubernetes is building toward a standard scheduling and admission layer for accelerators and policy, with a release train that holds its dates. The record shows reliable releases and features that often take two to five extra minors to reach stable. A buyer gets full portability and no fee, and pays with operations: no hosted control plane, no node provisioning, 14 months of support.

    11. Open questions and evidence caveats

    • Ops 2016 and accel 2016 cells are not confirmed in the research; both carry low scores with little effect.
    • Cluster API, Kueue, JobSet and Gateway API are SIG projects outside the release; Cluster API is credited in fleet, the others only in AI infra.
    • No official MCP server was found; community servers do not count under the rubric.
    • CVE severity is missing for many feed items; the feed gives CVSS only for some entries.

    More from Managed Cloud Kubernetes Ledger 2026