big size node memory cause metrics overflow

[leiwingqueen]

What happened:

I have a machine with big memory (about 10000TB size) will get a negative number in metrics. I found that the node metrics value do the convert as float64(val.MilliValue()) / 1000 before return. It may overflow when the value is bigger than maxInt64/1000.

What you expected to happen:

KSM will return the correct number even when the value is bigger than maxInt64/1000

How to reproduce it (as minimally and precisely as possible):

node memory size is larger than maxInt64/1000

Anything else we need to know?:

Environment:

• kube-state-metrics version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• Other info:

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[CatherineF-dev]

/close #2540