search

robusta-dev / krr

Prometheus-based Kubernetes Resource Recommendations
MIT License
3.05k stars 160 forks source link

Cant retrieve metrics from Kubernetes kind's #200

Open mustafataskir-bcfm opened 10 months ago

mustafataskir-bcfm commented 10 months ago

I have a Kubernetes cluster installed on AWS EKS version 1.25. I installed krr on my local computer with brew. I am publishing the Prometheus service with port forwarding, and while krr reports that it is connected, I am receiving the following errors.

krr simple -n monitoring --history_duration 10

| \ | | | | | |/ / | \ | |) |_ | |_ | |_ | ' /| |) | |) | | // | ' | | | / | / ` | | < | /| / | | \ \ () | |) | || _ \ || (| | | . | | \ | | \ \ || _\/|./ \,|/\_,| ||__| __| _\

Running Robusta's KRR (Kubernetes Resource Recommender) v1.6.0 Using strategy: Simple Using formatter: table

[INFO] Using clusters: ['cluster-name'] on 0: [INFO] Listing scannable objects in cluster-name on 0: [INFO] Connecting to Prometheus for cluster-name cluster on 0: [INFO] Using Prometheus at https://xxxxxxxxxxxxxx.gr7.xx-xxxx-x.eks.amazonaws.com/api/v1/namespaces/monitoring/services/prometheus-server:80/proxy for cluster cluster-name on 0: [INFO] Prometheus found on 0: [INFO] Prometheus connected successfully for cluster-name cluster on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for DaemonSet monitoring/prometheus-node-exporter/prometheus-node-exporter on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager-configmap-reload on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for Deployment monitoring/prometheus-msteams/prometheus-msteams on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for DaemonSet monitoring/prometheus-node-exporter/prometheus-node-exporter on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for Deployment monitoring/prometheus-server/prometheus-server on 0: [WARNING] Prometheus returned no PercentileCPULoader metrics for Deployment monitoring/prometheus-server/prometheus-server-configmap-reload on 0: [WARNING] Prometheus returned no CPUAmountLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager-configmap-reload on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for Deployment monitoring/prometheus-msteams/prometheus-msteams on 0: [WARNING] Prometheus returned no CPUAmountLoader metrics for DaemonSet monitoring/prometheus-node-exporter/prometheus-node-exporter on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for Deployment monitoring/prometheus-server/prometheus-server on 0: [WARNING] Prometheus returned no MaxMemoryLoader metrics for Deployment monitoring/prometheus-server/prometheus-server-configmap-reload on 0: [WARNING] Prometheus returned no MemoryAmountLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager on 1: [WARNING] Prometheus returned no CPUAmountLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager-configmap-reload on 1: [WARNING] Prometheus returned no CPUAmountLoader metrics for Deployment monitoring/prometheus-msteams/prometheus-msteams on 1: [WARNING] Prometheus returned no MemoryAmountLoader metrics for DaemonSet monitoring/prometheus-node-exporter/prometheus-node-exporter on 2: [WARNING] Prometheus returned no CPUAmountLoader metrics for Deployment monitoring/prometheus-server/prometheus-server on 2: [WARNING] Prometheus returned no CPUAmountLoader metrics for Deployment monitoring/prometheus-server/prometheus-server-configmap-reload on 2: [WARNING] Prometheus returned no MemoryAmountLoader metrics for Deployment monitoring/prometheus-alertmanager/prometheus-alertmanager-configmap-reload on 3: [WARNING] Prometheus returned no MemoryAmountLoader metrics for Deployment monitoring/prometheus-msteams/prometheus-msteams on 4: [WARNING] Prometheus returned no MemoryAmountLoader metrics for Deployment monitoring/prometheus-server/prometheus-server on 4: [WARNING] Prometheus returned no MemoryAmountLoader metrics for Deployment monitoring/prometheus-server/prometheus-server-configmap-reload Calculating Recommendation |████████████████████████████████████████| 6 in 3.7s (1.02/s)

The values in the table also appear as 'unset'.

image

Where am I making a mistake?

mustafataskir-bcfm commented 10 months ago

Additionally, when I scan a namespace with defined request-limit, it shows the existing resource values but does not provide any recommendations. I am receiving the same warning logs.