[DRBD-user] LINSTOR Operator release 1.8.1

[Moritz Wanzenböck]

Dear LINBIT SDS on Kubernetes users,

We just released LINSTOR Operator 1.8.1.

As expected for a patch release, no dramatic changes here, instead
just bringing all components to their latest release:

- LINSTOR 1.18.1: includes some stability improvements and support for
DRBD 9.1.7 features.
- DRBD 9.1.7: improves the way suspend of workloads works when losing quorum.
- LINSTOR CSI 0.19.0: fixes issues when provisioning big file system
volumes and when restoring a backup in a zoned cluster.

For LINSTOR CSI, there is one important note: If you provisioned an
empty volume using <0.19.0, but never used it until upgrading to
0.19.0 the volume will not attach. The solution is to delete the claim
and create it again. As the volumes were empty and never used, this
likely doesn't actually impact anyone.

For the operator itself: if you are using the "k8s" backend, you no
longer need to confirm creating a backup of the database before
upgrading: this is now directly handled by the operator, and the charm
hook was removed.

The new chart is available from https://charts.linstor.io. 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. [1]

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

Best regards,
Moritz

[1]: https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade
[2]: https://github.com/piraeusdatastore/piraeus-operator

Full Changes
------------

### Changed

- Default images:
  * LINSTOR 1.18.1
  * LINSTOR CSI 0.19.0
  * DRBD 9.1.7
  * DRBD Reactor 0.6.1

### Added

- Upgrades involving k8s databases no longer require manually
confirming a backup exists using
  `--set IHaveBackedUpAllMyLinstorResources=true`.