[Bug] No request or usage data found during CPU allocation calculation. Setting allocation to 0.

[philcz16]

Kubecost Helm Chart Version

1.106.7

Kubernetes Version

1.24

Kubernetes Platform

EKS

Description

I've been getting these warnings in my cost-model container and these are repeated after couple of minutes. 2024-02-23T15:51:15.45901507Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0. 2024-02-23T15:51:15.459065434Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.

Steps to reproduce

1. Install Kubecost using helm on EKS
2. Check kubecost logs kubectl logs kubecost-cost-analyzer-<your-pod-extension> -n kubecost -c cost-model

Expected behavior

I will like to know whether these warning can be ignored or is there a more serious configuration issue? Can there warning be suppressed if this isn't an issue?

Impact

No response

Screenshots

No response

Logs

2024-02-23T16:01:23.25664393Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.256688319Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.256728459Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.256791063Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.257049041Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.257098961Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.257132921Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.
2024-02-23T16:01:23.257174598Z WRN No request or usage data found during CPU allocation calculation. Setting allocation to 0.

Slack discussion

No response

Troubleshooting

• [X] I have read and followed the issue guidelines and this is a bug impacting only the Helm chart.
• [X] I have searched other issues in this repository and mine is not recorded.

[AjayTripathy]

Hi @philcz16 Can you share information from the Prometheus Metrics section in the /diagnostics page? This could happen if kubecost isn't properly being scraped by prometheus.

[chipzoller]

Closed by https://github.com/opencost/opencost/pull/2715