A release with breaking behavior for legacy V2 linked-clone volumes, a Kubernetes v1.25 minimum, and stronger default network controls, including expanded mTLS enforcement. It also adds V2 data engine capabilities and metrics while correcting defects across V2 operations, backups, expansion, and infrastructure.
Check if affected (6)
breakingInternal
NetworkPolicyresources enabled by defaultApplies if a
NetworkPolicyprovider is available in the cluster.Longhorn v1.12.1 enables ingress
NetworkPolicyresources by default for internal component endpoints and RPCs, including the instance-manager gRPC endpoint. The policies take effect only when aNetworkPolicyprovider is available, and the minimum required Kubernetes version is v1.25.breakingCross-namespace Prometheus scraper access through the Longhorn Manager network policy
Applies if you use cross-namespace Prometheus scrapers.
ServiceMonitordiscovery does not automatically authorize network traffic. Cross-namespace Prometheus scrapers might be blocked by the Longhorn Manager's network policy and require a scoped additive policy.breakingmTLS for all instance-manager gRPC services
Applies if you configure the
longhorn-grpc-tlssecret.When the
longhorn-grpc-tlssecret is configured, Longhorn v1.12.1 extends mTLS to all remaining instance-manager gRPC services, including the disk and SPDK services. Every instance-manager gRPC port then requires a valid client certificate.- + 3 more on the release page
Plan ahead (1)
deprecatedLegacy V2 linked-clone volumes deprecated
Applies if you use V2 linked-clone volumes created in v1.12.0 or earlier.
In v1.12.1, these volumes are legacy and can no longer be operated on except for detachment and deletion. Replacement linked-clone volumes can be created from the same source volumes without copying data.