Repository navigation
DOCS-3072: Publish Calico Cloud 24.1.1 - #3178
Merged
Merged
Conversation
Calico Cloud 24.1.1 is the next release after 24.0.0. Version 24.1.0 was not released. - Add the 24.1.1 image list for private registries, from cloud manifests v3.24.0-1.0-8. Only cc-core and cc-cni-config-scanner change from 24.0.0. - Set cloudUserVersion to v24.1.1. - Add 24.1.1 to the Kubernetes compatibility table. Next also gets the 24.0.0 row it was missing. - Add 24.1.1 release notes: the policy editor changes, the policy fixes for older managed clusters, compliance removal from installs, and the known issue carried over from 24.0.0.
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ctauchen
commented
Nov 3, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Active moderate issues leave the 24.1.1 documentation inconsistent about the required download manifest and whether compliance-benchmarker remains deployed, creating contradictory upgrade and private-registry guidance.
5 open issues
What changed in this PR
Publishes Calico Cloud 24.1.1 documentation for current and versioned sites, including release notes, private-registry images, version metadata, and Kubernetes compatibility information.
Changes:
- Adds the 24.1.1 private-registry image list with updated
cc-coreandcc-cni-config-scannerimages. - Updates the documented Cloud version to 24.1.1.
- Adds 24.1.1 release notes and Kubernetes compatibility entries.
- Adds the missing 24.0.0 compatibility entry to the current documentation.
This pull request requires changes.
| File | Summary | Review notes |
|---|---|---|
src/___new___/data/ccImageLists.js |
Adds the 24.1.1 private-registry image list and relabels the 24.0.0 list. | Moderate: Confirm whether compliance-benchmarker is deployed in 24.1.1 and align the image list with the release notes and upgrade behavior. |
calico-cloud/variables.js |
Updates the current documentation version to 24.1.1. | Moderate: Update clouddownloadurl from the previous -4 manifest to the 24.1.1 -8 manifest. |
calico-cloud/release-notes/index.mdx |
Adds current 24.1.1 release notes and known issues. | Nit: Clarify whether compliance reporting components were removed entirely or only the web-console/reporting UI. |
calico-cloud/get-started/system-requirements.mdx |
Adds 24.1.1 and 24.0.0 Kubernetes compatibility entries. | No review issues noted. |
calico-cloud_versioned_docs/version-24-1/variables.js |
Updates the versioned documentation to Cloud 24.1.1. | Moderate: Update clouddownloadurl from the previous -4 manifest to the 24.1.1 -8 manifest. |
calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx |
Adds versioned 24.1.1 release notes and known issues. | Nit: Clarify whether compliance reporting components were removed entirely or only the web-console/reporting UI. |
calico-cloud_versioned_docs/version-24-1/get-started/system-requirements.mdx |
Adds the 24.1.1 Kubernetes compatibility entry. | No review issues noted. |
Review effort: Lite
| const variables = { | ||
| releaseTitle: 'v3.24.0-1.0', | ||
| cloudUserVersion: 'v24.0.0', | ||
| cloudUserVersion: 'v24.1.1', |
| const variables = { | ||
| releaseTitle: 'v3.24.0-1.0', | ||
| cloudUserVersion: 'v24.0.0', | ||
| cloudUserVersion: 'v24.1.1', |
|
|
||
| ### Deprecated and removed features | ||
|
|
||
| * $[prodname] no longer installs the compliance reporting components on your cluster. |
|
|
||
| ### Deprecated and removed features | ||
|
|
||
| * $[prodname] no longer installs the compliance reporting components on your cluster. |
Calico Cloud 24.1.1 needs the admissionregistration.k8s.io/v1beta1 API on clusters that use the projectcalico.org/v3 CRDs. Kubernetes 1.36 doesn't provide it, and 1.34 and 1.35 turn it off by default. Calico Open Source 3.33 uses the v3 CRDs for new installs by default, so more clusters are affected than the 24.0.0 note implied. The cc-operator v24.1.1 installer now refuses these clusters with a message, so the known issue says that and lists the two ways to connect.
- Merge the two policy editor changes under one heading. - Drop the note about the skipped version and the web console line. - Cut the v3 CRD known issue down to the condition, the default setup that hits it, and the two fixes. Engineering asked us not to give Kubernetes configuration steps, and earlier Calico Cloud versions don't support the configuration, so the note covers installs only. - Remove compliance-benchmarker from the 24.1.1 image list, since 24.1.1 no longer installs compliance components.
tmjd
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Publishes Calico Cloud 24.1.1.
Jira: https://tigera.atlassian.net/browse/DOCS-3072
Changes:
A follow-up PR to this branch, #3179, documents the policy editor changes on the network policy tutorial page.
Preview: