# LINSTOR Operator 2.10.2

**URL:** https://forums.linbit.com/t/linstor-operator-2-10-2/1073
**Category:** Release Announcements
**Tags:** kubernetes, drbd
**Created:** [November 27, 2025, 2:04pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-2/1073 "2025-11-27T14:04:48Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![wanzenbug](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/wanzenbug/32/39_2.png) [@wanzenbug](https://forums.linbit.com/u/wanzenbug)
#### Post date: [November 27, 2025, 2:04pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-2/1073/1 "2025-11-27T14:04:48Z")

</div>

We've just released another small bug fix for our Kubernetes Operator.

We have updated DRBD to 9.2.16, and also updated LINSTOR CSI to 1.10.3  
to fix some small issues with the new "fsck" checks on mounts.

In addition, we have added some configurable timeouts when using  
graceful evacuation, and fixed a bug that prevented the SELinux  
integration of LINSTOR CSI from working.

We recommend all users of release 2.10.x to update to this latest release.

To upgrade, either point your kustomization.yaml at the new manifest:

&nbsp;&nbsp;[https://charts.linstor.io/static/v2.10.2.yaml](https://charts.linstor.io/static/v2.10.2.yaml)

Or, if using helm, upgrade the linstor-operator chart:

&nbsp;&nbsp;helm repo update  
&nbsp;&nbsp;helm upgrade linstor-operator linstor/linstor-operator --wait

To get specific instructions to apply the update, check our users guide[1].

If you need to upgrade from Operator v1, check out our upgrade guide[2].

Source code is, as always, available upstream[3].

Best regards,  
Moritz

[1]: [LINSTOR 1.0 en - LINBIT](https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade)  
[2]: [Migrating to Operator V2](https://charts.linstor.io/migration/)  
[3]: [GitHub - piraeusdatastore/piraeus-operator: The Piraeus Operator manages LINSTOR clusters in Kubernetes.](https://github.com/piraeusdatastore/piraeus-operator)
