fleet-site
This content is for 0.1.0. Switch to the latest version for up-to-date documentation.
The fleet-site controller owns fleet.umkim.com/v1alpha1 resources for
registry sites, FCJ lifecycle, and selected optional features.
| Resource | Purpose |
|---|---|
FleetSite |
Workload-site registry metadata |
FleetClusterJoin |
Bootstrap, validate, and provision a workload cluster |
FleetAcme / FleetIngressAuth |
Optional certificate and ingress-auth configuration |
FleetLLM |
Optional hub LLM configuration |
FleetInstanceBackup / FleetInstanceRestore |
Experimental backup and restore requests |
Mutating fleet-site calls must pass through the authenticated console proxy or
an authorized service path. Do not send or forge X-Fleet-Subject-*
headers: those are internal identity assertions added by the trusted auth
proxy.
FCJ bootstrap bundles contain sensitive credentials and may be obtained only through the authenticated workflow. See Cluster join and Multi-tenancy.