Repository navigation
Conversation
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
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.
Missing or stale Kata readings must not become zero usage in autoscaling decisions. Return a Pod's metrics only when every declared container has complete, valid, recent measurements for its current identity. Reject duplicates and retired containers. Query updates automatically restart the adapter.
Validation: 33 promtool scenarios cover missing containers, stale collection, replacement, invalid or duplicate readings, and genuine zero usage. The adapter overlay renders; CI runs these regressions.
Rollout order: infra #6854 → Kata provider #39 → this change. Kata metrics are unavailable until the prerequisites arrive. The API timestamp remains query time; freshness is checked separately.
Related to datum-labs/kata-provider#32 and datum-cloud/enhancements#919.