Skip to content

chore: update image tags and helm chart versions to latest compatible releases - #1455

Open
aneojgurhem wants to merge 2 commits into
mainfrom
chore/update-dependency-versions
Open

aneojgurhem wants to merge 2 commits into
mainfrom
chore/update-dependency-versions

Conversation

@aneojgurhem

Copy link
Copy Markdown
Contributor

Motivation

Keep third-party image tags and Helm chart versions in versions.tfvars.json up to date with the latest stable releases, ensuring compatibility with the target Kubernetes 1.35 EKS cluster.

Description

Updated image_tags and helm_charts in versions.tfvars.json:

  • KEDA: 2.19.0 → 2.20.1 (image + chart) — first branch officially tested against Kubernetes 1.35
  • aws-node-termination-handler: v1.25.4 → v1.25.6, chart 0.27.4 → 0.27.6
  • EFS CSI driver: v2.3.0 → v2.3.1, chart 3.4.0 → 3.4.1 (kept on the current v2.x line intentionally)
  • EBS CSI driver: v1.55.0 → v1.62.0, chart 2.55.1 → 2.62.0
  • CSI sidecars: livenessprobe, csi-node-driver-registrar, csi-provisioner bumped to match latest EBS/EFS chart defaults
  • cluster-autoscaler chart: 9.55.0 → 9.58.0 (image already up to date at v1.35.0, pinned to the cluster's Kubernetes minor version)
  • metrics-server chart: 3.13.0 → 3.13.1 (image already up to date)
  • MongoDB: 8.2.5 → 8.3.4, mongosh: 2.7.0 → 2.9.1, Redis: 8.6.0 → 8.8.0-alpine
  • RabbitMQ chart: 16.0.7 → 16.0.14 (image already up to date)
  • Grafana: 12.3.0 → 12.4.5 (latest patch on the current 12.x line, intentionally not moving to the 13.x major)
  • Prometheus: v3.5.1 → v3.13.0 (multiple CVE fixes and TSDB retention bugfix)
  • Fluent Bit: 4.2.2 → 5.0.8 (new major line, patched through 5.0.8)
  • node-exporter, windows-exporter, mongodb_exporter, nginx-unprivileged: minor/patch bumps
  • Chaos Mesh: v2.8.1 → v2.8.3 (images + chart), security patch release, tested against Kubernetes 1.35

Percona server MongoDB, the Percona operator, its chart, ActiveMQ Classic, MinIO, bitnamilegacy/rabbitmq, Seq/seqcli and nanoserver were already at their latest compatible version and were left unchanged.

Testing

No automated tests apply to this version bump. Versions were selected by checking each upstream project's release notes/compatibility matrix against Kubernetes 1.35; no cluster deployment was performed as part of this change.

Impact

  • No behavioral change expected for components with patch-level bumps.
  • Prometheus (v3.5.1 → v3.13.0) and Fluent Bit (4.2.2 → 5.0.8) involve major version jumps with breaking changes to review before rollout (Fluent Bit's forward output now retains metadata by default; Prometheus PromQL/remote-write spec changes). See PR discussion/commit context for details.
  • KEDA 2.20.0 changed Kubernetes event registration to events.k8s.io; custom RBAC for the KEDA operator may need updating.
  • EFS CSI driver and Grafana were deliberately kept on their current major version line to avoid unrelated breaking changes.

Additional Information

infrastructure/quick-deploy/aws/parameters.tfvars and parameters.tfvars.back have unrelated local changes and are intentionally excluded from this PR.

Checklist

  • My code adheres to the coding and style guidelines of the project.
  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • I have thoroughly tested my modifications and added tests when necessary.
  • Tests pass locally and in the CI.
  • I have assessed the performance impact of my modifications.

aneojgurhem and others added 2 commits July 2, 2026 16:29
… releases

Refresh dependency versions (KEDA, CSI drivers, MongoDB, Redis, RabbitMQ,
Grafana, Prometheus, Fluent Bit, Chaos Mesh, etc.) against Kubernetes 1.35
compatibility, keeping EFS CSI driver and Grafana on their current minor
version lines.
@sonarqubecloud

sonarqubecloud Bot commented Jul 3, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants