Compatibility Matrix Update 2026-09-11

[github-actions]

Automated Pull Request to update compatibility matrix

[soffi-ai]

Soffi AI Summary

This is an automated pull request that refreshes the static compatibility matrix data used by the Console to inform users about add-on version support across Kubernetes releases. The update adds new version entries and enriches existing ones with structured release summaries (features, breaking changes, chart updates) for several key add-ons: a new aws-ebs-csi-driver v1.66.0 entry covering Kubernetes 1.20–1.36, a corrected container image reference for Karpenter v1.5.0, detailed release notes and breaking-change warnings for Kong Ingress Controller v3.0.0 and v3.1.0, and comprehensive upgrade guidance for MongoDB Kubernetes Operator v1.12.0 (including webhook enforcement changes, required secret pre-creation, and Search topology restrictions). These changes keep the Console's add-on compatibility views current and actionable for operators managing fleet upgrades.

Changes

Compatibility matrix update (2026-09-11)

• Automated refresh of static/compatibilities.yaml and per-add-on YAML files. Adds aws-ebs-csi-driver v1.66.0 support data, fixes missing Karpenter v1.5.0 container image, and populates structured release summaries (features + breaking changes) for Kong Ingress Controller v3.0.0/v3.1.0 and MongoDB Kubernetes Operator v1.12.0. (6f940cb)

---

Updated: 2026-09-11 01:53 UTC

Deploy in Soffi

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge after addressing the non-blocking Kong documentation-quality issue.

Findings

1.  Changelog Links Are Missing ▶

Summary

• Adds AWS EBS CSI Driver 1.66.0 and chart 2.66.0.
• Records the Karpenter 1.5.0 controller image by tag and digest.
• Adds MongoDB Kubernetes 1.12.0 feature and breaking-change guidance.
• Adds Kong summaries, but two entries contain unusable references to nonexistent links.

_{Reviews (1) · Last reviewed commit: "Updated compatibility matrix 2026-09-11"}

[greptile-apps]

Changelog Links Are Missing

These breaking-change summaries tell users to review “linked CHANGELOG sections,” but the compatibility data provides only bare issue numbers and no usable URLs. This text is shown directly in the upgrade-plan UI, so users cannot follow the references or determine the actual upgrade impact. Replace these placeholders with verified release details and usable URLs, or leave the summaries null when meaningful content is unavailable. The 3.0.0 summary has the same issue.