Skip to content

Install providers

This content is for 0.1.0. Switch to the latest version for up-to-date documentation.

After an FCJ reaches Ready, use its authenticated cluster detail flow to install only the provider needed by the workload:

Provider Role
k8s Container Deployments/Services via k8s-container-service-provider
helm Helm charts from Harbor OCI via fleet-helm-release-sp
kubevirt KubeVirt workloads via kubevirt-service-provider

k8s, helm, and kubevirt are the only FCJ provider kinds in v0.1.0. KubeVirt also requires compatible host preparation. A provider must report Ready before DCM can materialize a matching workload. OLM platform resources are not an FCJ provider kind.

See Provider install lifecycle and DCM.