Deploy first app
Console path
Section titled “Console path”Catalog → Deploy wizard: Template → Configure → Placement → Review.
- Creates a catalog-item-instance on the DCM gateway (
POST /api/v1alpha1/catalog-item-instances). - Password fields with
x-secret-bindare written to the spoke first (PUT /fleet/api/v1alpha1/catalog-instance-secrets); DCM only storesexistingSecretrefs. - DCM evaluates Rego placement policies against
ManagedClusterlabels. - The matching service provider materializes the workload on placed clusters.
fleet-edge-route-synccreates/updates aFleetAppRoutewhenrouting.modeishub,site, ordual.fleet-edge-controllerprograms hub Traefik fragments and spoke Ingress ManifestWorks.
Demo catalog items (for example demo-webapp, whoami-helm) are seeded at hub install. Re-seed:
ansible-playbook $INV fleet-dcm.yml -l hub -t dcm_seed_catalogFor hub-routed apps, ensure wildcard DNS for fleet_edge_domain points at the hub WAN IP.
Deep dive: App deploy and routes.