Our great sponsors
-
terraform-kubernetes-ebs-csi-driver
Terraform module which creates Kubernetes EBS CSI controller resources on AWS EKS.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
When updating to 1.24 I first found https://github.com/DrFaust92/terraform-kubernetes-ebs-csi-driver but trying that one again does not change things.
We are running the `kube-prometheus-stack` helm chart: https://github.com/prometheus-community/helm-charts/
I can also post some link but I'll actually read it before posting... https://github.com/aws/aws-node-termination-handler/pull/758
I looks like the driver's permissions to invoke the EBS APIs was revoked and/or changed. When you install the EBS CSI addon you can either inherit permissions from the worker node or you can choose an IRSA role (preferred). If you use IRSA, the service account that the EBS CSI driver uses should have an annotation that references the ARN of the IAM role you selected, e.g. eks.amazonaws.com/role-arn: arn:aws:iam::111122223333:role/my-role. You can see an example of the IAM policy the driver needs here, https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/fb6d456558fb291b13f855454c1525c7acaf7046/docs/example-iam-policy.json.
Related posts
- You get what you Measure: Understanding your applications health with Grafana, Loki and Prometheus
- Porter Cloud – PaaS you can eject
- Multi-Cluster Prometheus: Scaling Metrics Across Kubernetes Clusters
- Hands On: Pull metrics into Kubernetes from anywhere and treat them generically with the Keptn Metrics Server
- Smart-Cash project -Adding monitoring to EKS using Prometheus operator