Forklift Operator installs a suite of migration tools that facilitate the migration of VM workloads to OpenShift Virtualization or KubeVirt.
OpenShift Virtualization/KubeVirt is required and must be installed prior attempting to deploy Forklift, see the table below for supported configurations:
Forklift release | OpenShift Virtualization/KubeVirt | VMware | oVirt |
---|---|---|---|
v2.2 | v4.9 | 6.5+ | 4.4.9+ |
v2.3 | v4.10+ | 6.5+ | 4.4.9+ |
Note: Please keep in mind Forklift will not deploy in unsupported configurations.
The operator will install all the necessary components which Forklift needs to operate. The projects and a description of each are detailed below:
See development.md for details in how to contribute to Forklift operator.
The method used for these instructions relies on OKD/OCP Web Console, it is also possible to automate the deployment in OpenShift using manifests if needed, please check the k8s deployment manifest for details.
Released (or public betas) of Forklift are installable via community operators which appear in OCP and OKD marketplace.
Installing latest is almost an identical procedure to released versions but requires creating a new catalog source.
oc create -f forklift-operator-catalog.yaml
Note: Installing latest may also include OLM channels for other released versions.
Once you have successfully installed the operator, proceed to deploy components by creating the ForkliftController CR.
Once the CR is created, the operator will deploy the controller, UI and configure the rest of required components.
See k8s.md for details.
Custom deployment settings can be applied by editing the ForkliftController
CR.
oc edit forkliftcontroller -n konveyor-forklift
Use the Forklift cleanup script, this is the recommended method to delete operator, CRDs and all related objects. It supports OpenShift and Kubernetes environments.
forklift-cleanup.sh -o
See the Forklift Documentation for detailed installation instructions as well as how to use Forklift.