Deploy Prometheus using HELM chart on EKS

Observability And Monitoring
#1

I cannot understand its me or there is limitation on EKS service in AWS Playground.

I have setup EKS cluster and install Prometheus using helm chart.
helm install prometheus prometheus-community/prometheus -n prometheus

But pods are not working fine.
rometheus prometheus-alertmanager-0 0/1 Pending 0 30s
prometheus prometheus-kube-state-metrics-7b97cb57c6-sw27t 1/1 Running 0 31s
prometheus prometheus-prometheus-node-exporter-chpmw 1/1 Running 0 31s
prometheus prometheus-prometheus-node-exporter-mvk88 1/1 Running 0 31s
prometheus prometheus-prometheus-node-exporter-wpgvs 1/1 Running 0 31s
prometheus prometheus-prometheus-pushgateway-9f8c968d6-ns56h 1/1 Running 0 31s
prometheus prometheus-server-6b58fcbc54-mfqp7 0/2 Pending 0 31s

Events:
Type Reason Age From Message

Warning FailedScheduling 2m3s (x4 over 17m) default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

I cannot get storage for pods. Is this limitation or my settings are incorrect ?

#2

Hi @shaz

It looks like the issue is related to the PVC not binding correctly, which can stem from several configuration issues involving PV, PVC, or storage class configs. To fin the root cause, I’d suggest checking the PVs are properly provisioned, the storage class is set up to match the PVC requirements, and that the PVCs are correctly referenced in the Pod specs would help you.

Reviewing logs and events on the PVCs and PVs can also provide more context on the binding issues you are facing.

Regards.