Add supported versions of Redis to the FAQ (#44471)

Spurred from https://github.com/fleetdm/fleet/pull/43936.
2026-05-05 10:16:17 -03:00
parent 01c526089a
commit ac8d875fb4
1 changed files with 4 additions and 4 deletions
@@ -155,6 +155,10 @@ See the ["How to uninstall fleetd" guide](https://fleetdm.com/guides/how-to-unin

 Fleet is tested with MySQL 8.0.44, 8.4.8, and 9.5.0 (9.6.0 is currently incompatible). Newer versions of MySQL 8 typically work well. AWS Aurora requires at least version 3.10.3. Please avoid using MariaDB or other MySQL variants that are not officially supported. Compatibility issues have been identified with MySQL variants, and these may not be addressed in future Fleet releases.

+### What Redis versions are supported?
+
+Fleet is actively tested with Redis 6.2 and 7 (specifically engine_version 7.1 on AWS ElastiCache). Redis 8 and Valkey are also known to work, though we don't currently actively test with those versions.
+
 ### What version of the Mac Admins osquery extension is supported?

 Fleet deploys v1.4.1 of the [Mac Admins osquery extension](https://github.com/macadmins/osquery-extension), with full support for the tables currently available in Fleet. For a list of supported tables, see the [Fleet tables reference](https://fleetdm.com/tables).
@@ -514,7 +518,6 @@ We've found this error when you try to build an MSI on Docker 4.17. The underlyi
 - [Does Fleet support MySQL replication?](#does-fleet-support-mysql-replication)
 - [What is duplicate enrollment and how do I fix it?](#what-is-duplicate-enrollment-and-how-do-i-fix-it)
 - [What API endpoints should I expose to the public internet?](#what-api-endpoints-should-i-expose-to-the-public-internet)
- [What Redis versions are supported?](#what-redis-versions-are-supported)

 ### How do I get support for working with Fleet?

@@ -704,9 +707,6 @@ Fleet requires at least MySQL version 8.0.44, and is tested using the InnoDB sto

 To migrate from Fleet Free to Fleet Premium, once you get a Fleet license, set it as a parameter to `fleet serve` either as an environment variable using `FLEET_LICENSE_KEY` or in [Fleet's config file](https://fleetdm.com/docs/deploying/configuration#license). You don't need to redeploy Fleet after the migration.

-### What Redis versions are supported?
-Fleet is actively tested with Redis 6 and 7. Redis 8 and Valkey are also known to work, though we don't currently actively test with those versions.
-
 ## What happened to the "Schedule" page?
 Scheduled queries are not gone! Instead, the concept of a scheduled query has been merged with a saved query. After 4.35, scheduling now happens on the queries page: a query can be scheduled (via familiar attributes such as "interval" and "platform"), or it can simply be saved to be run ad-hoc. A query can now belong to a team, or it can be a global query that every team inherits. This greatly simplifies the mental model of the product and enables us to build [exciting features](https://github.com/fleetdm/fleet/issues/7766) on top of the new unified query concept.