NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2570 by repository stars
Latest stable
v1.10.9
Last release 3 years ago
no release in 18 months
Ships fairly regularly
a new release about every 5 weeks
Nearly every release is documented
notes for 35 of 35 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
103 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
This release updates the base images to the latest upstream releases.
This release updates the base images to the latest upstream releases.
Updates will only happen for Operator v2. Please start the migration process described in upgrade guide.
If you see this release and wonder what happened to the other v1.10.9: there was a typo in the CSI sidecar containers that needed fixing.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
This updates images and fixes a bug where some seldom used values could not be set via the helm chart.
This updates images and fixes a bug where some seldom used values could not be set via the helm chart.
Nothing published for this version
This release contains updated images, as well as a direct dependency on the HA Controller chart.
This release contains updated images, as well as a direct dependency on the HA Controller chart.
If you run had haController.enabled=true, please use piraeus-ha-controller.enabled=true now instead.
Nothing published for this version
This releases fixes a bug in the monitoring services created, which meant that the satellite set was not properly updated. It also adds monitoring to
This releases fixes a bug in the monitoring services created, which meant that the satellite set was not properly updated. It also adds monitoring to the CSI sidecars, if monitoring is available.
Nothing published for this version
This release brings the usual round of image updates, along with a fix for the optional Stork deloyment and an update to allow DNS policy customizatio
This release brings the usual round of image updates, along with a fix for the optional Stork deloyment and an update to allow DNS policy customization for the satellites.
The dns policy change requires updating the CRDs. To replace the CRDs, run:
kubectl replace -f ./charts/piraeus/crds
If you do not need to change dns policy, there is no need to replace the CRDs.
Nothing published for this version
This release brings the usual round of image updates, as well as a fix to the way we register the controller pod.
This release brings the usual round of image updates, as well as a fix to the way we register the controller pod.
Nothing published for this version
Nothing published for this version
This release brings the usual round of image updates, as well as a small improvement to the Operator itself: It now respects the zap-log-level argumen
This release brings the usual round of image updates, as well as a small improvement to the Operator itself: It now respects the zap-log-level argument (as set via the operator.args.zapLogLevel Helm value) when logging.
zap-log-level flag.Nothing published for this version
Nothing published for this version
This release brings a new LINSTOR and DRBD release, with other small fixes along the way.
This release brings a new LINSTOR and DRBD release, with other small fixes along the way.
Notable changes include:
controllerStrategy option on the LinstorCSIDriver resource allows fine tuning the deployment strategy.controllerStrategy to describe how to replace existing pods with new ones for csi-controllerNothing published for this version
This release brings a new LINSTOR version and an updated CSI driver. There are no substantial changes in the operator itself, the changes are all part
This release brings a new LINSTOR version and an updated CSI driver. There are no substantial changes in the operator itself, the changes are all part of the updated images:
k8s.gcr.io to registry.k8s.ioNothing published for this version
This is the final release of 1.10.0. In the long phase between RC.1 and this released, a lot of work was happening on the LINSTOR side.
This is the final release of 1.10.0. In the long phase between RC.1 and this released, a lot of work was happening on the LINSTOR side.
Other than that, this release contains a few small improvements with regards to IPv6 based setups, as well as an option to share DRBD configuration between host and container.
mountDrbdResourceDirectoriesFromHost in the Helm chart to create hostPath Volumes for DRBD and LINSTOR configuration directories for the satellite set.[::]. This will still to work on IPv4
only systems with IPv6 disabled via sysctl.Nothing published for this version
This release brings the usual updates to container images, notably the new LINSTOR 1.20.0 RC. Other than that, there is a small fix to restoring evict
This release brings the usual updates to container images, notably the new LINSTOR 1.20.0 RC. Other than that, there is a small fix to restoring evicted nodes.
Nothing published for this version
Nothing published for this version
Right after releasing 1.9.0, we noticed that some resources were not cleanly upgraded. There was an issue in the way certain resources were patched on
Right after releasing 1.9.0, we noticed that some resources were not cleanly upgraded. There was an issue in the way certain resources were patched on upgrade. So now it's already time for 1.9.1, which fixes this issue and allows for a clean upgrade.
Nothing published for this version
In this release we focused on general imrovements, including the usual round of version updates.
In this release we focused on general imrovements, including the usual round of version updates.
We'd also like to announce two additions to the Piraeus Project in general that might be of interest to the community:
values.yaml.last-applied-configuration annotation was never updated, so updating of some fields was not performed correctly.Nothing published for this version
Nothing published for this version
Another small update, since LINSTOR released another bug-fix release.
Another small update, since LINSTOR released another bug-fix release.
Apart from updated images, this release features initial support for extending existing pods with custom sidecar containers. Examples include configurating kube-rbac-proxy for the metrics endpoints.
csi.controllerSidecars, csi.controllerExtraVolumes, csi.nodeSidecars, csi.nodeExtraVolumes,
operator.controller.sidecars, operator.controller.extraVolumes, operator.satelliteSet.sidecars,
operator.satelliteSet.extraVolumes to allow specifying extra sidecar containers.operator.controller.httpBindAddress, operator.controller.httpsBindAddress,
operator.satelliteSet.monitoringBindAddress to allow specifying bind address.Nothing published for this version
This patch release mainly brings updated LINSTOR and DRBD images, as well as removal of the "backup nag" when upgrading the k8s backend. Please note t
This patch release mainly brings updated LINSTOR and DRBD images, as well as removal of the "backup nag" when upgrading the k8s backend. Please note that for upgrades from before 1.8.0, a manual backup of the k8s database is still needed.
We have also upgraded some internal dependencies that lead to frequent crashing of the operator, as well as upgrading some default tolerations to get them ready for Kubernetes 1.24.
--set IHaveBackedUpAllMyLinstorResources=true.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is the final release for the Operator 1.8.0 release. It includes some quality of life improvements and the usual update to components. There were
This is the final release for the Operator 1.8.0 release. It includes some quality of life improvements and the usual update to components. There weren't any big changes since the release candidate, so I'll just repeat the noteworthy changes since 1.7.0:
For those using the k8s database: On upgrade you will be prompted to create a database backup. LINSTOR 1.17.0 still had a lot of issues with the backend, so having a backup that you can roll back to is important. Once ready to upgrade, add
--set IHaveBackedUpAllMyLinstorResources=true
to the upgrade command. This check will be removed in a future release: the Operator will perform the necessary backup and store it in a kubernetes secret.
tar.gz. If the secret would get too big, the backup can be downloaded from
the operator pod.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is the first release candidate for the upcoming Operator 1.8.0 release. It includes some quality of life improvements and the usual update to com
This is the first release candidate for the upcoming Operator 1.8.0 release. It includes some quality of life improvements and the usual update to components.
A few things to note:
tar.gz. If the secret would get too big, the backup can be downloaded from
the operator pod.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release is mainly focused on cleaning up some bugs and small features.
This release is mainly focused on cleaning up some bugs and small features.
There are no additional upgrade steps necessary. If you are experimenting with the K8s backend, don't forget to create a backup of all internal resources.
operator.satelliteSet.kernelModuleInjectionAdditionalSourceDirectoryNothing published for this version
Nothing published for this version
One column per quarter.