Kubernetes resource.Quantity methods like Value() silently overflow and wrap on int64 limits, causing incorrect negative values for large resource amounts, impacting components like the kubelet.

Existing Quantity accessors returned int64 values that wrapped on overflow without indication, leading to invalid negative values when resource amounts exceeded int64 bounds.

Introduced AsScaledInt64(scale) and AsMilliInt64() methods that return a boolean indicating success and saturate values to int64 min/max instead of wrapping. Updated existing wrappers to use these saturating methods, and fixed kubelet CPU reservation parsing to avoid negative wraparound.

APIs returning numeric resource values should signal overflow and saturate to prevent subtle bugs from silent wrapping; callers must still handle bounds explicitly when combining values.