Deploy first app
This content is for 0.1.0. Switch to the latest version for up-to-date documentation.
Catalog deployment is optional; it is not required for hub installation or the FCJ lifecycle. In an authenticated console session, select catalog content, choose placement inputs, and submit the instance.
DCM evaluates placement policies against eligible ManagedCluster labels. A
ready matching provider materializes the workload on the selected cluster:
| Workload | FCJ provider |
|---|---|
| Kubernetes container resources | k8s |
| OCI Helm chart | helm |
| KubeVirt workload | kubevirt |
Sensitive catalog fields marked for secret binding are written to a spoke
Kubernetes Secret; DCM receives only a reference. Never place workload
credentials in catalog values, URLs, or source control.
When routing is configured, route sync creates a FleetAppRoute and
fleet-edge reconciles it. Public exposure, DNS, and certificate handling remain
operator responsibilities and are experimental in this release.
See App deploy and routes and fleet-edge.