This release brings two new features.
First, you can now restrict the IP address family used by the Operator to set up the Satellites. By default, the Operator will configure all .status.PodIPs, which in dual stack cluster contains both IPv4 and IPv6 addresses. However, it turns out that users might have a broken IPv6 configuration, which may cause LINSTOR to try to connect to IPv6 when that is not available. Users can now limit the IP address family using the following configuration:
apiVersion: piraeus.io/v1
kind: LinstorSatelliteConfiguration
metadata:
name: ipv4-only
spec:
ipFamilies:
- IPv4Second, the LINSTOR Satellite now tries to detect the host's LVM configuration on start up, reusing locks and udev rules if available. This fixes a long-standing issue where certain device links would disappear during resizes, leading to all kinds of errors on the LINSTOR side.
On the image front, the new LINSTOR 1.29.2 image includes a better backup mechanism for the LINSTOR database, so manual oversight should no longer be required in larger clusters.
Added
- Option to select IP Family to use for LINSTOR control traffic.
Changed
- Reconciliation of a Satellites network interfaces now also deletes unneeded interfaces.
- Satellites try to detect the LVM configuration on the host, reusing locks and udev rules if available.
- Updated images:
- LINSTOR 1.29.2
- LINSTOR CSI 1.6.4
- DRBD Reactor 1.5.0
- LINSTOR HA Controller 1.2.2