# LINSTOR Operator v2.8.0

**URL:** <https://forums.linbit.com/t/linstor-operator-v2-8-0/630>\
**Category:** Release Announcements\
**Tags:** kubernetes, drbd\
**Created:** [February 17, 2025, 9:25am UTC](https://forums.linbit.com/t/linstor-operator-v2-8-0/630 "2025-02-17T09:25:51Z")\
**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:** [February 17, 2025, 9:25am UTC](https://forums.linbit.com/t/linstor-operator-v2-8-0/630/1 "2025-02-17T09:25:51Z")

</div>

We've recently released version 2.8.0 of our Kubernetes Operator.

This release improves support for reusing existing LINSTOR clusters to  
provide storage for Kubernetes in a few different ways.

First, you can now specify multiple controller URLs when setting up  
the connection. This is commonly used when setting up a highly  
available LINSTOR Controller with DRBD Reactor: specify the possible  
IP addresses where the Controller is running, and the Operator and  
components will automatically connect to the right node.

Secondly, the Operator will now automatically try to determine the  
LINSTOR version from the external controller, and deploy the matching  
Satellite version by default.

With the usual update of image versions, we also now support the  
x-replicas-on-different setting on StorageClasses[1]. For example, to  
deploy 2 replicas per zone, you can now set:

parameters:  
&nbsp;&nbsp;linstor.csi.linbit.com/xReplicasOnDifferent: |  
&nbsp;&nbsp;&nbsp;&nbsp;topology.kubernetes.io/zone: 2

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

&nbsp;&nbsp;[https://charts.linstor.io/static/v2.8.0.yaml](https://charts.linstor.io/static/v2.8.0.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[2].

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

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

Best regards,  
Moritz

[1]: [Distributing Volume Replicas for High Availability & Disaster Recovery Using LINSTOR - LINBIT](https://linbit.com/blog/distributing-volume-replicas-for-high-availability-disaster-recovery-using-linstor/)  
[2]: [https://linbit.com/drbd-user-guide/linstor-guide-1\_0-en/#s-kubernetes-upgrade](https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade)  
[3]: [Migrating to Operator V2](https://charts.linstor.io/migration/)  
[4]: [GitHub - piraeusdatastore/piraeus-operator: The Piraeus Operator manages LINSTOR clusters in Kubernetes.](https://github.com/piraeusdatastore/piraeus-operator)

Operator v2.8.0 Changelog  
-------------------------  
### Added

- Automatically set the LINSTOR Satellite image version when using an  
external LINSTOR Controller.

### Changed

- Disable debug logging by default for the Operator.  
- Allow specifying multiple controller URLs for external LINSTOR clusters.  
- Updated images:  
&nbsp;&nbsp;&nbsp;&nbsp;\* LINSTOR 1.30.4  
&nbsp;&nbsp;&nbsp;&nbsp;\* LINSTOR CSI 1.7.0  
&nbsp;&nbsp;&nbsp;&nbsp;\* DRBD Reactor 1.8.0  
&nbsp;&nbsp;&nbsp;&nbsp;\* LINSTOR HA Controller 1.3.0  
&nbsp;&nbsp;&nbsp;&nbsp;\* Latest CSI sidecars
