NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #2407 by repository stars
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
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
pv-hostpath: automatically determine on which nodes PVs should be created if no override is given.
pv-hostpath: automatically determine on which nodes PVs should be created if no override is given.replicasOnSame: topology.kubernetes.io/zone.k8s backend by adding the necessary RBAC resources and documentation.quay.io/piraeusdatastore/piraeus-server:v1.17.0quay.io/piraeusdatastore/piraeus-csi:v0.17.0quay.io/piraeusdatastore/drbd9-bionic:v9.1.4quay.io/piraeusdatastore/drbd-reactor:v0.4.4volumeBindingMode: WaitForFirstConsumer.volumeBindingMode: WaitForFirstConsumer in storage classes.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
Allow CSI to work with distributions that use a kubelet working directory other than /var/lib/kubelet. See the `csi.kubeletPath` option.
/var/lib/kubelet. See
the csi.kubeletPath option.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.0quay.io/piraeusdatastore/drbd9-bionic:v9.0.30quay.io/piraeusdatastore/drbd-reactor:v0.4.3quay.io/piraeusdatastore/piraeus-ha-controller:v0.2.0The 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.
Nothing published for this version
Nothing published for this version
### Changed - Default images: * Piraeus Server v1.13.0 * Piraeus CSI v0.13.1 * CSI Provisioner v2.1.2
Nothing published for this version
Nothing published for this version
External: CSI snapshotter subchart now packages v1 CRDs. Fixes deprecation warnings when installing the snapshot controller.
drbd-reactor to expose Prometheus endpoints on each satellite.ServiceMonitor resources if they are supported by the cluster (i.e. prometheus operator is configured)hostNetwork: true. The pods already got the correct hostname via the downwardAPI and do not
talk to DRBD's netlink interface directly.v1 CRDs. Fixes deprecation warnings when installing
the snapshot controller.Nothing published for this version
Additional environment variables and Linstor properties can now be set in the LinstorController CRD.
LinstorController CRD.New guide on host preparation here.
operator.satelliteSet.kernelModuleInjectionImage: quay.io/piraeusdatastore/drbd9-bionic:v9.0.27operator.satelliteSet.satelliteImage: quay.io/piraeusdatastore/piraeus-server:v1.11.1operator.controller.controllerImage: quay.io/piraeusdatastore/piraeus-server:v1.11.1haController.image: quay.io/piraeusdatastore/piraeus-ha-controller:v0.1.3pv-hostpath: chownerImage: quay.io/centos/centos:8New component: haController will deploy the [Piraeus High Availability Controller]. More information is available in the optional components page
haController will deploy the Piraeus High Availability Controller.
More information is available in
the optional components pagepv-hostpath chart by using --set chownerImage=<my-image>.operator-sdk to v0.19.4operator.controller.controllerImage: quay.io/piraeusdatastore/piraeus-server:v1.11.0operator.satelliteSet.satelliteImage: quay.io/piraeusdatastore/piraeus-server:v1.11.0operator.satelliteSet.kernelModuleInjectionImage: quay.io/piraeusdatastore/drbd9-bionic:v9.0.26csi.pluginImage: quay.io/piraeusdatastore/piraeus-csi:v0.11.0Using automaticStorageType is deprecated. Use the storagePools values instead.
storagePools can now also set up devices similar to automaticStorageType, but with more fine grained control.
See the updated storage guideoperator.controller.enabled and operator.satelliteSet.enabled.controllerEndpointsecurityContext on a component basis:
etcd.podsecuritycontext sets the securityContext of etcd podsstork.podsecuritycontext sets the securityContext of stork plugin and scheduler podscsi-snapshotter.podsecuritycontext sets the securityContext of the CSI-Snapshotter podsoperator.podsecuritycontext sets the securityContext of the operator podspv-hostpath where permissions on the created directory are not applied on all nodes.pv-hostpath are now group writable. This makes them easier to integrate with fsGroup settings.automaticStorageType is deprecated. Use the storagePools values instead.The LINSTOR controller image given in operator.controller.controllerImage has to have its entrypoint set to `k8s-await-election v0.2.0` or newer. Lear
operator.controller.controllerImage has to have
its entrypoint set to k8s-await-election v0.2.0
or newer. Learn more in the upgrade guide.operator.controller.replicas.
NOTE: This requires support from the container. You need piraeus-server:v1.8.0 or newer.pv-hostpath helper chart automatically sets up permissions for non-root etcd containers.global.setSecurityContext=false.csi.enableTopology.psp.* can automatically configure the ServiceAccount
of all components to use the appropriate PSP roles.operator.controller.controllerImage: quay.io/piraeusdatastore/piraeus-server:v1.9.0operator.satelliteSet.satelliteImage: quay.io/piraeusdatastore/piraeus-server:v1.9.0operator.satelliteSet.kernelModuleInjectionImage: quay.io/piraeusdatastore/drbd9-bionic:v9.0.25stork.storkImage: docker.io/openstorage/stork:2.5.0v1alpha CRD versions have been removed.drbdiocred removed. To keep using it, use --set drbdRepoCred=drbdiocred.Central value for controller image pull policy of all pods. Use --set global.imagePullPolicy= on helm deployment.
v1 of all CRDs--set global.imagePullPolicy=<value> on
helm deployment.charts/piraeus/values.cn.yaml a set of helm values for faster image download for CN users.etcd.resources for etcd containersstork.storkResources for stork plugin resourcesstork.schedulerResources for the kube-scheduler deployed for use with storkcsi-snapshotter.resources for the cluster snapshotter controllercsi.resources for all CSI related containers. for brevity, there is only one setting for ALL CSI containers.
They
are all stateless go process which use the same amount of resources.operator.resources for operator containersoperator.controller.resources for LINSTOR controller containersoperator.satelliteSet.resources for LINSTOR satellite containersoperator.satelliteSet.kernelModuleInjectionResources for kernel module injector/builder containersetcd => set etcd.replicas to the desired countstork => set stork.replicas to the desired count for stork scheduler and controllersnapshot-controller => set csi-snapshotter.replicas to the desired count for cluster-wide CSI snapshot
controllercsi-controller => set csi.controllerReplicas to the desired count for the linstor CSI controlleroperator => set operator.replicas to have multiple replicas of the operator runningstork.schedulerTag can override the automatically chosen tag for the kube-scheduler image.
Previously, the tag always matched the kubernetes release.LinstorNodeSet to LinstorSatelliteSet. This brings the operator in line with other LINSTOR resources.
Existing LinstorNodeSet resources will automatically be migrated to LinstorSatelliteSet.LinstorControllerSet to LinstorController. The old name implied the existence of multiple (separate)
controllers. Existing LinstorControllerSet resources will automatically be migrated to LinstorController.operator.controllerSet to operator.controlleroperator.nodeSet to operator.satelliteSetlinstor.linbit.com/piraeus-node labels. Instead, all CRDs support
setting pod affinity and tolerations.
In detail:
linstorcsidrivers gained 4 new resource keys, with no change in default behaviour:
nodeAffinity affinity passed to the csi nodesnodeTolerations tolerations passed to the csi nodescontrollerAffinity affinity passed to the csi controllercontrollerTolerations tolerations passed to the csi controllerlinstorcontrollerset gained 2 new resource keys, with no change in default behaviour:
affinity affinity passed to the linstor controller podtolerations tolerations passed to the linstor controller podlinstornodeset gained 2 new resource keys, with change in default behaviour:
affinity affinity passed to the linstor controller podtolerations tolerations passed to the linstor controller podkernelModImage to kernelModuleInjectionImagedrbdKernelModuleInjectionMode to KernelModuleInjectionModeNothing published for this version
Nothing published for this version
Add new kmod injection mode DepsOnly. Will try load kmods for LINSTOR layers from the host. Deprecates None.
Support volume resizing with newer CSI versions.
A new Helm chart csi-snapshotter that deploys extra components needed for volume snapshots.
Add new kmod injection mode DepsOnly. Will try load kmods for LINSTOR layers from the host. Deprecates None.
Automatic deployment of Stork scheduler configured for LINSTOR.
bitnami/etcd dependency with vendored custom version
Some important keys for the etcd helm chart have changed:
statefulset.replicaCount -> replicaspersistence.enabled -> persistentVolume.enabledpersistence.size -> persistentVolume.storageàuth.rbac was removed: use tls certificatesauth.peer.useAutoTLS was removedenvVarsConfigMap was removed*.<release-name>-etcd (was
.<release-name>>-etcd-headless.<namespace>.svc.cluster.local)*.<release-name>-etcd (was
.<release-name>>-etcd.<namespace>.svc.cluster.local)Nothing published for this version
Automatic storage pool creation via automaticStorageType on LinstorNodeSet. If this option is set, LINSTOR will create a storage pool based on all ava
automaticStorageType on LinstorNodeSet. If this option is set, LINSTOR
will create a storage pool based on all available devices on a node.Secured database connection for Linstor: When using the etcd connector, you can specify a secret containing a CA certificate to switch from HTTP to HT
etcd connector, you can specify a secret containing a CA
certificate to switch from HTTP to HTTPS communication.piraeus-op-ns) was replaced by the ControllerSet service (piraeus-op-cs) everywherecsi.image was renamed to csi.pluginImagelinstorcsidrivers.piraeus.linbit.comNothing published for this version
Use single values for images in CRDs instead of specifying the version separately
operator.nodeSet.spec and operator.controllerSet.spec by
just operator.nodeSet and operator.controllerSet.Fix reporting of errors in LinstorControllerSet status
Helm: Update LINSTOR server dependencies to fix startup problems
Helm: Allow an existing database to be used instead of always setting up a dedicated etcd instance
etcdURL parameter of LinstorControllerSet to dbConnectionURL to
reflect the fact that it can be used for any database typepv-hostchart installationHelm: Add support for hostPath PersistentVolume persistence of etcd
hostPath PersistentVolume persistence of etcdNothing published for this version
Initial public version with docs
Your coding agent can read these notes before it upgrades. Set up the MCP server →