This repository was archived by the owner on May 7, 2026. It is now read-only.
REP-1722: Expose allocatable storage from node#626
Open
krystiancastai wants to merge 2 commits into
Open
Conversation
krystiancastai
force-pushed
the
REP-1772
branch
from
b979e60 to
9869293
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Added node-level storage fields (NodeFsCapacityBytes, NodeFsAllocatableBytes) to NodeStatsSummaryMetric.
Capacity is the sum of well-known storage paths deduplicated by device ID.
Allocatable follows Kubernetes calculation:
allocatable = capacity - nodefs eviction threshold - kube-reserved ephemeral-storage - system-reserved ephemeral-storage