`/proxy/stats/summary` returning incorrect PVC capacity bytes

What happened:

When querying kubectl get --raw /api/v1/nodes/<node-ip>/proxy/stats/summary, the capacity bytes returned for PVCs are not what are shown in tools like k9s which therefore tell me that tooling built around this endpoint will show incorrect values.

What you expected to happen:

PVC capacity and other metrics show the correct sizes

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

$ kubectl get --raw "/api/v1/nodes/ip-<>.ec2.internal/proxy/stats/summary"
...
        {
          "time": "2024-09-30T18:27:06Z",
          "availableBytes": 467653439488,
          "capacityBytes": 1623168045056,
          "usedBytes": 1155497828352,
          "inodesFree": 100516333,
          "inodes": 100663296,
          "inodesUsed": 146963,
          "name": "pvc-data",
          "pvcRef": {
            "name": "name-pvc",
            "namespace": "namespace-pvc"
          }
        },
...

Take capacity bytes, convert to GiB/MiB, compare with k9s or other tooling for spec.resources.requests.storage

I used: kubectl get pvc name-pvc -o json to get the spec requests to compare against (which was larger by 125 MiB):

    },
    "spec": {
        "accessModes": [
            "ReadWriteOnce"
        ],
        "resources": {
            "requests": {
                "storage": "9600Gi"
            }
        },

Anything else we need to know?:

Environment:

kube-state-metrics version:
Kubernetes version (use kubectl version): v1.27.14
Cloud provider or hardware configuration: AWS EKS
Other info:

kubernetes / kube-state-metrics

`/proxy/stats/summary` returning incorrect PVC capacity bytes #2516