Fleet

The Fleet page connects this FlatRun server to others without moving their deployments. For the concepts behind it, see Clustering & Federation.

Set up Fleet

1. Open Fleet and select Set up Fleet.
2. Confirm the server name.
3. Confirm the agent URL that other servers can reach.
4. Select Enable Fleet.

The agent URL is suggested from Server Info. Change it when peers must use a different public or private address.

Fleet overview

The page header summarizes this server:

• Server name: how this node identifies itself to peers
• Peer count: number of connected servers
• Runtime: the selected orchestrator and traffic router

Peer list

Connected peers appear in a table:

• Name and URL
• Status: online or offline
• Last seen: the last successful peer check
• Actions: open deployments, edit access, or remove the peer

Manage deployments across servers

Deployments shows this server by default. Select a server under Deployments in the sidebar, or use a peer's Deployments action, to open only that server's inventory. You can inspect a peer deployment or run an allowed operation without signing in to the peer separately.

Choose providers

Open Cluster providers to select Docker Swarm with Nginx or K3s with Traefik. FlatRun checks the selected provider before saving it. K3s also asks for the kubeconfig path and namespace.

Offer capacity to a peer

1. Open a peer's permissions.
2. Enable Offer capacity.
3. Set the maximum CPU, memory, and replicas that peer may use.
4. Save the policy.

Capacity permission is separate from deployment read and run permissions. Removing it prevents new workload placement for that peer.

Invite a server

1. Select Invite server.
2. Copy the token from the dialog. It expires in one hour and works once.
3. Hand the token and this server's URL to whoever administers the other server.

Join a Fleet

1. On the server that received an invite, select Join Fleet.
2. Enter the peer server URL (the server that issued the invite).
3. Paste the invite token.
4. Click Connect. The two servers exchange API keys and the peer appears in both lists.

Removing a Peer

1. Find the peer in the list and click its remove action.
2. Confirm. The peer is disconnected immediately.

Reconnecting a removed peer requires a new invite.

Permissions

Generating invites, joining, and removing peers require the cluster:write permission. Users without it can view cluster status but not change membership.

Each peer also has its own access policy. Viewing or operating deployments, reading capacity, offering capacity, publishing events, and managing routes are separate grants. Capacity remains disabled until an administrator explicitly enables it and sets limits.