Skip to content

docs: add k8s 1.36 to compatibility matrix#2014

Draft
pascalbreuninger wants to merge 1 commit intomainfrom
project/k8s-1.36-support
Draft

docs: add k8s 1.36 to compatibility matrix#2014
pascalbreuninger wants to merge 1 commit intomainfrom
project/k8s-1.36-support

Conversation

@pascalbreuninger
Copy link
Copy Markdown
Member

Summary

  • Add Kubernetes 1.36 as a new row/column in the compatibility matrix (static/api/k8s-compatibility.json).
  • Diagonal cell host 1.36 / vcluster 1.36 marked tested; all other new cells default to compatible.
  • lastUpdated bumped to 2026-04-24.

Resolves ENGCP-227.

Follow-up

Draft only — once the 1.36 conformance test sweep completes we'll come back and adjust any cells that surface known issues, then mark ready for review.

Test plan

  • npm run generate-compatibility-matrix (schema validation) — passes
  • npm run start → verified /docs/api/k8s-compatibility.json serves updated payload with 7 versions and lastUpdated: 2026-04-24
  • Eyeball rendered matrix at /docs/vcluster/manage/upgrade/supported_versions in the Netlify preview

🤖 Generated with Claude Code

Adds a new row/column for Kubernetes 1.36. Diagonal cell marked as
tested; all other new cells default to compatible. Conformance test
results will follow in a separate update.

Resolves ENGCP-227

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 24, 2026

Deploy Preview for vcluster-docs-site ready!

Name Link
🔨 Latest commit 78548f2
🔍 Latest deploy log https://app.netlify.com/projects/vcluster-docs-site/deploys/69eba41210355800089b9077
😎 Deploy Preview https://deploy-preview-2014--vcluster-docs-site.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@github-actions
Copy link
Copy Markdown
Contributor

@djwfyi
Copy link
Copy Markdown
Collaborator

djwfyi commented Apr 24, 2026

Do we want to drop EOL versions while we're making updates? We still go back to 1.30.

1 similar comment
@djwfyi
Copy link
Copy Markdown
Collaborator

djwfyi commented Apr 24, 2026

Do we want to drop EOL versions while we're making updates? We still go back to 1.30.

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.

2 participants