From: "Moritz Wanzenböck" <moritz.wanzenboeck@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: [DRBD-announce] linstor-csi 0.10.2 released
Date: Fri, 04 Dec 2020 10:52:54 +0100 [thread overview]
Message-ID: <6G7TKQ.MXKBGVH3RPKJ3@linbit.com> (raw)
Dear LINSTOR on Kubernetes Users,
We just released version 0.10.2 of LINSTOR CSI.
This release contains fixes for the following issues:
- Under specific conditions it was possible for
a PV to be created in Kubernetes without the matching
LINSTOR resources being available. Any Pods using these
PVs would forever be stuck, as LINSTOR CSI would fail
to attach the volume. Any PV created in this way has
to be deleted and re-created.
- Another possible outcome of the above bug was a complete
crash of LINSTOR CSI on a node. On restart of the pod,
it would immediatly crash again.
The update is available from our registry:
drbd.io/linstor-csi:v0.10.2
Updates can be applied by:
- Using the LINSTOR helm chart:
Run helm upgrade, setting:
csi.pluginImage=drbd.io/linstor-csi:v0.10.2
- Other linstor-operator deployments:
Edit the LinstorCSIDriver resource and set:
linstorPluginImage: drbd.io/linstor-csi:v0.10.2
Best regards,
Moritz
reply other threads:[~2020-12-04 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6G7TKQ.MXKBGVH3RPKJ3@linbit.com \
--to=moritz.wanzenboeck@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.