Skip to content

List Windows Server 2025 as a supported Windows version - #3226

Merged
caseydavenport merged 2 commits into
tigera:mainfrom
caseydavenport:casey-windows-2025
Nov 17, 2026
Merged

caseydavenport merged 2 commits into
tigera:mainfrom
caseydavenport:casey-windows-2025

Conversation

@caseydavenport

Copy link
Copy Markdown
Member

The Windows requirements pages list only Windows Server 1809 and 2022, but Calico now supports Windows Server 2025. This PR adds it to the supported Windows platforms on the current OSS and Enterprise pages and on the OSS 3.32 and 3.33 pages.

  • Current docs. The OSS and Enterprise pages list "Windows Server 2025 (build 26100 or later)". Master in both products runs the Windows CI host on Server 2025 and publishes ltsc2025 container images.
  • Versioned OSS docs. The 3.33 and 3.32 pages list it "from Calico v3.33.1" and "from Calico v3.32.4", the first releases that include the backported CI host upgrade. The 3.33 page is what "latest" points to.
  • Testing. Each change is one list item and has no links, so I didn't run a build.

Product Version(s): Calico (master, v3.33, v3.32) and Calico Enterprise (current)

Issue: projectcalico/calico issue 11691 (Windows Server 2025 missing from the requirements page)

Link to docs preview:

SME review:

  • An SME has approved this change.

DOCS review:

  • A member of the docs team has approved this change.

Additional information:

Windows Server 2025 build 26100 is the base build, and no minimum patch level is known, so the line gives only that. The OSS CI host upgrade landed in PR 14071 (Windows CI host on Server 2025) and PR 14118 (ltsc2025 images), then was backported in PR 14562 (release-v3.33) and PR 14561 (release-v3.32). Kubernetes also lists Windows Server 2025 as supported.

Merge checklist:

  • Deploy preview inspected wherever changes were made
  • Build completed successfully
  • Test have passed
Agent context

Decisions

  • Versioned 3.33 and 3.32 pages carry the "from Calico v3.33.1" and "from Calico v3.32.4" qualifier because the backport merge commits, merged 2026-11-09, are ancestors of those tags (checked with the GitHub compare API). On those branches the Windows FV runs on a 2025 host with the ltsc2022 images, which work because calico-node on Windows runs as a HostProcess container.
  • Enterprise master has the same CI host upgrade and ltsc2025 images, so the current Enterprise page lists 2025 without a version qualifier.

Rejected alternatives

  • Not editing version-3.31: the CI host upgrade was never backported to release-v3.31.
  • Not editing Enterprise versioned docs: the upgrade was backported to the release-calient branches, but this PR keeps Enterprise to the current tree.

Code map

  • calico/getting-started/kubernetes/windows-calico/requirements.mdx: one list item.
  • calico-enterprise/getting-started/install-on-clusters/windows-calico/requirements.mdx: one list item.
  • calico_versioned_docs/version-3.33 and version-3.32, same path as the OSS page: one list item each, with the release qualifier.

Follow-ups

  • Decide whether released Enterprise versions should claim Windows Server 2025 too.

@caseydavenport
caseydavenport requested a review from a team as a code owner November 16, 2026 22:53
Copilot AI lite review requested due to automatic review settings November 16, 2026 22:53
@netlify

netlify Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

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

Built without sensitive environment variables

Name Link
🔨 Latest commit fa375c6
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/6afc66ca7c85ea9fcd1ec170
😎 Deploy Preview https://deploy-preview-3226--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 Nov 16, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit fa375c6
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/6afc66ca42790513cb870534
😎 Deploy Preview https://deploy-preview-3226--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: 87 (🟢 up 16 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.

🟢 Approval recommended

The review found no active issues, and the documentation updates consistently record the newly supported Windows Server 2025 requirements across current and versioned pages.

No open issues 🎉

What changed in this PR

Updates Calico Windows platform requirements to document support for Windows Server 2025 across current OSS and Enterprise documentation and the OSS 3.32 and 3.33 versioned pages.

Changes:

  • Added Windows Server 2025 build 26100 or later to the current OSS and Enterprise requirements pages.
  • Added version-qualified support beginning with Calico v3.33.1 and v3.32.4.
File Description
calico/​getting-started/​kubernetes/​windows-calico/​requirements.mdx Adds Windows Server 2025 to the current Calico OSS requirements.
calico-enterprise/​getting-started/​install-on-clusters/​windows-calico/​requirements.mdx Adds Windows Server 2025 to the current Calico Enterprise requirements.
calico_versioned_docs/​version-3.33/​getting-started/​kubernetes/​windows-calico/​requirements.mdx Documents Windows Server 2025 support beginning with Calico v3.33.1.
calico_versioned_docs/​version-3.32/​getting-started/​kubernetes/​windows-calico/​requirements.mdx Documents Windows Server 2025 support beginning with Calico v3.32.4.

Review effort: Lite

@ctauchen

Copy link
Copy Markdown
Collaborator

I see new images only for 3.34, not for 3.33 or 3.32. e2es are pending. Based on what I'm seeing, I'd think we should wait for e2es, and then document support only in 3.34. Do you have plans to build 2025 images for older versions?

@ctauchen ctauchen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM with suggestion. The docs always presume the latest patch.


- Windows Server 1809 (build 17763.1432 or later)
- Windows Server 2022 (build 20348.169 or later)
- Windows Server 2025 (build 26100 or later), from Calico v3.32.4

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- Windows Server 2025 (build 26100 or later), from Calico v3.32.4
- Windows Server 2025 (build 26100 or later)


- Windows Server 1809 (build 17763.1432 or later)
- Windows Server 2022 (build 20348.169 or later)
- Windows Server 2025 (build 26100 or later), from Calico v3.33.1

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- Windows Server 2025 (build 26100 or later), from Calico v3.33.1
- Windows Server 2025 (build 26100 or later)

@caseydavenport
caseydavenport merged commit ea3a69c into tigera:main Nov 17, 2026
11 checks passed
@caseydavenport
caseydavenport deleted the casey-windows-2025 branch November 17, 2026 15:15
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