Blogpost: Fleet 4.22.0

[noahtalerman]

Fleet 4.22.0 is scheduled for release on 2022-10-20 (afternoon PST)

Goal

Prepare and publish the release blogpost for Fleet 4.22.0 so that folks in the Fleet/osquery community can understand the latest improvements.

How?

• @mike-j-thomas: Hand images for cover and primary improvements to @chris-mcgillicuddy
• @chris-mcgillicuddy: Write and publish blogpost
• @noahtalerman: Complete CHANGELOG

Primary improvements

• Know how many hosts, and which hosts, are missing #6435
• Know how many hosts, and which hosts, have a low disk space #7479
• Update query console right side panel in Fleet product #7080
• Update a host's display name #4931

List of other improvements

• Added usage statistics for the weekly count of aggregate policy violation days. One policy
  violation day is counted for each policy that a host is failing, measured as of the time the
  count increments. The count increments once per 24-hour interval and resets each week.

• Added functionality to consider device tokens as expired after one hour.
  This change is not compatible with older versions of Fleet Desktop, we recommend to manually update Orbit and Fleet Desktop to > v1.0.0 in addition to upgrading the server if:

  • You're managing your own TUF server.
  • Or have auto-updates disabled (fleetctl package [...] --disable-updates)
  • Or have channels pinned to an older version (fleetctl package [...] --orbit-channel 1.0.0 --desktop-channel 1.1.0)

• Clarify last seen time and last fetched time in Fleet UI

• Added server-side validation of user emails

• Added security headers to HTML, CSV and installer responses.

• Fix a bug in which clicking the select all checkbox did not select all in some cases.

• Fixed bug introduced in 4.21.0 where Windows-specific query was being sent to non-Windows hosts
  causing an error in query ingestion for directIngestOSWindows.

• Login route reroutes to dashboard if already logged in

• Create teams modal has better team name suggestions

• Translated technical error messages returned by Organization's and Team's validations to be more user-friendly.

• Fix a bug in which uninstalled software (DEB packages) appeared in Fleet.

• Added validation of the command_line_flags object in the Agent Options section of Organization Settings and Team Settings.

• Added logic to clean up irrelevant policies for a host on re-enrollment, for example: if a host changes its OS from linux to macOS or it changes teams.

• Rename machine serial to serial number and IPv4 properly to private IP address

• Added the inherited_policies array to the GET /teams/{team_id}/policies endpoint that lists the global policies inherited by the team, along with the pass/fail counts only for hosts that belong to that team.

• Fixed a bug where if a team didn't have a config.features settings and was edited via the UI, the both features.enable_host_users and features.enable_software_inventory would be false insead of the global default.

• Fixed host filters by mdm enrollment status

• add new UI state when results are coming in from a live query or policy query

• Fixed a bug that resulted in false negatives for vulnerable versions of Zoom, Google Chrome, Adobe Photoshop, Node.js, Visual Studio Code, Adobe Media Encoder, VirtualBox, Adobe Premiere Pro, Pip, and Firefox software.

• Fixed bug that caused duplicated vulnerabilities to be sent to third party integrations.

• Fixed panic in ingestKubequeryInfo query ingestion.

• Fix a bug in which host_count and user_count being always returned as 0 in teams/{id} endpoint.

• Updated Fleet Desktop to use the new endpoint introduced in
  Add new /api/_version_/fleet/device/{token}/desktop endpoint #7084

• Host details software table links to software details, better responsive UI for software table

• Fixed a server panic happening when a team was edited via yaml without an agent_options key.

[noahtalerman]

@chris-mcgillicuddy I assigned you to this issue. Can you please drive the writing of the blogpost? Please let me know how I can be helpful :)

[noahtalerman]

@mike-j-thomas I assigned you this issue and added it to the digital experience board.

Can you please create and upload the images for this release blog post? Thanks :)

[chris-mcgillicuddy]

@noahtalerman, when is this release scheduled to go live?

[noahtalerman]

when is this release scheduled to go live?

@chris-mcgillicuddy afternoon PST on Thursday, October 10th.

[noahtalerman]

@chris-mcgillicuddy @mike-j-thomas just checking in, how is the release blogpost coming along?

[chris-mcgillicuddy]

@noahtalerman, I've had to shift focus to address handbook issues. There's another blog post that we'd also like to post this week. Would it be possible to delay publishing this post until Monday, 10/24?

[noahtalerman]

possible to delay publishing this post until Monday, 10/24?

@chris-mcgillicuddy I think both blog posts should be prioritized above the handbook issues. That being said, it's your and @mike-j-thomas's call.

What's the other blog post? And, just for my understanding, what's the reason for prioritizing the other blogpost?

[chris-mcgillicuddy]

@noahtalerman, the other blog post addresses BOD 23-01. As I'm working on it though, I think it might take more time. I'll prioritize the release post for this week. My thinking was that releases can get delayed, which may result in no blogs going out this week. I wanted to have one blog ready just in case, but, again, the BOD 23-01 article is a little complex.

As for the handbook issues, Mike M. asked Charlie, Nathan, and I to reorganize content to better match departments. We've made good progress, so I can prioritize the blogs for the rest of the week.

[mike-j-thomas]

@chris-mcgillicuddy, I added the images to a draft pull request for the release post. You can add your write-up directly to this draft PR #8357

[noahtalerman]

My thinking was that releases can get delayed, which may result in no blogs going out this week.

@chris-mcgillicuddy totally makes sense. I had the same thought.

Thank you for drafting the blog post! https://docs.google.com/document/d/1Y87Q4mBMme73XA7rECAAsvJh7kA42mZskD5jYe05-_U/edit?disco=AAAAiDCcsPM&usp_dm=true

My plan is to response to your comments this afternoon EST.

[chris-mcgillicuddy]

@noahtalerman, Fleet 4.22.0 article is ready for your review:

https://docs.google.com/document/d/1Y87Q4mBMme73XA7rECAAsvJh7kA42mZskD5jYe05-_U/edit?usp=sharing

I included a couple comments for specific feedback.

[noahtalerman]

@chris-mcgillicuddy looking good! I responded to your comment and left a couple suggestions in the Google doc: https://docs.google.com/document/d/1Y87Q4mBMme73XA7rECAAsvJh7kA42mZskD5jYe05-_U/edit#

[chris-mcgillicuddy]

PR #8357 was merged on Friday, 10/21.