Hi everyone! I just wanted to let you know that the feature for uploading custom organization logos, introduced in

v4.86.0

, is breaking for Kubernetes deployments that use a mandatory read-only file system. It's necessary to create a volume (usually an

emptyDir

) in

/tmp/org-logos

so that the application doesn't get stuck in CrashLoopBackOff with the log below:

Using config file: /tmp/config/fleet.yaml
{"ts":"2026-06-08T14:33:30Z","level":"info","msg":"redis initialized","component":"redis","mode":1}
{"ts":"2026-06-08T14:33:30Z","level":"info","msg":"host lookup redis cache enabled","component":"mysqlredis","ttl":60000000000}
Failed to start: initializing filesystem org logo store: mkdir /tmp/org-logos: read-only file system

Hey @Saulo Guilhermino, thanks for the heads up. We'll get a bug opened for this and start looking into it.

Thank you for reporting this! We're on it.

Hey @Saulo Guilhermino, just wanted to share with you that this should be fixed in https://github.com/fleetdm/fleet/releases/tag/fleet-v4.86.2

Awesome! Thank you for the update and for acting quickly on this 👏