All plan tasks
As of Nov 18, 2026 04:42 UTC. 52 tasks: 1 done · 16 proven in lab, in review · 6 in progress · 29 not started. Back to the summary.
Baselines and scorecard · 3 of 5 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T0.1 | Public repo audit on `main`: `SUSE/elemental`, `SUSE/elemental-lifecycle-manager`, `rancher/elemental-operator`, `rancher/elemental-ui`, `rancher/elemental-channels`, `rancher/turtles`, CAPRKE2, Harvester repos; open PRs and issues that overlap this plan | Done | Written findings; overlapping work linked to task IDs so nothing is built twice | Nov 12: public repo audit; plan corrections and new blockers |
| T0.2 | `parity/matrix.yaml`: every user journey × baseline × target, with legacy step count and expected result | Proven in lab, in review | Owner approves the journey list | Nov 12: parity matrix draft (52 journeys) for owner review |
| T0.3 | Journey harness: scripted Rancher API + UI (Playwright) runs recording steps, wall time, pass/fail | Proven in lab, in review | Runs green against provisioning v2 on Harvester | Nov 18: two clean Elemental 3 create samples on 3 + 2 (27m03s, 27m13s; legacy 25m30s) |
| T0.4 | Legacy baselines measured for all four baselines | In progress | Numbers committed, reproducible from one command | Nov 14: Elemental 2 OS upgrade with 4 vCPU / 16 GiB control planes |
| T0.5 | Scorecard page generated nightly from harness results | Not started | Published; red/green per row |
Images · 5 of 6 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T1.1 | Output types beyond `iso` and `raw`: qcow2, VMDK/OVA, AMI, Azure VHD, GCE image, PXE artifacts | Proven in lab, in review | Each boots on its target in CI | Nov 12: Elemental 3 main boots on Harvester with boot-time config |
| T1.2 | Per-platform enablement: Ignition platform IDs, guest agents (qemu-guest-agent, open-vm-tools) as systemd extensions | Not started | Node reports IP and readiness to its platform | |
| T1.3 | Prebuilt fast path: pipeline publishes signed tier 2 images per target for each Core Platform release | Proven in lab, in review | A first cluster on Harvester needs no build | Nov 16: prebuilt image pipeline; first cluster on Harvester with no build (lab) |
| T1.4 | Generic CAPI-ready image: `split` mode, no baked node role or network; all per-node config arrives at boot | Proven in lab, in review | Same image used for server and agent nodes | Nov 16: generic CAPI-ready image; one image serves 3 control plane + 2 workers (lab) |
| T1.5 | Image build operator: CRD requesting (release, target, config) → `elemental3 customize` job → delivered to target; cache by digest | Proven in lab, in review | Solution release requested in Rancher becomes a usable Harvester image with no manual step; second request is a cache hit | Nov 17: image build operator; request to usable Harvester image with no manual step (lab) |
| T1.6 | Unprivileged or contained builds | Proven in lab, in review | Build job runs without host-level privileges, or in an isolated builder documented as such | Nov 17: pod builder proof on the Rancher management cluster |
Cluster provisioning · 4 of 6 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T2.1 | Bootstrap contract: CAPRKE2 Ignition output consumed natively by Elemental 3; remove the manual Butane and kernel-parameter steps | Proven in lab, in review | CAPM3 cookbook example works with zero hand edits | |
| T2.2 | ClusterClass per target (Harvester, Metal3, AWS, Azure, GCP, vSphere), parameterised by Elemental release | Proven in lab, in review | `kubectl apply` of one Cluster object yields a ready cluster | Nov 18: Rancher-free create with a direct Harvester credential (17m46s, zero packets to Rancher) |
| T2.3 | Auto-import into Rancher with agents, projects, RBAC working | Proven in lab, in review | Cluster shows Active in Rancher with no manual import | |
| T2.4 | Manage operations mapped: scale, remediation (MachineHealthCheck), etcd snapshot/restore, cert rotation | Not started | Each WS0 Manage journey passes | |
| T2.5 | Compatibility with Turtles current and next minor (v1beta2 contract) | Not started | CI matrix green on both | |
| T2.6 | cloud-init support in Elemental 3 through yip, reusing elemental-toolkit work where possible; coexists with Ignition | Proven in lab, in review | A cloud-config supplied as NoCloud or ConfigDrive user-data configures an Elemental 3 node at first boot; CAPHV and Harvester node configuration work unmodified | Nov 12: cloud-init via yip design, prototype branch reference and lab proof |
Upgrade · 2 of 6 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T3.1 | Release catalog on the management cluster: manifest sources, discovered tier 2/3 releases, valid upgrade paths per cluster | Proven in lab, in review | New release appears without operator action; invalid jumps are not offered | |
| T3.2 | Rancher-driven upgrade: LCM present in every Elemental 3 cluster by default; management controller sets the downstream `Release` and mirrors its status | In progress | Picking a release in the management cluster upgrades a 3+3 Harvester guest cluster with no `kubectl` on the downstream | Nov 13: real version upgrade and power-cut injection; gaps G1-G13 |
| T3.3 | LCM hardening: health-gated progress, concurrency control, fix early status.version, component config outside upgrades. Release rollback/downgrade out of scope (owner 2026-11-12) | In progress | Injected node failure stops the upgrade, the failed OS transaction rolls back via Elemental snapshots, and the cluster stays healthy | Nov 17: upgrade on a cluster Rancher does not manage (runs G and H) |
| T3.4 | Rolling-replace option for VM and cloud: CAPI rollout to an image of the new release (from T1.5) | Proven in lab, in review | Zero-downtime upgrade by replacement; user chooses strategy per cluster | Nov 17: upgrade by replacement on 3 + 2 (54m39s); zero-downtime not met (API gaps up to 27 s) |
| T3.5 | Pre-flight checks and progress reporting (conditions, events, phase, percent) exposed for the UI | Not started | Harness reads progress through the management API only | |
| T3.6 | API maturity: `Release` to v1beta1, manifest schema v1, conversion tested | Not started | Upgrade across the schema change tested |
Rancher UI · 1 of 5 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T4.1 | UI extension: create-cluster wizard per target, matching provisioning v2 screens field for field where concepts overlap | Proven in lab, in review | Step count ≤ provisioning v2 for the same cluster | Nov 18: Elemental 3 create-cluster wizard in Rancher; tenant created a real 1 + 1 (12 interactions vs 18 legacy) |
| T4.2 | Release picker and one-click upgrade with pre-flight result, progress, and rollback | In progress | Upgrade journey ≤ legacy steps; shows OS + RKE2 + apps as one version | Nov 18: owner-approved owner binding for the UI test cluster (orchestrator shim log) |
| T4.3 | Bare-metal views: registration endpoints, inventory, select hosts into a cluster | Not started | Elemental 2 users complete the flow without docs | |
| T4.4 | Cluster detail parity: machine pools, conditions, events, snapshots | In progress | All Manage journeys doable from UI | |
| T4.5 | Appears in Cluster Management next to existing provisioners, not in a separate area | Not started | UX review sign-off |
Bare metal · 0 of 5 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T5.1 | Registration service and inventory on Elemental 3: registration URL, seed/installer ISO, TPM-based identity, labels | Not started | Host boots ISO and appears in inventory | |
| T5.2 | Inventory → CAPI infrastructure provider (hosts selected by label into clusters) | Not started | Cluster built from inventory hosts | |
| T5.3 | Metal3 directed provisioning with Elemental 3 images | Not started | Edge "directed network provisioning" journey passes | |
| T5.4 | Disk encryption (#627), reset/re-provision, node decommission | Not started | Journeys pass | |
| T5.5 | Edge Image Builder equivalence: document and automate the EIB → `elemental3 customize` mapping | Not started | An EIB definition converts and builds |
Harvester · 2 of 8 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T6.1 | Target: Harvester CAPI provider ClusterClass; image auto-upload to Harvester; Harvester cloud provider and CSI as solution charts | Proven in lab, in review | Guest cluster with load balancer and PVCs working | |
| T6.2 | Tenancy: provisioning scoped by Rancher project and Harvester namespace, quotas respected, per-tenant credentials | Not started | Tenant A cannot see or use tenant B resources; quota breach is refused cleanly | |
| T6.3 | Parity with the Harvester node driver experience from Rancher (Virtualization Management → create cluster) | Not started | Step count ≤ node driver path | |
| T6.4 | Migration design spike: compare the Elemental 1 on-disk layout and configuration used by Harvester (partitions, active/passive images, cloud-init config) with Elemental 3 (btrfs snapshots, Ignition); choose an in-place conversion approach | Proven in lab, in review | Written design reviewed by the Harvester team; prototype converts one node in a VM with data intact | Nov 13: rolling three-node Harvester migration with live guest, rollback and Secure Boot |
| T6.5 | Harvester as a tier 3 solution manifest on SLES 16.1: host dependencies as systemd extensions, installer for new installs | In progress | New Harvester cluster installs from an Elemental 3 image and runs a VM | Nov 13: three-node rolling migration onto the host image with enforcing trial boots |
| T6.6 | In-place migration delivered through Harvester's existing upgrade flow: node by node, VMs live-migrate, persistent data and settings preserved, rollback if a node fails | Not started | A 3-node Harvester cluster on the current Micro 6.x release reaches the Elemental 3 release from the normal upgrade UI, with running VMs and no reinstall | |
| T6.7 | After migration, Harvester upgrades through LCM and the release catalog like any other solution | Not started | Next upgrade is a release pick | |
| T6.8 | Harvester host operations on Elemental 3: add a node, put a node into maintenance, remove a node (journey J-MANAGE-11; owner ruling Q10, 2026-11-18) | Not started | J-MANAGE-11 passes with step count <= Harvester's own flow |
Clouds and vSphere · 0 of 4 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T7.1 | AWS: published AMIs, CAPA ClusterClass, cloud credentials reused from Rancher | Not started | Deploy/manage/upgrade journeys pass | |
| T7.2 | Azure and GCP, same shape | Not started | Same | |
| T7.3 | vSphere: OVA template publishing, CAPV ClusterClass | Not started | Same | |
| T7.4 | Cloud provider / CSI charts per platform in the solution manifests | Not started | Load balancer and storage work |
Air-gap, migration, docs · 0 of 3 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T8.1 | Air-gap: mirrored registry bundle per release; all journeys with no internet | Not started | Harness passes in an isolated network | |
| T8.2 | Migration tooling: provisioning v2, Elemental 2, and Edge clusters → Elemental 3 (rolling node replacement into the new model) | Not started | One cluster of each type migrated with workloads up | |
| T8.3 | Product docs, quick starts per target, and the parity report for stakeholders | Not started | Docs reviewed; a new user completes a quick start unaided |
Quality gates · 0 of 4 proven in the lab
| Task | Deliverable | Status | Passes when | Latest result |
|---|---|---|---|---|
| T9.1 | Fix adoption blockers: SELinux with Cilium (#529), local-path (#480), HelmChartConfig (#570), manifest isolation (#516) | Not started | Issues closed with regression tests | |
| T9.2 | Nightly e2e matrix: target × release × journey | Not started | Dashboard feeds the scorecard | |
| T9.3 | Upgrade matrix: N-1 → N, skip attempts, mid-upgrade failures | Not started | All handled or refused cleanly | |
| T9.4 | Scale test: 100+ downstream clusters, 500+ inventory hosts | Not started | No degradation versus Elemental 2 |