Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(helm): update chart descheduler to 0.31.0 #1324

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 8, 2024

This PR contains the following updates:

Package Update Change
descheduler minor 0.29.0 -> 0.31.0

Release Notes

kubernetes-sigs/descheduler (descheduler)

v0.31.0

Compare Source

Descheduler for Kubernetes is used to rebalance clusters by evicting pods that can potentially be scheduled on better nodes. In the current implementation, descheduler does not schedule replacement of evicted pods but relies on the default scheduler for that.

v0.30.1: Descheduler v0.30.1

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/descheduler@v0.30.0...v0.30.1

v0.30.0: Descheduler v0.30.0

Compare Source

What's Changed

New Contributors

Full Changelog: kubernetes-sigs/descheduler@v0.29.0...v0.30.0


Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title feat(helm): update chart descheduler to 0.30.1 feat(helm): update chart descheduler to 0.31.0 Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants