Prometheus node exporter helm8/7/2023 % kubectl logs -namespace default prometheus-prometheus-node-exporter-pp4rxįailed to try resolving symlinks in path "/var/log/pods/default_prometheus-prometheus-node-exporter-pp4rx_a4192875-5875-417a-a575-bec6ea2a5a81/node-exporter/6.log": lstat /var/log/pods/default_prometheus-prometheus-node-exporter-pp4rx_a4192875-5875-417a-a575-bec6ea2a5a81/node-exporter/6.log: no such file or directory%Įven though there are no errors during the installation phase, the prometheus-prometheus-node-exporter pod keeps in CrashLoopBackOff state. Prometheus-prometheus-node-exporter-pp4rx 0/1 CrashLoopBackOff 3 (16s ago) 61s Prometheus-kube-state-metrics-9bc7f5984-ldn7w 1/1 Running 0 61s ![]() Prometheus-kube-prometheus-operator-579c654f9f-5zdzg 1/1 Running 0 61s % kubectl -namespace default get pods -l "release=prometheus" It configures a default set of Kubernetes observability scraping jobs for Prometheus. Visit for instructions on how to create & configure Alertmanager and Prometheus instances using the Operator. Pushgateway, Alertmanager, and node-exporter. enabled: true Use the value configured in prometheus-node-exporter. Kubectl -namespace default get pods -l "release=prometheus" Provide a name in place of prometheus-operator for app: labels nameOverride. Kube-prometheus-stack has been installed. % helm install prometheus prometheus-community/kube-prometheus-stack Successfully got an update from the "bitnami" chart repository Successfully got an update from the "prometheus-community" chart repository Hang tight while we grab the latest from your chart repositories. "prometheus-community" has been added to your repositories Have free ports for the requested pod ports.I just installed Docker Desktop (4.17.0 (99724)) on my Apple Air (M2, 2022) and after enabling Kubernetes flag, I now trying to follow Install Helm Chart % helm version 1 The way that your command is running, is pulling the chart from the internet, you are not passing any extra values file. Warning FailedScheduling 2s (x24 over 29m) default-scheduler 0/3 nodes are available: 2 node(s) didn't match node selector, 3 node(s) didn't SecretName: exporter-prometheus-node-exporter-token-rl4fm Type: Secret (a volume populated by a Secret) Type: HostPath (bare host directory volume)Įxporter-prometheus-node-exporter-token-rl4fm: var/run/secrets/kubernetes.io/serviceaccount from exporter-prometheus-node-exporter-token-rl4fm (ro) Any other ideas for troubleshooting would be greatly appreciated.Įxporter-prometheus-node-exporter-bcwc4 0/1 Pending 0 15mĮxporter-prometheus-node-exporter-kr7z7 0/1 Pending 0 15mĮxporter-prometheus-node-exporter-lw87g 0/1 Pending 0 15mĭescribe Pods Name: exporter-prometheus-node-exporter-bcwc4Īnnotations: kubernetes.io/psp: eks.privilegedĬontrolled By: DaemonSet/exporter-prometheus-node-exporter I believe it may have something to do with "tolerations" but I'm still digging in.ĮKS cluster is running on 3 t2.large which can support up to 35 pods per node, and I'm running a total of 43 pods. I've attached some troubleshooting output for your reference. I'm able to install many other apps on my cluster with the exception of just this one. I've searched high and low and I'm not sure where else to turn. 1 helm install prometheus-operator stable/prometheus-operator -namespace monitor Alternatively, you can wget a tar file through GitHub and unzip it: 1 2 3 4 wget tar xvfz cd nodeexporter-.-amd64. ![]() For the purposes of troubleshooting I decided to deploy a very vanilla implementation of Prometheus NodeExporter via helm install exporter stable/prometheus however I can't get the pods to start.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |