Create a site

Create a registry site in the authenticated console (or with umkim site create) before creating workload clusters. The management site represents the hub and must not host workload clusters.

Provide the site identity, region, and edge settings. Sites do not use a single site-wide exposure_mode. Instead:

Edge setting	Behavior
hubGateway	Enables hub-fronted public URLs for the site
Ingress entry port_forward	WAN port-forwards to spoke Traefik NodePorts; one cluster binds per entry
Ingress entry reverse_proxy	External reverse proxy reaches cluster ingress; may be shared
Neither	No fleet-managed WAN exposure at the site

Add or edit ingress rows in console Sites detail, or:

umkim site ingress add SITE --id ID --method port_forward --address A --zone Z --wildcard W
umkim site ingress list SITE

Inventory examples: examples/site-profiles/.

A registry site becomes Ready before it has clusters; membership is derived later from each cluster’s site assignment. Clusters bind to an ingress row with ingressId (umkim cluster patch --ingress-id).

Configure public DNS, NAT, firewall, and TLS outside UMKIM, then verify the live route. The controller does not create those external resources for you.

Match per-app FleetApp route.mode to site edge: hub with hubGateway; site with a bound port_forward or reverse_proxy ingress; none for chart-owned or internal ingress.

For delete rules and edge metadata, see the site lifecycle.