Skip to content

v1.6.0
Compare
Choose a tag to compare
@WanzenBug WanzenBug released this 02 Sep 12:34
· 182 commits to master since this release
v1.6.0
This tag was signed with the committer’s verified signature.
WanzenBug Moritz Wanzenböck
GPG key ID: 17A456B9520BB5C8
Learn about vigilant mode.
bbe2735

This release brings some new and exciting features:

  • All images should now also be available for arm64 in addition to amd64.
  • Piraeus is now compatible with Kubernetes v1.22. Note that this does not extend to some external components (notably: STORK), which require additional updates. For now we recommend disabling STORK on v1.22.
  • You can enable CSI storage capacity tracking.
  • We improved support for deploying the CSI Snapshot Controller. As such, it was moved into a separate chart.

Detailed instructions on how to upgrade can be found in the upgrade guide

IMPORTANT

  • Piraeus Operator now requires Kubernetes 1.19+

Added

  • Allow CSI to work with distributions that use a kubelet working directory other than /var/lib/kubelet. See
    the csi.kubeletPath option.
  • Enable Storage Capacity Tacking. This enables Kubernetes to base Pod scheduling decisions on remaining storage
    capacity. The feature is in beta and enabled by default starting with Kubernetes 1.21.

Changed

  • Disable Stork Health Monitoring by default. Stork cannot distinguish between control plane and data plane issues,
    which can lead to instances where Stork will migrate a volume that is still mounted on another node, making the
    volume effectively unusable.

  • Updated operator to kubernetes v1.21 components.

  • Default images:

    • quay.io/piraeusdatastore/piraeus-server:v1.14.0
    • quay.io/piraeusdatastore/drbd9-bionic:v9.0.30
    • quay.io/piraeusdatastore/drbd-reactor:v0.4.3
    • quay.io/piraeusdatastore/piraeus-ha-controller:v0.2.0
    • external CSI images

Removed

  • The cluster-wide snapshot controller is no longer deployed as a dependency of the piraeus-operator chart.
    Instead, separate charts are available on artifacthub.io
    that deploy the snapshot controller and extra validation for snapshot resources.

    The subchart was removed, as it unnecessarily tied updates of the snapshot controller to piraeus and vice versa. With
    the tightened validation starting with snapshot CRDs v1, moving the snapshot controller to a proper chart seems
    like a good solution.

Assets 2
Loading