'[DRBD-announce] LINSTOR Operator 1.8.0'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: drbd-announce
Subject: [DRBD-announce] LINSTOR Operator 1.8.0
From: Moritz_Wanzenböck <moritz.wanzenboeck () linbit ! com>
Date: 2022-03-15 16:25:35
Message-ID: CAKnz9xKQDk-rHf9PHODDsMfpMim3ZN8Y7HCv7=qN8HgsrvzHaw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Dear LINBIT SDS on Kubernetes users,

We just released Operator 1.8.0

As there weren't many changes since the release candidate, I'll mostly copy
that announcement.

1.8.0 includes many quality of life improvements, as well as the usual
upgrade of components.

A few changes I want to highlight:

* Thanks to an open source contributor, it is now easier than ever to set
up secure communication between all components. A simple "--set
linstorHttpsMethod=helm --set linstorSslMethod=helm" will get you started!
An updated user guide will follow soon.

* The new LINSTOR CSI 0.18.0 can finally integrate with the existing
"Backup to S3" features in LINSTOR: That means you can create off-site
backups using the Kubernetes native VolumeSnapshot resources. You can check
the examples on the upstream project for more information, a user guide
will follow soon. [1][2]

* Some much needed bug fixes were applied to the new LINSTOR k8s backend.
Certain operations (such as node evacuation or toggling resources to
diskless) caused LINSTOR 1.17.0 to corrupt its database. These issues are
now fixed.

Speaking of the k8s backend: While upgrading, if you use the k8s backend,
you will be instructed to back up your resources (see [3] how). A new
feature in the Operator can automate this step. However, as the update
might be triggered while the old operator version is still running, the
manual acknowledgement can only be removed in a future update.

The new chart version will be available from https://charts.linstor.io
shorty. 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://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volume-snapshot-class.yaml
[2]:
https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volume-snapshot-from-s3.yaml
[3]:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade
[4]: https://github.com/piraeusdatastore/piraeus-operator

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

Breaking
--------

- If you have SSL configured, then the certificates must be regenerated in
PEM format.

Added
-----

- Allow setting the number of parallel requests created by the CSI
sidecars. This limits the load on the LINSTOR backend, which could easily
overload when creating many volumes at once.
- Unify certificates format for SSL enabled installation, no more java
tooling required.
- Automatic certificate generation using Helm or Cert-manager
- HA Controller and CSI components now wait for the LINSTOR API to be
initialized using InitContainers.

Changed
-------

- Create backups of LINSTOR resources if the "k8s" database backend is used
_and_ an image change is detected. Backups are stored in Secret resources
as a `tar.gz`. If the secret gets too big, the backup can be downloaded
from the operator pod.
- Default images:
  * LINSTOR 1.18.0
  * LINSTOR CSI 0.18.0
  * DRBD 9.1.6
  * DRBD Reactor 0.5.3
  * LINSTOR HA Controller 0.3.0
  * CSI Attacher v3.4.0
  * CSI Node Driver Registrar v2.4.0
  * CSI Provisioner v3.1.0
  * CSI Snapshotter v5.0.1
  * CSI Resizer v1.4.0
  * Stork v2.8.2
- Stork updated to support Kubernetes v1.22+.
- Satellites no longer have a readiness probe defined. This caused issues
in the satellites by repeatedly opening unexpected connections, especially
when using SSL.
- Only query node devices if a storage pool needs to be created.
- Use cached storage pool response to avoid causing excessive load on
LINSTOR satellites.
- Protect LINSTOR passphrase from accidental deletion by using a finalizer.

[Attachment #5 (text/html)]

<div dir="ltr">Dear LINBIT SDS on Kubernetes users, We just released Operator \
1.8.0 As there weren&#39;t many changes since the release candidate, I&#39;ll \
mostly copy that announcement. 1.8.0 includes many quality of life \
improvements, as well as the usual upgrade of components. A few changes I want \
to highlight: * Thanks to an open source contributor, it is now easier than \
ever to set up secure communication between all components. A simple &quot;--set \
linstorHttpsMethod=helm --set linstorSslMethod=helm&quot; will get you started! An \
updated user guide will follow soon. * The new LINSTOR CSI 0.18.0 can \
finally integrate with the existing &quot;Backup to S3&quot; features in LINSTOR: \
That means you can create off-site backups using the Kubernetes native VolumeSnapshot \
resources. You can check the examples on the upstream project for more information, a \
user guide will follow soon. [1][2] * Some much needed bug fixes were applied \
to the new LINSTOR k8s backend. Certain operations (such as node evacuation or \
toggling resources to diskless) caused LINSTOR 1.17.0 to corrupt its database. These \
issues are now fixed. Speaking of the k8s backend: While upgrading, if you use \
the k8s backend, you will be instructed to back up your resources (see [3] how). A \
new feature in the Operator can automate this step. However, as the update might be \
triggered while the old operator version is still running, the manual acknowledgement \
can only be removed in a future update. The new chart version will be \
available from <a href="https://charts.linstor.io">https://charts.linstor.io</a> \
shorty. New images are available from <a href="http://drbd.io">drbd.io</a>. 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]: <a \
href="https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volume- \
snapshot-class.yaml">https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volume-snapshot-class.yaml</a> [2]: \
<a href="https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volu \
me-snapshot-from-s3.yaml">https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/volume-snapshot-from-s3.yaml</a> [3]: \
<a href="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</a> [4]: \
<a href="https://github.com/piraeusdatastore/piraeus-operator">https://github.com/piraeusdatastore/piraeus-operator</a> Full \
Changes ------------ Breaking -------- - If you have SSL \
configured, then the certificates must be regenerated in PEM \
format. Added ----- - Allow setting the number of parallel requests \
created by the CSI sidecars. This limits the load on the LINSTOR backend, which could \
easily overload when creating many volumes at once. - Unify certificates format \
for SSL enabled installation, no more java tooling required. - Automatic \
certificate generation using Helm or Cert-manager - HA Controller and CSI \
components now wait for the LINSTOR API to be initialized using \
InitContainers. Changed ------- - Create backups of LINSTOR \
resources if the &quot;k8s&quot; database backend is used _and_ an image change is \
detected. Backups are stored in Secret resources as a `tar.gz`. If the secret gets \
too big, the backup can be downloaded from the operator pod. - Default images: \
* LINSTOR 1.18.0 * LINSTOR CSI 0.18.0 * DRBD 9.1.6 * DRBD Reactor \
0.5.3 * LINSTOR HA Controller 0.3.0 * CSI Attacher v3.4.0 * CSI \
Node Driver Registrar v2.4.0 * CSI Provisioner v3.1.0 * CSI Snapshotter \
v5.0.1 * CSI Resizer v1.4.0 * Stork v2.8.2 - Stork updated to support \
Kubernetes v1.22+. - Satellites no longer have a readiness probe defined. This \
caused issues in the satellites by repeatedly opening unexpected connections, \
especially when using SSL. - Only query node devices if a storage pool needs to be \
created. - Use cached storage pool response to avoid causing excessive load on \
LINSTOR satellites. - Protect LINSTOR passphrase from accidental deletion by using \
a finalizer.</div>

_______________________________________________
drbd-announce mailing list
drbd-announce@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-announce

[prev in list] [next in list] [prev in thread] [next in thread] 