Repository navigation
Compatibility Matrix Update 2026-10-24 - #4581
Conversation
Soffi AI SummaryThis is an automated pull request that refreshes the static compatibility matrix data used by Plural Console to track which versions of Kubernetes add-ons are compatible with which Kubernetes versions. The update bumps several add-ons to their latest patch/minor releases, adds new version entries, corrects image digests and chart versions, and enriches version summaries with feature and breaking-change notes. No application logic was modified — only the static data files that the server reads to inform users about add-on compatibility. ChangesCompatibility matrix refresh 2026-10-24
Updated: 2026-10-24 01:47 UTC |
[Medium impact] The changes reach compatibility information for several add-ons and upgrade workflows. The PR appears safe to merge, with two non-blocking improvements to the release notes. FindingsSummaryUpdates addon versions, chart versions, images, and release notes in the combined matrix and nine individual files.
Reviews (1) · Last reviewed commit: "Updated compatibility matrix 2026-10-24" · Reviewed by Greptile |
| patch versions.', 'AlibabaCloud IPAM: adds support for RRSA (RAM Roles for | ||
| Service Accounts) credentials, in addition to static AccessKeys and ECS RAM | ||
| roles.'] | ||
| breaking_changes: [] |
There was a problem hiding this comment.
Cilium upgrade warnings disappear
Replacing 1.20.3 with 1.20.4 drops the existing warnings about empty redirectBackend.toPorts and changed nodeSelector behavior. The new entry covers the jump from retained version 1.20.2, but its breaking_changes is empty. Carry those warnings forward, including in the combined matrix, so readers do not lose the documented upgrade checks.
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!
| features: ["No specific feature details were provided in the notes you shared;\ | ||
| \ both entries primarily include installation/asset info and point to external\ | ||
| \ changelog/blog for \u201CWhat\u2019s New\u201D.", The main visible change | ||
| is the target release artifact versions (CLI binaries and install.yaml) moving | ||
| from v4.1.0 to v4.1.6.] | ||
| breaking_changes: [No breaking changes were listed in the provided excerpts; they | ||
| refer to an external upgrading guide/known issues instead.] |
There was a problem hiding this comment.
The new Argo Workflows summary replaces concrete release information with statements about missing source notes. The page displays these under Features and Breaking changes, but they provide neither upgrade guidance nor a usable link. Replace them with verified release information, or leave the unavailable fields empty. Update the combined matrix too.
Automated Pull Request to update compatibility matrix