We've just released a small bug fix for our Kubernetes Operator.
The three issues fixed are:
* A bug preventing the operator from making progress when running in a
cluster with Cluster API labels, but without the Cluster API CRDs
deployed
* A bug that caused excessive load on the Operator by repeatedly
updating the status conditions.
* A bug preventing the snapshot creation on clusters without
VolumeGroupSnapshot resources deployed.
We recommend all users of release 2.10.0 to update to this latest release.
To upgrade, either point your kustomization.yaml at the new manifest:
https://charts.linstor.io/static/v2.10.1.yaml
Or, if using helm, upgrade the linstor-operator chart:
helm repo update
helm upgrade linstor-operator linstor/linstor-operator --wait
To get specific instructions to apply the update, check our users guide[1].
If you need to upgrade from Operator v1, check out our upgrade guide[2].
Source code is, as always, available upstream[3].
Best regards,
Moritz
[1]: LINSTOR 1.0 en - LINBIT
[2]: Migrating to Operator V2
[3]: GitHub - piraeusdatastore/piraeus-operator: The Piraeus Operator manages LINSTOR clusters in Kubernetes.