Skip to content

Add 3.24 to support and compatibility section - #2897

Open
sabags wants to merge 2 commits into
tigera:mainfrom
sabags:de-fossa-3.24-compatibility
Open

Add 3.24 to support and compatibility section#2897
sabags wants to merge 2 commits into
tigera:mainfrom
sabags:de-fossa-3.24-compatibility

Conversation

@sabags

@sabags sabags commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

The CE 3.24 compatibility page had no 3.24 rows. This adds one 3.24 row per platform table, above the existing 3.23 row — nothing removed.

Table 3.24
kOps on AWS 1.33 - 1.35
Kubernetes-kubeadm 1.34 - 1.36
MKE 4k MKE 4k 4.1.2 / k8s 1.32
MKE MKE 3.9 / k8s 1.34
OpenShift 4.20 - 4.22
RKE 1.8 / k8s 1.32
RKE2 k8s 1.34 - 1.36
VKS VKS 3.8 / k8s 1.36
TKG 2.4 / k8s 1.27

Applied to both files that render this page, matching how 3.23 was added in d6e3e12:

  • calico-enterprise/getting-started/compatibility.mdx
  • calico-enterprise_versioned_docs/version-3.24-1/getting-started/compatibility.mdx

The AKS / EKS / GKE / Charmed Kubernetes tables are unchanged — they read "3.21 to current release", which already covers 3.24.

@sabags
sabags requested a review from a team as a code owner July 31, 2026 17:13
Copilot AI review requested due to automatic review settings July 31, 2026 17:13
@netlify

netlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit 208511a
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/6a6ce1707d5b77000876db52
😎 Deploy Preview https://deploy-preview-2897--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit 208511a
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/6a6ce170d22b8400086fad8f
😎 Deploy Preview https://deploy-preview-2897--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 73 (🟢 up 3 from production)
Accessibility: 98 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds Calico Enterprise 3.24 entries to the “Support and compatibility” platform tables so the compatibility page reflects the current release series (both for “next” docs and the versioned 3.24-1 docs).

Changes:

  • Added a new 3.24 row to each relevant platform compatibility table (kOps on AWS, kubeadm, MKE 4k, MKE, OpenShift, RKE, RKE2, VKS, TKG) above the existing 3.23 row.
  • Applied the same table updates to both the unversioned and versioned (3.24-1) compatibility pages.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
calico-enterprise/getting-started/compatibility.mdx Inserts 3.24 compatibility rows across the relevant platform tables in the unversioned CE docs page.
calico-enterprise_versioned_docs/version-3.24-1/getting-started/compatibility.mdx Mirrors the same 3.24 row additions for the CE 3.24-1 versioned docs page.

@ctauchen

Copy link
Copy Markdown
Collaborator

LGTM, but add those two temporarily dead links to the skip list. @sabags

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.

3 participants