feat: use raw metrics over recording rule rollout#4329
Open
sidtuladhar wants to merge 7 commits into
Open
Conversation
sidtuladhar
changed the title
The system paasta config call added in d8bfaf8 requires /etc/paasta/ which doesn't exist in CI.
nemacysts
reviewed
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The worker-load HPA formula uses a
missing_instancesterm (pods with no worker_busy data, assumed at 100% load) to account for pods that haven't reported metrics yet.When pods disappear,
worker_busydrops immediately but the recording rulek8s:deployment:pods_status_readygoes stale so pods start to appear missing and are assumed 100% load, causing the HPA to scale up.This PR switches to raw kube-state-metric metrics so both sides reflect current state, which prevents any staleness and the HPA doesn't create phantom pods.