Hello FleetDM team & Admins, I have a couple of inquiries regarding our current deployment and some issues we're encountering: 1. Upgrade Sequence for FleetDM: We have our FleetDM set up in a GCP GKE Autopilot cluster with CloudSQL, managed through Terraform with a custom Helm chart. Our planned upgrade sequence for FleetDM versions is: ◦ v4.39 ◦ v4.41 ◦ v4.51 ◦ v4.67 Could you please provide guidance or best practices on executing this upgrade sequence? Are there any specific steps or precautions we need to take at each stage to ensure a smooth transition? ◦ 2. Pub/Sub Results Log Feed Issues: After upgrading from v4.30.1 to v4.39, we have noticed that our Pub/Sub results log feed has stopped functioning, yet the system status indicates that it is still operational, with no noticeable errors reported. ◦ What could be the possible reasons behind the Pub/Sub results log feed becoming inactive while the status shows it as active? ◦ Are there any diagnostic steps or tools you recommend for troubleshooting this issue? These details would greatly aid us in addressing the current problems and ensuring a seamless upgrade process. Looking forward to your expert advice.

by the way for the pubsub issue, the results logs stopped coming. the pubsub status logs keep flowing 🙂 and >the system status indicates that it is still operational the container logs indicate it's registering the pubsub writer for both status and result topics,

GCP PubSub writer configured

, just no logs flowing for results anymore somehow for >Our planned upgrade sequence for FleetDM versions we're not sure where the versions came from (one of our colleagues suggested it without a reference)... So just looking for some general guidance on big gap version upgrades to current the latest would've changed from v4.67 to 4.70.1 by now i guess

Hello! Great questions, double checking with the team for any info on best practices, etc. I'll pass them along as soon as I have them for you.

Hi @Vlad Previn and @Pin Li! My only recommendation there would be to check the release notes for each version you’re planning to upgrade to to check for any required infrastructure updates or known issues. For example, there’s a v4.41.1 patch release that addresses a known issue with result log forwarding in some scenarios: https://github.com/fleetdm/fleet/issues/15168

thank you folks, that's helpful will try re 4.41.1 hopefully Matt and co can also suggest an upgrade path to close the version gap as well one more question please The packs stuff has been deprecated but 'kindly left there' as a legacy. in 4.39 still there. Is it still there in 4.71.0 or gone?

/packs/manage

gui and the apis

/api/latest/fleet/packs

/api/latest/fleet/packs/schedule

/api/latest/fleet/packs/{pack['id']}

we have pipeline dependencies on these unfortunately

It’s all still there, and will not be removed.

@Matt Rebelo did the folks on your side have more thoughts on the upgrade path from 4.39 to current (4.71.1)?

@Vlad Previn the good news is when I say I'm checking with the team, I'm checking with @Kathy Satterlee so you got all the info right from the source! 😃

also looking at our gcp cloudsql DB - instance version: MySQL 8.0.28 🤔 that's curious (gcp managed for upgrades) - is it has its own instance (fleetdm) - do we need to check at database level as well or that would be compatible with 4.55>=? Or is instance level enough