Update 2024-07-17: These changes have been rolled out to all clusters.
As part of our regular upgrade cycle, the following Kubernetes cluster components have been updated and have been rolled out to all our managed clusters. Highlight of this update is Grafana v11.1.0, which brings a lot of new features but is also the last version to support the deprecated AngularJS plugins. This is a reminder to please make sure to go through the Actions to take section!
Most other updates focus on resolve CVEs, bug fixes and general improvements. Click each link to go to the full upstream changelog.
- amazon-eks-ami v20240625
- aws-ebs-csi-driver v1.32.0-eksbuild.1
- aws-efs-csi-driver v2.0.5
- aws-load-balancer-controller 2.8.1
- cert-manager v1.15.1
- csi-snapshot-controller v8.0.0-eksbuild.1
- The snapshot controller now gets correctly scheduled to the
systemNodePool.
- The snapshot controller now gets correctly scheduled to the
- dex v2.40.0
- external-dns v0.14.2
- fluent-bit v3.0.7
- gha-runner-scale-set-controller v0.9.3
- Several reliability bug fixes, including better handling of autoscaling from 0
- grafana-agent v0.41.1
- ingress-nginx v1.10.1
- jaeger-operator v1.57.0
- k8s-dns-node-cache v1.23.1
- kube-prometheus-stack chart v61.2.0
- This brings updates to alertmanager, prometheus-operator, prometheus, grafana, etc.
- grafana v11.1.0
- AngularJS plugin warnings in dashboards, see Actions to take section
- prometheus v2.53.0
- prometheus-operator v0.75.0
- nvidia-k8s-device-plugin v0.15.1
- secrets-store-csi-driver v1.4.4
- secrets-store-csi-driver-provider-aws v0.3.9
- vertical-pod-autoscaler v1.1.2
- velero v1.14.0
Removals and deprecations:
- We are removing support for the
deschedulercomponent while migrating clusters depending on it tokarpenter.
Actions to take
An important change has come to Grafana where the use of AngularJS is being removed in favor of React. Support for AngularJS will be completely removed in Grafana 12, the next major release. As a result you will see warning messages in Grafana dashboards, helping you to identify which panels are using AngularJS plugins.
Many of our customers deploy their own custom dashboards, so we recommend you to check these for AngularJS plugin warnings and update them accordingly. For more information on how to do this, you can refer to the Grafana pages on this topic:
- Removal of AngularJS support in Grafana: what you need to know (blog)
- List of lugins using AngularJS and alternatives to use
Often, you can just click the Try migration button in the warning and Grafana will auto-migrate your dashboard. After verifying the results, you can save your updated dashboard:
- If using persistence, just click save and you’re done
- If not using persistence, instead relying on dynamic ConfigMap dashboard loading, export the dashboard’s json and backport it to your ConfigMap.
The most commonly used core plugins to change are Graph (old), Singlestat, Table (old), and Worldmap. While these can be auto-migrated, you can also update them to the newer versions, for example:
graph->timeseriessinglestat->stat
Some old custom plugins also have found there way as core plugins. For example you can replace grafana-piechart-panel with the build-in Pie Chart.
[!NOTE] While we have updated our own custom dashboards to use newer plugin versions, unfortunately there are a handfull of leftover dashboards, included in the upstream
kube-prometheus-stackthat we deploy and have not yet been updated. You can safely ignore the warnings for these dashboards for now. Affected dashboards are:
- Alertmanager / Overview
- Grafana / Overview
- Node Exporter / MacOS
- Node Exporter / Nodes
- Node Exporter / USE Method / Cluster
- Node Exporter / USE Method / Node
- Prometheus / Overview