DCM
This content is for 0.1.0. Switch to the latest version for up-to-date documentation.
DCM on the hub supplies catalog, policy, placement, and provider registration for the experimental v0.1.0 fleet. Workloads materialize on registered clusters only after a matching provider is ready.
| FCJ provider | Workload |
|---|---|
k8s |
Kubernetes container resources |
helm |
OCI Helm releases |
kubevirt |
KubeVirt workloads on compatible prepared clusters |
These are the only FCJ provider kinds. OLM is not an FCJ provider kind.
Catalog content is optional: the hub and FCJ lifecycle do not depend on an
optional catalog checkout. When a catalog item uses secret binding, store the
sensitive value in a target-cluster Kubernetes Secret and pass a reference to
DCM instead of plaintext.
Placement, deletion, and rehydration behavior require independent validation. Do not treat catalog operations as a production workload-management guarantee.
See Provider install and Secrets and vault.