Fleet Types

Microservices fleets are full-featured, allowing you to run multiple containers and set up a public URL.

circle-exclamation

Essentials, Classic, and Legacy (sunset)

Essentials, classic, and legacy fleets allow you to run a single container and do not permit public device URLs. The classic and legacy fleet types allow for fleets that don't meet the requirements for new fleet types. Classic fleets support devices with balenaOS v2.0.3 and above, and legacy fleets support all earlier balenaOS versions. Classic fleets use Docker Registry V2, whereas legacy fleets use the slower and less reliable Registry V1. New classic fleets can only be created for device types that do not yet have balenaOS v2.12.0 or higher available. However, for supported device types, you can convert an essentials, classic, and legacy fleet to a microservices fleet, as described below.

circle-exclamation

Converting to Microservices

Existing fleets can be converted to Microservices, as long as all devices belonging to that fleet meet the OS version requirements, and the account has appropriate privileges.

To convert your fleet, first be sure all devices meet the balenaOS version requirements for the desired fleet type, updating if necessary. Then, from the fleet summary page, click Settings, and scroll down to the Fleet type section. Select the fleet type you would like to convert to from the dropdown. If your fleet cannot be converted to the selected type, you will see it marked as unavailable.

Last updated

Was this helpful?