Elemental 3 Parity: Status

As of Nov 18, 2026 05:02 UTC. Started Nov 12, 2026. Work is done by software agents; every result is checked against its evidence before it is recorded.

Day 7
since work started on Nov 12, 2026
17 of 52
plan tasks proven in the lab and in review
6
more tasks in progress
41
task results recorded, each checked against its evidence

What "parity" means here

Parity means a Rancher user can deploy, manage and upgrade an Elemental 3 cluster with an experience equal to or better than each solution it replaces. It is measured, not asserted.

Milestones: plan against actual

Targets are the estimates made before work began. Later milestones will be re-estimated from the measured pace.

WaveGoalTargetStatusNotes
W0Scorecard live; legacy baselines measured; Harvester migration spike startedNov 18, 2026 Met
Nov 13 (5 days ahead of target)
Scorecard and both legacy baselines measured by day 2.
W1Create, scale and upgrade an Elemental 3 cluster on Harvester through the APIDec 2, 2026 Shown in the lab
Nov 17 (15 days ahead of target)
Measured end to end by the harness on a 3 + 2 cluster. Still uses lab workarounds for the Harvester provider.
W2Same flow in the Rancher UI with tenancyDec 23, 2026 Under wayCreate wizard works for a tenant (day 6). Tenant can create, see, scale and delete their cluster with prototype roles (day 7). Upgrade UI and cluster detail are in progress.
W3Bare metal: registration, inventory, in-place upgradeto be re-estimated Not startedNot started.
W4AWS, Azure, GCP, vSphere; upgrade by replacement; air-gap; migrationto be re-estimated Under wayUpgrade by replacement shown on Harvester (day 6). Other targets not started.
W5Harvester itself on Elemental 3, with in-place migrationto be re-estimated Under wayThree-node rolling migration prototype with live guest and rollback ran on day 2.

Activity by task

All 52 plan tasks and their status, including those not started.

Proven in the lab, in review In progress Each dot is one verified result committed with its evidence (41 shown; hover for details). 18 of 52 plan tasks have activity.
Nov 12 day 1 Nov 13 day 2 Nov 14 day 3 Nov 15 day 4 Nov 16 day 5 Nov 17 day 6 Nov 18 day 7 now Baselines and scorecard T0.1 Audit of the public repositories T0.1 · Nov 12 16:57Z · T0.1: public repo audit; plan corrections and new blockers done T0.3 Journey harness and scorecard T0.3 · Nov 12 17:21Z · T0.3: journey harness, scorecard and first provisioning v2 results T0.3 · Nov 12 21:00Z · T0.3: first passing provisioning v2 create run on 1x1; scale and upgrade not yet passing T0.3 · Nov 13 00:20Z · T0.3: legacy baseline measured for 1x1 (all three journeys) and 3x2 create T0.3 · Nov 13 03:22Z · T0.3: 3x2 legacy baseline measured; scorecard and task board updated T0.3 · Nov 17 23:03Z · T0.3: Elemental 3 harness driver; scale and upgrade measured on 3 + 2 T0.3 · Nov 18 02:34Z · T0.3: two clean Elemental 3 create samples on 3 + 2 (27m03s, 27m13s; legacy 25m30s) proven in lab, in review T0.4 Elemental 2 baseline T0.4 · Nov 13 09:20Z · T0.4: Elemental 2 baseline at 1x1; elemental2 harness driver; scorecard T0.4 · Nov 13 09:22Z · T0.4: 3x2 Elemental 2 run deferred on capacity; diagnostics added to the driver T0.4 · Nov 13 15:58Z · T0.4: 3x2 Elemental 2 run stopped by lab storage limit; storage budget rule T0.4 · Nov 13 20:40Z · T0.4: Elemental 2 at 3x2; fix upgrade completion check in both drivers T0.4 · Nov 13 23:42Z · T0.4: Elemental 2 at 3x2 final; OS upgrade fails on the 900 s job deadline T0.4 · Nov 14 04:18Z · T0.4: Elemental 2 OS upgrade with 4 vCPU / 16 GiB control planes in progress Images T1.1 Elemental 3 image boots on Harvester T1.1 · Nov 12 20:54Z · T1.1 spike: Elemental 3 main boots on Harvester with boot-time config proven in lab, in review T1.3 Prebuilt image path (no build for a first cluster) T1.3 · Nov 16 22:11Z · T1.3: prebuilt image pipeline; first cluster on Harvester with no build (lab) proven in lab, in review T1.4 One generic image for all node roles T1.4 · Nov 16 23:15Z · T1.4: generic CAPI-ready image; one image serves 3 control plane + 2 workers (lab) proven in lab, in review T1.5 Image build operator T1.5 · Nov 17 04:03Z · T1.5: image build operator; request to usable Harvester image with no manual step (lab) proven in lab, in review T1.6 Image build without a privileged container T1.6 · Nov 17 06:01Z · T1.6: image build needs no privileged container; pod builder beside the VM builder (lab) T1.6 · Nov 17 18:17Z · T1.6: pod builder proof on the Rancher management cluster proven in lab, in review Cluster provisioning T2.2 Cluster on Harvester, with and without Rancher T2.2 · Nov 13 00:05Z · T2.2: Cluster API cluster of Elemental 3 nodes on Harvester, imported into Rancher (works with shims) T2.2 · Nov 18 00:54Z · T2.2: full lifecycle from a management cluster with no Rancher (Cluster API alone) T2.2 · Nov 18 03:34Z · T2.2: Rancher-free create with a direct Harvester credential (17m46s, zero packets to Rancher) proven in lab, in review T2.6 Boot-time configuration (cloud-init) T2.6 · Nov 12 21:19Z · T2.6: cloud-init via yip design, prototype branch reference and lab proof proven in lab, in review Upgrade T3.2 Upgrade driven from Rancher T3.2 · Nov 13 01:38Z · T3.2: in-place LCM run on the imported cluster, triggered from the Rancher side T3.2 · Nov 13 16:43Z · T3.2 round 2: real version upgrade and power-cut injection; gaps G1-G13 in progress T3.3 Lifecycle manager hardening T3.3 · Nov 13 04:31Z · T3.3: three lifecycle manager upgrade-time fixes on the fork; report T3.3 · Nov 13 15:16Z · T3.3: release marker commits on both forks; report updated T3.3 · Nov 13 17:12Z · T3.3: deadline, failure reporting, retry and interrupted-upgrade fixes on the forks T3.3 · Nov 13 17:31Z · T3.3: fix series rebased on upstream main as -v2; lab build recipe T3.3 · Nov 14 01:36Z · T3.3: fix series validated on a 3+2 cluster; 10 of 11 commits confirmed T3.3 · Nov 14 06:46Z · T3.3: clean hands-off upgrade on 3+2 takes 2h14m; chart downgrade stalls the worker phase T3.3 · Nov 14 19:44Z · T3.3: G5 fixed in the lifecycle manager; hands-off 3+2 upgrade in 72m55s T3.3 · Nov 17 03:57Z · T3.3: upgrade on a cluster Rancher does not manage (runs G and H) in progress T3.4 Upgrade by node replacement T3.4 · Nov 17 23:05Z · T3.4: upgrade by replacement on 3 + 2 (54m39s); zero-downtime not met (API gaps up to 27 s) proven in lab, in review Rancher UI T4.1 Create-cluster wizard in Rancher T4.1 · Nov 18 00:19Z · T4.1: Elemental 3 create-cluster wizard in Rancher; tenant created a real 1 + 1 (12 interactions vs 18 legacy) proven in lab, in review T4.2 Upgrade UI in progress T4.4 Cluster detail and scaling UI in progress Harvester T6.4 Harvester in-place migration (design and prototype) T6.4 · Nov 12 16:39Z · T6.4: Harvester in-place migration design spike (first pass) T6.4 · Nov 13 00:58Z · T6.4: in-place migration prototype results (partial) T6.4 · Nov 13 03:22Z · T6.4 round 2: clean unattended single-node migration run; 3x2 legacy baseline results T6.4 · Nov 13 08:44Z · T6.4 round 3: rolling three-node Harvester migration with live guest, rollback and Secure Boot proven in lab, in review T6.5 Harvester host image on Elemental 3 T6.5 · Nov 13 15:16Z · T6.5 first slice: Harvester host extension image; migration proof without borrowed tools T6.5 · Nov 13 18:51Z · T6.5: three-node rolling migration onto the host image with enforcing trial boots in progress

Measured so far

Same cluster shape (3 control plane + 2 workers, 2 vCPU), same harness, x86-64, lab conditions. Mostly single samples.

JourneyRancher provisioning v2Elemental 2Elemental 3
Create a cluster: user steps1886
Create a cluster: time25 min 30 s42 min 15 s27 min 03 s
Create in the Rancher UI: interactions18not measured12
Upgrade Kubernetes only24 min 29 s36 min 45 spart of the combined upgrade
Upgrade OS and Kubernetes as one actionnot offeredfails (node left cordoned)90 min in place; 55 min by replacement
Works with no Rancher at allnonoyes: create, scale, upgrade, delete

Known gaps