英文:
Prometheus Server on EKS with Helm - FailedScheduling
问题
我试图在我的AWS EKS集群中使用社区Helm Chart 存储库安装全新的Prometheus Chart。
然而，alertmanager和prometheus-server容器无法启动。它们都显示了一个事件警告：
Warning FailedScheduling 10m (x25 over 4h13m) default-scheduler running PreBind plugin “VolumeBinding”: binding volumes: timed out waiting for the condition
我们的EKS集群正在使用EKS托管的EC2节点，如果这个信息有关的话。有人在尝试在AWS上设置Prometheus时遇到过这个问题吗？任何建议将不胜感激！
步骤：
通过以下命令安装Helm Chart：
helm install <chartName> prometheus-community/prometheus -n <namespaceName>
我通过以下命令验证了图表是否已部署：
kubectl get pods -n <namespaceName>
两个容器都无法启动 - prometheus-server和alert-manager。每个容器的日志都显示了相同的内容：
Warning FailedScheduling 5m22s (x1019 over 7d4h) default-scheduler running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
英文:
I’m trying to install a fresh Prometheus Chart into my AWS EKS cluster using the community helm-chart repo.
However, alertmanager and prometheus-server pods fail to start. They both show an event warning:
Warning FailedScheduling 10m (x25 over 4h13m) default-scheduler running PreBind plugin “VolumeBinding”: binding volumes: timed out waiting for the condition
Our EKS cluster is using EKS managed EC2 nodes, if that’s relevant. Anyone run into this before trying to set up Prometheus on AWS? Any suggestions would be much appreciated!
Steps:
Installed the helm chart via
helm install <chartName> prometheus-community/prometheus -n <namespaceName>
I verified the chart was deployed via
kubectl get pods -n <namespaceName>
Two pods do not start - prometheus-server and alert-manager. The logs from each pod say the same thing:
Warning FailedScheduling 5m22s (x1019 over 7d4h) default-scheduler running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
答案1
得分: 0
根据错误消息和prometheus-server（这里）以及alertmanager（这里）的默认Prometheus图表数值，它正在等待PVC被创建。集群上安装了EBS CSI 驱动程序附加组件吗？从 EKS 1.23 开始（此处的变更日志），内置存储插件已被替换，这意味着将需要类似于EBS附加组件提供的CSI驱动程序来为EBS卷进行配置。
英文:
From the error, and default Prometheus chart values for prometheus-server (here) & alertmanager (here), it's waiting for the PVC to be created. Is the EBS CSI driver add-on installed on the cluster? As of EKS 1.23 (changelog here), the in-tree storage plugin has been replaced, which means a CSI driver like the one provided in EBS add-on will be needed in order to provision EBS volumes.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论