Compatibility Matrix Update 2026-07-24

[github-actions]

Automated Pull Request to update compatibility matrix

[soffi-ai]

Soffi AI Summary

This is an automated pull request generated by the compatibility matrix scraper tooling (utils/compatibility/scrapers/) to keep the static add-on compatibility data in static/compatibilities/ and the consolidated static/compatibilities.yaml in sync with upstream release data as of 2026-07-24.

What changed and why:

• Big Bang 3.29.0 — Added a full new version entry for Big Bang 3.29.0 targeting Kubernetes 1.34, including a comprehensive list of pinned sub-component versions (ArgoCD 10.1.3-bb.0, External Secrets Operator 2.7.0-bb.2, Monitoring 87.10.1-bb.1, Prometheus Operator CRDs 30.0.1-bb.0, and ~40 other components). The summary flags potential breaking changes in major/minor version jumps for ArgoCD (9.x → 10.x), ESO (1.x → 2.x), Monitoring (85.x → 87.x), and Prometheus Operator CRDs (28 → 30).
• AWS EFS CSI Driver 3.4.1 — Added a new version entry with updated container images.
• AWS EBS CSI Driver — Enriched an existing version's summary field with AI-generated release notes analysis, noting that the upstream changelog link must be consulted to determine breaking changes between v1.62.0 and v1.63.0.
• Argo CD — Bumped chart_version from 10.1.4 to 10.2.1 for an existing version entry.
• Argo Workflows — Bumped chart_version from 1.0.21 to 1.0.22 and updated the kubectl image tag from v1.36.2 to v1.36.3.

Commits

Commit	Summary
7a15294	Automated scraper run that refreshes add-on compatibility data across five YAML files: adds Big Bang 3.29.0 (Kubernetes 1.34, ~40 pinned sub-components with breaking-change warnings), adds AWS EFS CSI Driver 3.4.1, enriches the AWS EBS CSI Driver summary field, and bumps chart versions for Argo CD (10.1.4 → 10.2.1) and Argo Workflows (1.0.21 → 1.0.22, kubectl image v1.36.2 → v1.36.3).

Deploy in Soffi

---

Updated: 2026-07-24 01:43 UTC

[greptile-apps]

Greptile Summary

This automated PR updates the compatibility matrix for several components as of 2026-07-24. It adds new releases (BigBang 3.29.0, aws-efs-csi-driver 3.4.1), bumps chart versions and images for ArgoCD v3.4.5 and Argo Workflows v4.0.8, and populates previously-null summary fields for aws-ebs-csi-driver v1.63.0.

• ArgoCD / Argo Workflows: Chart version bumps (10.1.4 → 10.2.1 and 1.0.21 → 1.0.22) and a kubectl image patch (v1.36.2 → v1.36.3) for existing version entries — clean, low-risk corrections.
• aws-ebs-csi-driver v1.63.0: summary: null replaced with structured content, but the features and breaking_changes values contain instructional placeholder text rather than factual data.
• BigBang 3.29.0: New entry added with a full requirements list, but kube: ['1.34'] is lower than the kube: ['1.35'] listed for the prior 3.28.0 release, which may mislead users about 1.35 cluster compatibility.

Confidence Score: 3/5

Two data quality issues need resolution before merging: placeholder text published as real breaking-change guidance, and a Kubernetes version regression in the BigBang 3.29.0 entry.

The ArgoCD, Argo Workflows, and aws-efs-csi-driver changes are straightforward and correct. The aws-ebs-csi-driver breaking_changes field publishes AI-generated instructional text as if it were factual compatibility data, and BigBang 3.29.0 lists kube 1.34 while its predecessor 3.28.0 lists kube 1.35, which could cause users on Kubernetes 1.35 to mistakenly believe the newer BigBang release is incompatible with their cluster.

static/compatibilities/aws-ebs-csi-driver.yaml (placeholder breaking_changes text) and static/compatibilities/bigbang.yaml (kube version regression from 1.35 to 1.34 between consecutive releases).

Important Files Changed

Filename	Overview
static/compatibilities/aws-ebs-csi-driver.yaml	Replaces summary: null with structured content for v1.63.0, but breaking_changes and features fields contain AI-generated placeholder/instructional text rather than real data.
static/compatibilities/aws-efs-csi-driver.yaml	Adds new version 3.4.1 entry with kube: [] (consistent with the prior 3.4.0 entry) and summary: null; straightforward addition.
static/compatibilities/bigbang.yaml	Adds Big Bang 3.29.0 with kube: ['1.34'], but the previous version 3.28.0 listed kube: ['1.35'] — a newer release listing lower Kubernetes compatibility is unusual and may be a data error.
static/compatibilities/argo-cd.yaml	Updates chart_version for ArgoCD v3.4.5 from 10.1.4 to 10.2.1; straightforward chart version bump.
static/compatibilities/argo-workflows.yaml	Updates chart_version for Argo Workflows v4.0.8 from 1.0.21 to 1.0.22 and bumps kubectl image from v1.36.2 to v1.36.3; straightforward patch update.
static/compatibilities.yaml	Aggregates all per-component changes into the main compatibility manifest; inherits the same data quality concerns from aws-ebs-csi-driver and bigbang entries.

_{Reviews (1): Last reviewed commit: "Updated compatibility matrix 2026-07-24" | Re-trigger Greptile}

[greptile-apps]

Placeholder text published as real compatibility data

The features and breaking_changes fields contain what appear to be AI-generated instructions rather than curated data. Text like "Release notes provided do not enumerate changes; both versions only link to the upstream CHANGELOG" and "Unknown from provided notes; need to review upstream CHANGELOG between v1.62.0 and v1.63.0 … to confirm any breaking changes" will be read by end users as if they are authoritative compatibility notes, potentially causing confusion or misplaced confidence. If the information is genuinely unknown, null (as the previous value) or an empty list is a safer representation than prose that describes a data-gathering task.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Kubernetes compatibility may regress between versions

Big Bang 3.29.0 is listed with kube: ['1.34'], while the immediately preceding 3.28.0 lists kube: ['1.35']. A newer Big Bang release listing a lower Kubernetes version than the previous one is unexpected and likely means either the 3.29.0 entry should include 1.35 (or both), or the 3.28.0 entry was incorrect. As written, users running Kubernetes 1.35 who read this matrix might incorrectly believe 3.29.0 is incompatible with their cluster.