fix limit and request availability with -a with json and yaml #174
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.
Closes #92
Add Available Resources to JSON/YAML Output
Description
Currently, when using the
-aflag with JSON/YAML output formats, the available resources are not displayed in a clear format. This PR adds new fieldsrequestsAvailableandlimitsAvailableto show available resources explicitly while maintaining backward compatibility.Changes
requestsAvailableandlimitsAvailableto listResourceOutput struct-aflagExamples
Without
-aflag (unchanged):{ "nodes": [ { "name": "minikube", "cpu": { "requests": "1350m", "requestsPercent": "11%", "limits": "700m", "limitsPercent": "5%" }, "memory": { "requests": "522Mi", "requestsPercent": "6%", "limits": "362Mi", "limitsPercent": "4%" } } ] } ### With `-a` flag (unchanged): { "nodes": [ { "name": "minikube", "cpu": { "requests": "1350m", "requestsPercent": "11%", "requestsAvailable": "10650m", "limits": "700m", "limitsPercent": "5%", "limitsAvailable": "11300m" }, "memory": { "requests": "522Mi", "requestsPercent": "6%", "requestsAvailable": "7315Mi", "limits": "362Mi", "limitsPercent": "4%", "limitsAvailable": "7475Mi" } } ] }