# Fleet allows agent upgrades higher than cluster version

**URL:** <https://discuss.elastic.co/t/fleet-allows-agent-upgrades-higher-than-cluster-version/375014>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [February 25, 2025, 12:23pm UTC](https://discuss.elastic.co/t/fleet-allows-agent-upgrades-higher-than-cluster-version/375014 "2025-02-25T12:23:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![djkprojects](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@djkprojects](https://discuss.elastic.co/u/djkprojects)\
**Post date:** [February 25, 2025, 12:23pm UTC](https://discuss.elastic.co/t/fleet-allows-agent-upgrades-higher-than-cluster-version/375014/1 "2025-02-25T12:23:34Z")

</div>

Hello,

In previous versions of Elastic the highest available version for upgrading Elastic Agent in fleet was the version of the cluster itself however the newer versions allow upgrading to the latest release version.

Is this expected as the documentation states the Agent cannot be higher version than the cluster itself and if this is the case it shouldn't be allowed in Fleet either.

Our cluster is 8.16.3 but the dropdown lets us go to v9

Can someone please clarify?

Thanks

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9ef72c78dc04072469be00fa827991cd97a3dc3b.png)

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [February 25, 2025, 1:54pm UTC](https://discuss.elastic.co/t/fleet-allows-agent-upgrades-higher-than-cluster-version/375014/2 "2025-02-25T13:54:34Z")

</div>

> [@djkprojects](#):
>
> Our cluster is 8.16.3 but the dropdown lets us go to v9

If you select any version higher than `8.16.X` will it show the upgrade button as available or will it be greyed out?

If I'm not wrong the versions available comes from the Elastic Package Registry, but the Fleet Server has some logic to block upgrades when the minor version is higher than the current Fleet Server.

I manage 2 clusters, one on 8.15.2 and another one on 8.17.2, both will make the upgrade button not available if I select a version where the minor or major version is higher than the current one.

For example, 8.16.X for the 8.15.2 cluster and 9.0.0 for the 8.17.2 cluster.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [February 25, 2025, 2:06pm UTC](https://discuss.elastic.co/t/fleet-allows-agent-upgrades-higher-than-cluster-version/375014/3 "2025-02-25T14:06:41Z")

</div>

On a cluster version 8.15.2, it correctly allows me to upgrade to 8.15.5.

 ![agent-screenshot](https://us1.discourse-cdn.com/elastic/original/3X/9/c/9cf2611ac124f064650646d1b02d8fa547bb370a.png)

But if I select a version where the minor or major version is higher than 8.15.X, it will not allow me to upgrade.

 ![Screenshot from 2025-02-25 10-53-02](https://us1.discourse-cdn.com/elastic/original/3X/b/f/bf779408232f639728e8570dcbe66bbf7677208b.png)

Same thing on a cluster on version 8.17.2 if I try to upgrade to 9.0.0.

 ![Screenshot from 2025-02-25 11-04-57](https://us1.discourse-cdn.com/elastic/original/3X/1/8/1852605466afc6d148ed33b7e330c0ab47266101.png)
