piraeusdatastore/piraeus-operator v1.2.0

on GitHub

The newest release brings updated default images, better integration with pod security policies and, perhaps most important of all: the ability to use helm upgrade to update to a new Piraeus version and change settings. See the upgrade guide

Added

• storagePools can now also set up devices similar to automaticStorageType, but with more fine grained control.
  See the updated storage guide
• New Helm options to disable creation of LinstorController and LinstorSatelliteSet resource
  operator.controller.enabled and operator.satelliteSet.enabled.
• New Helm option to override the generated controller endpoint: controllerEndpoint
• Allow overriding the default securityContext on a component basis:
  • etcd.podsecuritycontext sets the securityContext of etcd pods
  • stork.podsecuritycontext sets the securityContext of stork plugin and scheduler pods
  • csi-snapshotter.podsecuritycontext sets the securityContext of the CSI-Snapshotter pods
  • operator.podsecuritycontext sets the securityContext of the operator pods
• Example settings for openshift
• LINSTOR controller runs with additional GID 1000, to ensure write access to log directory

Changed

• Fixed a bug in pv-hostpath where permissions on the created directory are not applied on all nodes.
• Volumes created by pv-hostpath are now group writable. This makes them easier to integrate with fsGroup settings.
• Default value for affinity on LINSTOR controller and CSI controller changed. The new default is to distribute the pods
  across all available nodes.
• Default value for tolerations for etcd pods changed. They are now able to run on master nodes.
• Updates to LinstorController, LinstorSatelliteSet and LinstorCSIDriver are now propagated across all created resources
• Updated default images:
  • csi sidecar containers updated (compatible with Kubernetes v1.17+)
  • LINSTOR 1.10.0
  • LINSTOR CSI 0.10.0

Deprecation

• Using automaticStorageType is deprecated. Use the storagePools values instead.