Compatibility Matrix Update 2026-05-15#3560
Conversation
Greptile SummaryThis automated PR updates the compatibility matrix for three add-ons: adds aws-ebs-csi-driver v1.60.0, populates the external-secrets v0.10.7 summary, and bumps kube-prometheus-stack from 85.0.2 to 85.0.3 (including a security-patched Grafana image).
Confidence Score: 3/5The aws-ebs-csi-driver entry should not be merged as-is due to a CI test image appearing in the production image list. The static/compatibilities/aws-ebs-csi-driver.yaml and the corresponding aws-ebs-csi-driver section in static/compatibilities.yaml — both carry the spurious test image reference.
|
| Filename | Overview |
|---|---|
| static/compatibilities/aws-ebs-csi-driver.yaml | Adds v1.60.0 entry, but the images list incorrectly includes a kubekins-e2e CI test image from k8s-staging-test-infra, which is not a production component of the driver. |
| static/compatibilities.yaml | Mirrors the aws-ebs-csi-driver.yaml addition (v1.60.0 with the same spurious kubekins-e2e image), plus updates external-secrets summary and bumps kube-prometheus-stack to 85.0.3 with a security-patched Grafana image. |
| static/compatibilities/external-secrets.yaml | Adds structured summary for v0.10.7, replacing null. Changes look accurate and well-formed. |
| static/compatibilities/kube-prometheus-stack.yaml | Version bumped from 85.0.2 to 85.0.3; Grafana image updated to security-patched tag 13.0.1-security-01; chart_updates summary reworded. Changes appear correct. |
Reviews (1): Last reviewed commit: "Updated compatibility matrix 2026-05-15" | Re-trigger Greptile
| '1.25', '1.24', '1.23', '1.22', '1.21', '1.20'] | ||
| requirements: [] | ||
| incompatibilities: [] | ||
| summary: null |
There was a problem hiding this comment.
Test infrastructure image included in production image list
The image us-central1-docker.pkg.dev/k8s-staging-test-infra/images/kubekins-e2e:v20260512-1f34ef0df3-master is a Kubernetes end-to-end test tooling image from the k8s-staging-test-infra GCP project. It is not a runtime component of the aws-ebs-csi-driver and should not appear in the compatibility matrix images list. Including it may cause consumers of this data to attempt pulling a staging/ephemeral CI image as part of driver deployments, and the staging registry is not guaranteed to be stable or long-lived.
Automated Pull Request to update compatibility matrix