2026.01.0 Release Notes
Released on March 21, 2026.
Highlights
- GA provider surface is now explicitly documented as
openstack,vmware,baremetal, andkind. vmwareis the canonical provider name in CLI help and docs;vsphereremains a compatibility alias for existing configs.- Infrastructure drift detection now covers OpenStack and VMware.
- The default test lane is documented as a deterministic GA gate, with separate property, integration, and perf lanes.
- The CLI command reference has been refreshed from the live Cobra command tree.
GA Support Boundary
| Area | Status | Notes |
|---|---|---|
| OpenStack | GA | Most complete production automation path |
| VMware | GA | Pre-provisioned VMs; drift detection is detect-only |
| Baremetal | GA | Pre-provisioned Linux hosts; no hardware provisioning or drift backend |
| Kind | GA for local/dev | Development and CI provider only |
| AWS infrastructure provider | Non-GA | AWS-backed service integrations remain supported where already used |
Important Changes
- User-facing provider help no longer advertises AWS, GCP, or Azure as supported infrastructure providers.
opencenter cluster driftregisters only OpenStack and VMware backends.- Shell integration and completion commands are now included in the maintained CLI reference.
- Kind documentation now includes
KIND_EXPERIMENTAL_PROVIDERfor Podman-based local environments.
Known Limitations
- VMware reconciliation is manual-only; drift detection reports differences but does not mutate vSphere resources.
- Baremetal does not provision hardware or operating systems and has no cloud-resource drift backend.
- Windows worker-node content is informational only and is not part of the GA support commitment.
- Keycloak backup durability remains operator-owned; protect and test the backing PostgreSQL restore path separately.
Upgrade Notes
- Prefer
vmwarein all new configurations and examples. Existingvspherevalues still load. - Use
mise run testfor the deterministic default gate. - Run
mise run property,mise run integration, andmise run perfseparately when you want the broader non-default coverage lanes.