Skip to content
UMKIMDocs

Site creation

A FleetSite is a logical location with edge metadata: named spec.edge.ingress[] entries (port_forward, reverse_proxy) and optional hubGateway. Public onboarding creates registry sites; the seeded management site represents the hub and cannot be deleted or used for workload clusters.

When a registry site is created, the controller records its edge-domain intent. Attached clusters are derived from their site membership rather than manually entered on the site. Clusters bind to an ingress row with FleetClusterJoin.spec.edge.ingressId.

Inventory examples: examples/site-profiles/.

Match per-app FleetApp route.mode to site edge:

  • hub with site hubGateway
  • site with a bound port_forward or reverse_proxy ingress
  • none for chart-owned or internal ingress

Deletion is allowed only for an empty registry site. Configure and verify DNS, certificates, NAT, firewall rules, and third-party proxies separately; controller configuration does not prove those external systems are ready.

Day-2 site and ingress edits: console Sites detail or umkim site / umkim site ingress.