Skip to content

Fix snapshot memory quantity parsing - #72

Merged
PragalvaXFREZ merged 1 commit into
mainfrom
fix/snapshot-memory-quantity
Aug 17, 2026
Merged

PragalvaXFREZ merged 1 commit into
mainfrom
fix/snapshot-memory-quantity

Conversation

@PragalvaXFREZ

Copy link
Copy Markdown
Owner

Summary

  • parse Kubernetes node memory reported in bytes, Ki, Mi, Gi, or Ti
  • preserve the existing GiB output and rounding

Root cause

The publisher assumed every node capacity ended in Ki. After a reboot, Kubernetes canonically serialized the control-plane capacity as 3336Mi, causing jq to exit before publishing.

Validation

  • tested the converter against the live mixed-unit node capacities
  • tested bytes, Ki, Mi, Gi, and Ti inputs
  • validated the embedded shell syntax
  • kubeconform: 59 valid, 0 invalid, 0 errors, 4 skipped
  • git diff --check

Signed-off-by: Pragalva Sapkota <sapkotapragalva@gmail.com>
@PragalvaXFREZ
PragalvaXFREZ merged commit 1d4d01b into main Aug 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant