[DRBD-announce] LINSTOR Operator 1.7.0 and LINSTOR CSI 0.17.0 released

[Moritz Wanzenböck]

Dear LINSTOR on Kubernetes Users,

We just released LINSTOR Operator 1.7.0 as well as LINSTOR CSI 0.17.0.

The most exciting feature is certainly the option to run LINSTOR without an
additional database for the LINSTOR Controller. LINSTOR 1.16.0 added
experimental support for using the Kubernetes API directly to store its
internal state, which has been enhanced in 1.17.0. The current plan is to
support both Etcd and Kubernetes API as datastore, with the eventual goal
of removing Etcd support once we are happy with the stability of this new
backend. For more information, take a look at the updated user guide. [1]

This is also the first LINSTOR Operator release that supports creating
backups of your volumes and storing them in S3 or another LINSTOR cluster.
Currently this is only available using the LINSTOR CLI, take a look at the
linstor remote ... and linstor backup ... commands. In a future release,
this should be more tightly integrated with the Kubernetes infrastructure.
In order to securly store any access tokens for remote locations, LINSTOR
needs to be configured with a master passphrase. If no passphrase is
defined, the Helm chart will create one for you.

On the LINSTOR CSI front, a lot of improvements have been made under the
hood since shifting our focus away from Stork. The CSI driver now
automatically decides when it is appropriate to create diskless resources.
Previous releases of LINSTOR CSI would cause Kubernetes to never schedule
on nodes without a storage pool, even if diskless access was permitted.
With the introduction of advanced rules for diskless access, this issue is
now resolved. You can find examples in our user guide. [2]

The new chart version is available from https://charts.linstor.io and new
images are available from drbd.io. The usual upgrade procedure applies:

$ helm repo update
$ helm upgrade linstor-op linstor/linstor -f orig.yaml

For more information, please take a look at the upgrade guide. [3]

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

Best regards,
Moritz

[1]: https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#ch-kubernetes
[2]:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-volume-accessibility-and-locality
[3]:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade
[4]: https://github.com/piraeusdatastore/piraeus-operator

Full changes
------------

Added (Operator)
----------------
- Automatically create a LINSTOR passphrase when none is configured.
- Automatic eviction and deletion of offline satellites if the Kubernetes
node object was also deleted.

Changed (Operator)
------------------

- Default images:
-- drbd.io/linstor-controller:v1.17.0
-- drbd.io/linstor-satellite:v1.17.0
-- drbd.io/linstor-csi:v0.17.0
-- drbd.io/drbd9-rhel7:v9.1.4
-- drbd.io/drbd-reactor:v0.5.1
- Recreates or updates to the satellite pods are now applied at once,
instead of waiting for a node to complete before
  moving to the next.

Added (CSI)
-----------

- Gained the ability to handle preprovisioned volumes. In general this
involves creating matching PV object with the volume handle set to an
existing LINSTOR resource.
- Finer diskless volume control with new allowed values for the
"allowRemoteVolumeAccess" parameter.

Changed (CSI)
-------------

- Expand volumes after cloning or restoring from snapshot if required.
Previously the volume would report the wrong size to Kubernetes, creating
smaller volumes than requested by accident.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-announce/attachments/20211214/fa477ba2/attachment.htm>