Releases: piraeusdatastore/nri-volume-qos
Releases · piraeusdatastore/nri-volume-qos
Release list
v0.1.3
v0.1.2
This release publishes a helm chart at oci://ghcr.io/piraeusdatastore/nri-volume-qos.
Added
- Helm chart under
charts/nri-volume-qosfor deploying the plugin as a DaemonSet, with configurable image, host paths, RBAC, scheduling, and NRI plugin settings. - On each published release, the chart is packaged and pushed as an OCI artifact to
ghcr.io/piraeusdatastore/nri-volume-qos.
Changed
deploy/daemonset.yamlno longer tolerates all taints; it now relies on the default DaemonSet tolerations, so it no longer schedules onto control-plane or custom-tainted nodes unless tolerations are added.
v0.1.1
Some internal improvements so that other packages can consume the limits API.
v0.1.0
The very first release of this new project, aiming to solve a long standing gap in Kubernetes: there was no way to enforce IO limits on a per-volume level, outside of cloud providers that enforce those limits at the hypervisor level.
With this project, any CSI plugin that attaches and/or mounts a device can support IO limits, by setting a few well known markers on the volume attachment. The NRI plugin then translates these markers into actual cgroup limits enforced by the container runtime.
Added
- Initial implementation: an NRI plugin that enforces per-volume IO limits (read/write bandwidth and IOPS) on Kubernetes containers via the Linux cgroup v2
io.maxinterface, driven by QoS metadata on CSIVolumeAttachments. Supports both filesystem and raw block volumes, and runs as a DaemonSet on containerd 1.7+ and CRI-O 1.26+. - Multi-arch (linux/amd64, linux/arm64) container images, signed with cosign keyless signing and published from GitHub Actions.