Closed marquiz closed 10 months ago
Drafted a changelog. PTAL @klihub @kad @askervin
@marquiz , looks great to me! Thank you!
LGTM. one small addition: for CRI v1alpha2 deprecation, minimal version of cri-o also should be mentioned.
LGTM. one small addition: for CRI v1alpha2 deprecation, minimal version of cri-o also should be mentioned.
Added.
Container event relaying was implemented. Let's tag? 🕺
GitHub release page: https://github.com/intel/cri-resource-manager/releases/tag/v0.9.0
Release Process
make release-tests
to run an extended set of tests prior to a release.git tag -a -m "CRI Resource Manager release $VERSION" $VERSION
.make vendored-dist
.git push $VERSION
.What's Changed
New dynamic-pools policy
A new policy that allows applications to be assigned to dynamically resized CPU pools. The pools are non-overlapping and are resized based on the resource requests of the containers and the actual CPU utilization of the application.
Enhancements to balloons policy
New PreferSpreadOnPhysicalCores configuration option in the balloons policy. Enabling this option for a balloon makes the CPU allocator to prefer CPUs from separate physical CPU cores.
There are also bugfixes to dynamic configuration updates.
Config status
Configuration status (was the configuration successfully applied or not) is now exposed via readiness probe of the cri-resmgr-agent. (#986)
CRI v1alpha2 dropped
Support for deprecated CRI version v1alpha2 was removed. This means that CRI-RM v0.9 requires Kubernetes v1.23 (or later) and containerd v1.6 (or later) or CRI-O v1.20 (or later).
Bugfixes
List of PRs
New Contributors
Full Changelog: https://github.com/intel/cri-resource-manager/compare/v0.8.0...v0.9.0