Tool is showing unset for all resources for most namespaces

[bmaupin]

I'm not a kubernetes expert at all, so maybe we're doing this incorrectly. We have the following LimitRange set by default for most of our namespaces:

  - kind: LimitRange
    apiVersion: v1
    metadata:
      name: "core-resource-limits"
      namespace: ...
    spec:
      limits:
        - type: "Container"
          max:
            memory: "1Gi"
          defaultRequest:
            cpu: "5m"
            memory: "128Mi"

The deployed pods have resources accordingly set, e.g.

  containers:
    - resources:
        limits:
          memory: 1Gi
        requests:
          cpu: 5m
          memory: 128Mi

However, when we run this tool, it says "unset" for CPU/memory requests/limits.

For comparison, I found another namespace where only one of the containers showed unset:

The only difference I can tell between the second example and the ones that aren't working is that the ones that are showing "unset" for all values don't have CPU limits set, as per https://home.robusta.dev/blog/stop-using-cpu-limits

The closest issue I found was this one: #200

But we're not using AWS and we're not getting any warnings. We just get messages like this for the projects that are showing unset:

INFO     Calculated recommendations for Deployment appdev-ci-pipeline-development/development/auto-deploy-app (using 4 metrics)

Using krr v1.17.0 installed with brew

Run with WSL 2 on Windows 11

Linux ub 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Thanks!