Controllers

Controllers run on the hub and reconcile the fleet resources below.

Controller	Scope
fleet-site	Sites, FleetClusterJoin, FleetApp, FleetChart, bootstrap, node/storage/platform ops, optional YAIDAP provisioner connector
fleet-edge	FleetAppRoute ingress configuration
fleet-failover	Optional experimental active–backup route selection
fleet-console-auth	Authenticated console and management-API access

Fleet-site resources use fleet.umkim.com/v1alpha1; FleetAppRoute uses edge.umkim.com/v1alpha1; console authorization resources use console.umkim.com/v1alpha1.

Application charts are installed with FleetApp onto a named Ready cluster. Capability candidate filters help operators choose; there is no placement engine and no DCM catalog.

Use the console or an approved authenticated client for management operations. Never rely on direct controller exposure or locally fabricated identity information as an authorization boundary.