Cherry-pick #23335 to 7.x: Fix types for response fields of kubelet api #23383
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.
Cherry-pick of PR #23335 to 7.x branch. Original message:
What does this PR do?
This PR adjusts the types of the response fields from Kubelet
stats/summary
api so as to be consistent with the original types of the fields as defined on api's side: https://github.com/kubernetes/kubelet/blob/088ee84ea259bf9c445109ea75b2938dd39d2074/pkg/apis/stats/v1alpha1/types.goWhy is it important?
To avoid hitting integer overflow since we store as
int64
while the api can serve values stored asuint64
.int64
: -9223372036854775808 to 9223372036854775807uint64
: 0 to 18446744073709551615Closes #19475