One thing worth noting, if you install

fleetctl

via

npm

, it will auto-update when it notices a server update.

Is this why Fleet recommends installing fleetctl via

npm

? Since

fleetctl

is a self-contained binary on Linux, it seems excessive to install npm.

Installing

npm

is just one method for installing

fleetctl

. You can download the binary from GitHub and manually update it as needed.

Minor clarification there (I see that @Allen Houchins mentioned it in the other thread, but wanted to add it here as well):

fleetctl

itself is not autoupdated by

npm

to match your server version, that's something you'll need to manage manually (or using scripts, as we do in the Gitops action).

fleetctl

itself is not autoupdated by

npm

to match your server version

Uh, that's exactly the opposite of what Allen said. So installing

fleetctl

via

npm

or manually from the GitHub does not grant you auto-updates to match the server? If you want

fleetctl

to match the server, you need to determine the server version and then tell

npm

the version or download the appropriate release version?

Correct. The fleetd agent you’re generating with fleetctl auto updates, but fleetctl itself does not.