Deploy first app
There is no placement engine. Pick a Ready cluster (optionally filter with console capability chips or umkim cluster candidates --require …), then install:
- Console Apps → Install chart (library picker), or
- Authenticated
POST /fleet/api/v1alpha1/appswithclusterNameandchart, or umkim chart addthen create the FleetApp from the console/API, orplaybooks/flows/app-install.ymlwithfleet_flow_cluster_nameandfleet_flow_chart.
Publish additional charts with Apps → Add chart, umkim chart add, or scripts/fleet-chart.sh. Harbor publishes whoami at oci://<hub-overlay>:30443/charts/whoami after hub install.
route.mode defaults to none. Match routing to site edge:
| Mode | Result | Hub required for public URL? |
|---|---|---|
hub |
Hub gateway routes to the selected workload cluster | Yes (hubGateway on the site) |
site |
Bound site ingress exposes siteHost (port_forward / reverse_proxy) |
No |
none |
Chart or workload owns ingress; no FleetAppRoute |
No |
Supply Helm values that contain passwords through valuesYaml only over the authenticated console or API. Do not place application credentials in commands or API examples.
Hub-routed apps require a healthy hub. site and none apps can remain reachable when the hub is down if site ingress is healthy.
Verify workload health, storage, authentication, DNS, TLS, and external reachability independently. See app deployment and FleetApp for the full lifecycle.