9. Separate fleets
One fleet is one unit of trust. It has one server, one database, its own keys, its own sign-in and its own members. Two fleets share nothing. If two teams must not see the work of each other, give each team its own fleet.
fleet login <url>keeps one user token for each fleet, in~/.config/fleet/<fleet>/token.fleet use <name>sets the fleet that the next commands use.--fleet <name>selects a fleet for one command (fleet/internal/cli/target.go).- The page shows the fleet's name in its header, so you know which fleet you look at.
- Give each fleet its own GitHub team and its own client at the identity provider. Do not use again a team that opens other services.
- A node process joins one fleet only. To serve two fleets from one machine, run one node
process for each fleet, each with its own
--dirand unix user. The cleanvm layouttwofleetstests this (fleet/test/cleanvm/layouts/twofleets.sh).
This is the full picture: each fleet has one server and any number of nodes, and each node runs turns in its own way. Pages 1 to 8 added these parts one at a time.
Where to go from here
- The architecture pages show each layout and each sequence in full.
- The panel pages tell you how to read the dashboard.
- The glossary gives each word one meaning.
- To install, read operators. To use a fleet, read users.
Next: this is the last page. Return to the start of the guide.