What’s the update strategy for endpoint packages? ...
# fleet
s
What’s the update strategy for endpoint packages? I occasionally see Orbit releases in GitHub, how do we make sure our endpoints have the latest version? Do they self-update? Does
fleetctl
pull the latest version when building installers, so we have to re-build? In the web portal I only see the osquery version, not the Orbit version, so it’s always felt opaque to me.
k
Hi! Orbit keeps itself up to date, based on a configurable update channel
You can check the Orbit version on your hosts with the orbit_info table
s
Is Fleetd the old name for Orbit?
Because that
orbit_info
table is not available in my instance
Apologies if I’m missing some basic concepts here
k
Is it not queryable, or not showing up in the schema?
s
When I try to create a new query through the web UI, it’s not in the list of tables
k
Try querying it anyway.
SELECT * FROM orbit_info;
s
That worked!
k
I'll look in to why it's not showing as a table.
s
Stable channels for all three components, most on 1.6.0, a couple laggards on 1.5.0. 👍
Thanks for explaining!
k
Any time!