If the fleetd agent version tied to the server-side version in any way?

We document the version of fleetd associated with a given Fleet version in the Fleet release notes.

Is there any risk to a client getting a version of fleetd that is newer than the server? It appears when generating a package we can't make it retrieve the version that matches the server.

@Phillip Boushy just wanted to clear up that

fleetctl

(admin app) is different than

fleetd

(what gets installed on hosts). You mentioned generating a package so I am assuming you mean

fleetctl

. There is generally no harm in

fleetctl

being behind, especially if for you are using it only for generating enrollment packages. One thing worth noting, if you install

fleetctl

via

npm

, it will auto-update when it notices a server update. As Kathy mentioned, the server will keep

fleetd

up to date on your hosts.

Hey Allen - No I meant

fleetd

-

fleetctl package

generates a package, but the version of the package changes every few weeks even if we haven't updated the server. I'm asking "Is there any risk to a client getting a version of

fleetd

that is newer than the server?" - Like with Jamf if you're running 11.4, the agent is 11.4 because the APIs match, etc.

So a couple of things worth noting, the version of `fleetd`/`orbit` does not have the same version number as your server. For example, the latest version of Fleet is 4.61 but the latest version of

fleetd

is 1.37.0 and the latest version of

osquery

is 5.15.0. Your Fleet server is controlling the version of

fleetd

that is running via the agent options you have configured. Its not likely they will be on incompatible versions, and unless you have a specific reason to run the

edge

version of

fleetd

, you'll be fine with the default configuration of running on the

stable

channel.