Ceph Squid to Tentacle upgrade
Upgrading a cephadm-managed Squid cluster to Tentacle before Squid's estimated end of life: health checks, staggered daemon upgrade order, require-osd-release, new defaults and a rollback-free test plan.

Upgrade pages for moving between Ceph major releases with cephadm, based on the Ceph release notes and releases index.
Upgrading a cephadm-managed Squid cluster to Tentacle before Squid's estimated end of life: health checks, staggered daemon upgrade order, require-osd-release, new defaults and a rollback-free test plan.
Taking an out-of-support Reef cluster straight to Tentacle, which the Tentacle notes support: prerequisites, conversion of older non-cephadm clusters, upgrade sequencing and post-upgrade checks.
Moving a Quincy cluster forward when Tentacle does not support it as a source: upgrading to Squid first, then on to Tentacle before Squid's estimated end of life, with checks between the two hops.
FileStore OSDs cannot run on Reef or later: choosing mark-out replacement, whole-host replacement or per-OSD copy, keeping destruction inside one failure domain, and sequencing conversion with the release upgrade.
Handling the non-optimal tunables warning after an upgrade: how much data moves, which older kernel and librados clients are cut off, and planning the change around client upgrades.
Running cephadm upgrades without internet access: mirroring the new Ceph and monitoring images into a local registry, pointing the upgrade at the local image and checking every host can pull it.
Keeping a supported release patched: which releases receive backports and security fixes, reading point release notes for CVE fixes, and rolling a point release through a cluster with cephadm.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.