# LINSTOR Operator v2.5.2

**URL:** <https://forums.linbit.com/t/linstor-operator-v2-5-2/183>\
**Category:** Release Announcements\
**Tags:** kubernetes\
**Created:** [July 22, 2024, 6:52am UTC](https://forums.linbit.com/t/linstor-operator-v2-5-2/183 "2024-07-22T06:52:45Z")\
**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:** [July 22, 2024, 6:52am UTC](https://forums.linbit.com/t/linstor-operator-v2-5-2/183/1 "2024-07-22T06:52:45Z")

</div>

This contains updated LINSTOR, CSI driver and DRBD versions.

The LINSTOR CSI driver fixes some issues with the new caching strategy, as well as an issue when using both a custom “allowRemoteVolumeAccess” policy in combination with “diskless” worker nodes.

DRBD 9.2.10 contains a fix for a potential deadlock that was triggered by the way the the CSI driver handled removing of volumes.

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

```auto
resources:
- https://charts.linstor.io/static/v2.5.2.yaml

```

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

```auto
$ helm repo update
$ helm upgrade linstor-operator linstor/linstor-operator --wait

```

To get specific instructions to apply the update, check our [users guide](https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade).

If you need to upgrade from Operator v1, check out our [upgrade guide](https://charts.linstor.io/migration/).

Source code is, as always, available [upstream](https://github.com/piraeusdatastore/piraeus-operator).

## Operator v2.5.2 Changelog

### Added

- Option to specify custom CA certificate resources for TLS configuration.
- Ensure all Certificate resources have `dnsNames` set.

### Changed

- Updated images:
  - LINSTOR 1.28.0
  - LINSTOR CSI 1.6.3
  - DRBD 9.2.10
  - DRBD Reactor 1.4.1
  - kTLS-utils 0.11
  - Latest CSI sidecars

### Fixed

- The operator will no longer restart reconciliation on every change to `ServiceAccount` resources.