Harvester seems to be a Talos-like immutable OS. It runs K8S with Longhorn for local dynamic storage allocation and Kubevirt for running VMs in the K8S cluster (or maybe the other way around?)
Reason for assessing (What problem is it solving?):
It caters to companies that try to lift and shift from legacy on-premises VMs. They'd be able to keep running their VMs in Harvester while migrating services to K8S one by one
Research tasks:
Figure out how it actually works and how it differs from Talos.
Would it be a fit for our on-premises legacy customers (Siemens, Terma etc)?
Prerequisite:
Bare metal or cloud VM with support for nested virtualization (most modern systems)
https://harvesterhci.io/
Harvester seems to be a Talos-like immutable OS. It runs K8S with Longhorn for local dynamic storage allocation and Kubevirt for running VMs in the K8S cluster (or maybe the other way around?)
Reason for assessing (What problem is it solving?): It caters to companies that try to lift and shift from legacy on-premises VMs. They'd be able to keep running their VMs in Harvester while migrating services to K8S one by one
Research tasks:
Prerequisite:
Starting litterature
┆Issue is synchronized with this Trello card by Unito