Skip to content

v0.0.20
Compare
Choose a tag to compare
@dinogun dinogun released this 07 Nov 10:27
· 1120 commits to master since this release
v0.0.20
da75ffe
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Kruize Version 0.0.20_rm released!

You can get it from
docker pull docker.io/kruize/autotune_operator:0.0.20_rm
docker pull quay.io/kruize/autotune_operator:0.0.20_rm
Commit id: da75ffe66d1677375167a9c88046b0dbaadf41ac

Release Changelog

[API] V2 of the API, updates the listRecommendations / updateRecommendations API JSON to add the new recommendations profile.
[Deploy] No updates
[UI] A new version of the Kruize UI (0.0.3) has been released that supports the new recommendation profiles.
[DB] No updates
[Workflow] No updates
[Recommendations] update_recommendations JSON has been updated to add “cost” and “performance” recommendation engines.
[Recommendations] The definition of the two recommendation engines (or profiles) is documented here.
[Test] Test automation improvements
[Test] Running tests through comments
[Test] Script to grab Kruize metrics from prometheus
[Bug] Better validation of updtes_results params
Full list of PRs can be found here.

The primary focus of this release is adding the recommendations profile. We now support two different recommendation “profiles”, cost and performance. Currently they only affect CPU recommendations alone. Cost recommendations correspond to the 60th percentile of the CPU usage, while the performance profile recommendations correspond to the 98th percentile of CPU usage for the related container.

Assets 2
Loading