Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Cant retrieve metrics from Kubernetes kind's #200

Open
mustafataskir-bcfm opened this issue Jan 22, 2024 · 1 comment
Open

Cant retrieve metrics from Kubernetes kind's #200

mustafataskir-bcfm opened this issue Jan 22, 2024 · 1 comment

Comments

@mustafataskir-bcfm
Copy link

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
Copy link
Author

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant