From 0bf638f40ff6b0e7482228c593c7d741d2082af2 Mon Sep 17 00:00:00 2001 From: Chris Tauchen Date: Tue, 3 Nov 2026 12:31:50 +0000 Subject: [PATCH 1/3] DOCS-3072: Publish Calico Cloud 24.1.1 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. --- .../get-started/system-requirements.mdx | 2 + calico-cloud/release-notes/index.mdx | 35 ++++++++++++++++++ calico-cloud/variables.js | 2 +- .../get-started/system-requirements.mdx | 1 + .../version-24-1/release-notes/index.mdx | 35 ++++++++++++++++++ .../version-24-1/variables.js | 2 +- src/___new___/data/ccImageLists.js | 37 ++++++++++++++++++- 7 files changed, 111 insertions(+), 3 deletions(-) diff --git a/calico-cloud/get-started/system-requirements.mdx b/calico-cloud/get-started/system-requirements.mdx index 75baaeddc5..99c86ffd6a 100644 --- a/calico-cloud/get-started/system-requirements.mdx +++ b/calico-cloud/get-started/system-requirements.mdx @@ -48,6 +48,8 @@ To install Calico Cloud $[cloudUserVersion], your Kubernetes distribution must b | Calico Cloud version | Kubernetes versions | |-----------------------|---------------------| + | 24.1.1 | 1.34-1.36 | + | 24.0.0 | 1.34-1.36 | | 23.0.0 | 1.34-1.36 | | 22.5.0 | 1.31-1.35 | | 22.4.1 | 1.31-1.35 | diff --git a/calico-cloud/release-notes/index.mdx b/calico-cloud/release-notes/index.mdx index 0179651b2f..8f280afe03 100644 --- a/calico-cloud/release-notes/index.mdx +++ b/calico-cloud/release-notes/index.mdx @@ -8,6 +8,41 @@ import IconUser from '/img/icons/user-icon.svg'; # Calico Cloud release notes +

November 3, 2026 (version 24.1.1)

+ +Version 24.1.1 is the next release after 24.0.0. +There is no version 24.1.0. + +The web console changes in this release apply to every managed cluster, whatever version of $[prodname] it runs. + +### New features and enhancements + +#### Resizable YAML panel in the policy editor + +You can now drag the edge of the YAML panel in the policy editor to make it wider or narrower, or collapse it to give the form more room. +The web console remembers the width you choose. + +For more information, see [Network policy tutorial](../network-policy/policy-tiers/policy-tutorial-ui.mdx). + +#### Rule editor opens under the rule + +When you edit a rule in the policy editor, the rule editor now opens directly under that rule, instead of at the end of the list of rules. + +### Deprecated and removed features + +* $[prodname] no longer installs the compliance reporting components on your cluster. + +### Bug fixes + +* Fixed an issue where you couldn't create a policy in a tier other than `default` in the web console on a managed cluster that runs $[prodname] 22 or earlier. + The web console returned an "Incorrectly formatted policy name" error. +* Fixed an issue where you couldn't open or delete a Kubernetes network policy in the web console on a managed cluster that runs $[prodname] 22 or earlier. + +### Known issues + +* You can't connect a Kubernetes 1.36 cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster was installed with the `projectcalico.org/v3` CRDs. + The installation needs the `admissionregistration.k8s.io/v1beta1` API, which Kubernetes 1.36 doesn't provide. +

October 13, 2026 (version 24.0.0)

### New features and enhancements diff --git a/calico-cloud/variables.js b/calico-cloud/variables.js index 1335b4572b..614e0acca1 100644 --- a/calico-cloud/variables.js +++ b/calico-cloud/variables.js @@ -2,7 +2,7 @@ const releases = require('./releases.json'); const variables = { releaseTitle: 'v3.24.0-1.0', - cloudUserVersion: 'v24.0.0', + cloudUserVersion: 'v24.1.1', prodname: 'Calico Cloud', manifestsUrl: 'https://raw.githubusercontent.com/projectcalico/calico/v3.32.0', prodnamedash: 'calico-cloud', diff --git a/calico-cloud_versioned_docs/version-24-1/get-started/system-requirements.mdx b/calico-cloud_versioned_docs/version-24-1/get-started/system-requirements.mdx index 1e7bd9b176..99c86ffd6a 100644 --- a/calico-cloud_versioned_docs/version-24-1/get-started/system-requirements.mdx +++ b/calico-cloud_versioned_docs/version-24-1/get-started/system-requirements.mdx @@ -48,6 +48,7 @@ To install Calico Cloud $[cloudUserVersion], your Kubernetes distribution must b | Calico Cloud version | Kubernetes versions | |-----------------------|---------------------| + | 24.1.1 | 1.34-1.36 | | 24.0.0 | 1.34-1.36 | | 23.0.0 | 1.34-1.36 | | 22.5.0 | 1.31-1.35 | diff --git a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx index 0179651b2f..8f280afe03 100644 --- a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx @@ -8,6 +8,41 @@ import IconUser from '/img/icons/user-icon.svg'; # Calico Cloud release notes +

November 3, 2026 (version 24.1.1)

+ +Version 24.1.1 is the next release after 24.0.0. +There is no version 24.1.0. + +The web console changes in this release apply to every managed cluster, whatever version of $[prodname] it runs. + +### New features and enhancements + +#### Resizable YAML panel in the policy editor + +You can now drag the edge of the YAML panel in the policy editor to make it wider or narrower, or collapse it to give the form more room. +The web console remembers the width you choose. + +For more information, see [Network policy tutorial](../network-policy/policy-tiers/policy-tutorial-ui.mdx). + +#### Rule editor opens under the rule + +When you edit a rule in the policy editor, the rule editor now opens directly under that rule, instead of at the end of the list of rules. + +### Deprecated and removed features + +* $[prodname] no longer installs the compliance reporting components on your cluster. + +### Bug fixes + +* Fixed an issue where you couldn't create a policy in a tier other than `default` in the web console on a managed cluster that runs $[prodname] 22 or earlier. + The web console returned an "Incorrectly formatted policy name" error. +* Fixed an issue where you couldn't open or delete a Kubernetes network policy in the web console on a managed cluster that runs $[prodname] 22 or earlier. + +### Known issues + +* You can't connect a Kubernetes 1.36 cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster was installed with the `projectcalico.org/v3` CRDs. + The installation needs the `admissionregistration.k8s.io/v1beta1` API, which Kubernetes 1.36 doesn't provide. +

October 13, 2026 (version 24.0.0)

### New features and enhancements diff --git a/calico-cloud_versioned_docs/version-24-1/variables.js b/calico-cloud_versioned_docs/version-24-1/variables.js index 1335b4572b..614e0acca1 100644 --- a/calico-cloud_versioned_docs/version-24-1/variables.js +++ b/calico-cloud_versioned_docs/version-24-1/variables.js @@ -2,7 +2,7 @@ const releases = require('./releases.json'); const variables = { releaseTitle: 'v3.24.0-1.0', - cloudUserVersion: 'v24.0.0', + cloudUserVersion: 'v24.1.1', prodname: 'Calico Cloud', manifestsUrl: 'https://raw.githubusercontent.com/projectcalico/calico/v3.32.0', prodnamedash: 'calico-cloud', diff --git a/src/___new___/data/ccImageLists.js b/src/___new___/data/ccImageLists.js index fd4289ceb0..837788c787 100644 --- a/src/___new___/data/ccImageLists.js +++ b/src/___new___/data/ccImageLists.js @@ -1,6 +1,41 @@ const ccImageLists = { + // curl -0 https://installer.calicocloud.io/manifests/v3.24.0-1.0-8/image-list + 'v24.1.1 (latest)': `quay.io/calico/istio-pilot:v3.32.0 +quay.io/calico/istio-install-cni:v3.32.0 +quay.io/calico/istio-ztunnel:v3.32.0 +quay.io/calico/istio-proxyv2:v3.32.0 +quay.io/calico/webhooks:v3.32.0 +quay.io/tigera/calico:v3.24.0-1.0 +quay.io/tigera/compliance-benchmarker:v3.24.0-1.0 +quay.io/tigera/deep-packet-inspection:v3.24.0-1.0 +quay.io/tigera/fluentd:v3.24.0-1.0 +quay.io/tigera/fluentd-windows:v3.24.0-1.0 +quay.io/tigera/intrusion-detection-controller:v3.24.0-1.0 +quay.io/tigera/manager:v3.24.0-1.0 +quay.io/tigera/egress-gateway:v3.24.0-1.0 +quay.io/tigera/gateway-l7-collector:v3.24.0-1.0 +quay.io/tigera/envoy:v3.24.0-1.0 +quay.io/tigera/dikastes:v3.24.0-1.0 +quay.io/tigera/prometheus:v3.24.0-1.0 +quay.io/tigera/alertmanager:v3.24.0-1.0 +quay.io/tigera/node:v3.24.0-1.0 +quay.io/tigera/node-windows:v3.24.0-1.0 +quay.io/tigera/cni-windows:v3.24.0-1.0 +quay.io/tigera/third-party-cni-plugins:v3.24.0-1.0 +quay.io/tigera/envoy-gateway:v3.24.0-1.0 +quay.io/tigera/envoy-proxy:v3.24.0-1.0 +quay.io/tigera/envoy-ratelimit:v3.24.0-1.0 +quay.io/tigera/istio-pilot:v3.24.0-1.0 +quay.io/tigera/istio-install-cni:v3.24.0-1.0 +quay.io/tigera/istio-ztunnel:v3.24.0-1.0 +quay.io/tigera/istio-proxyv2:v3.24.0-1.0 +quay.io/tigera/operator:v1.43.0 +quay.io/tigera/cc-core:v0.4.1 +quay.io/tigera/prometheus-operator:v3.24.0-1.0 +quay.io/tigera/prometheus-config-reloader:v3.24.0-1.0 +quay.io/tigera/cc-cni-config-scanner:v0.7.5`, // curl -0 https://installer.calicocloud.io/manifests/v3.24.0-1.0-4/image-list - 'v24.0.0 (latest)': `quay.io/calico/istio-pilot:v3.32.0 + 'v24.0.0': `quay.io/calico/istio-pilot:v3.32.0 quay.io/calico/istio-install-cni:v3.32.0 quay.io/calico/istio-ztunnel:v3.32.0 quay.io/calico/istio-proxyv2:v3.32.0 From f9d0a1530f58f0b10f144eba4cdbb12d2768f5a3 Mon Sep 17 00:00:00 2001 From: Chris Tauchen Date: Tue, 3 Nov 2026 12:39:47 +0000 Subject: [PATCH 2/3] DOCS-3072: Explain which clusters can't connect to Calico Cloud 24.1.1 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. --- calico-cloud/release-notes/index.mdx | 13 +++++++++++-- .../version-24-1/release-notes/index.mdx | 13 +++++++++++-- 2 files changed, 22 insertions(+), 4 deletions(-) diff --git a/calico-cloud/release-notes/index.mdx b/calico-cloud/release-notes/index.mdx index 8f280afe03..4c06f0a467 100644 --- a/calico-cloud/release-notes/index.mdx +++ b/calico-cloud/release-notes/index.mdx @@ -40,8 +40,17 @@ When you edit a rule in the policy editor, the rule editor now opens directly un ### Known issues -* You can't connect a Kubernetes 1.36 cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster was installed with the `projectcalico.org/v3` CRDs. - The installation needs the `admissionregistration.k8s.io/v1beta1` API, which Kubernetes 1.36 doesn't provide. +* You can't connect a cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster uses the `projectcalico.org/v3` CRDs and the cluster doesn't serve the `admissionregistration.k8s.io/v1beta1` API. + Kubernetes 1.36 doesn't provide this API. + On Kubernetes 1.34 and 1.35, the API is turned off by default. + New installations of Calico Open Source 3.33 use the `projectcalico.org/v3` CRDs by default. + If your cluster is affected, $[prodname] refuses the installation and explains why. + To connect the cluster, do one of the following: + * On Kubernetes 1.34 or 1.35, turn on the `admissionregistration.k8s.io/v1beta1` API and the `MutatingAdmissionPolicy` feature gate on the Kubernetes API server. + * Install Calico Open Source with the aggregation API server instead of the `projectcalico.org/v3` CRDs. + For more information, see [Native v3 CRDs](/calico/latest/operations/native-v3-crds) in the Calico Open Source documentation. + + Support for clusters without this API is planned for a later release of $[prodname].

October 13, 2026 (version 24.0.0)

diff --git a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx index 8f280afe03..4c06f0a467 100644 --- a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx @@ -40,8 +40,17 @@ When you edit a rule in the policy editor, the rule editor now opens directly un ### Known issues -* You can't connect a Kubernetes 1.36 cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster was installed with the `projectcalico.org/v3` CRDs. - The installation needs the `admissionregistration.k8s.io/v1beta1` API, which Kubernetes 1.36 doesn't provide. +* You can't connect a cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster uses the `projectcalico.org/v3` CRDs and the cluster doesn't serve the `admissionregistration.k8s.io/v1beta1` API. + Kubernetes 1.36 doesn't provide this API. + On Kubernetes 1.34 and 1.35, the API is turned off by default. + New installations of Calico Open Source 3.33 use the `projectcalico.org/v3` CRDs by default. + If your cluster is affected, $[prodname] refuses the installation and explains why. + To connect the cluster, do one of the following: + * On Kubernetes 1.34 or 1.35, turn on the `admissionregistration.k8s.io/v1beta1` API and the `MutatingAdmissionPolicy` feature gate on the Kubernetes API server. + * Install Calico Open Source with the aggregation API server instead of the `projectcalico.org/v3` CRDs. + For more information, see [Native v3 CRDs](/calico/latest/operations/native-v3-crds) in the Calico Open Source documentation. + + Support for clusters without this API is planned for a later release of $[prodname].

October 13, 2026 (version 24.0.0)

From 687edd4add71e353424a8746f59297883a60eb57 Mon Sep 17 00:00:00 2001 From: Chris Tauchen Date: Tue, 3 Nov 2026 17:21:07 +0000 Subject: [PATCH 3/3] DOCS-3072: Trim the Calico Cloud 24.1.1 release notes - 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. --- calico-cloud/release-notes/index.mdx | 31 ++++--------------- .../version-24-1/release-notes/index.mdx | 31 ++++--------------- src/___new___/data/ccImageLists.js | 1 - 3 files changed, 12 insertions(+), 51 deletions(-) diff --git a/calico-cloud/release-notes/index.mdx b/calico-cloud/release-notes/index.mdx index 4c06f0a467..0c115157a5 100644 --- a/calico-cloud/release-notes/index.mdx +++ b/calico-cloud/release-notes/index.mdx @@ -10,23 +10,11 @@ import IconUser from '/img/icons/user-icon.svg';

November 3, 2026 (version 24.1.1)

-Version 24.1.1 is the next release after 24.0.0. -There is no version 24.1.0. - -The web console changes in this release apply to every managed cluster, whatever version of $[prodname] it runs. - ### New features and enhancements -#### Resizable YAML panel in the policy editor - -You can now drag the edge of the YAML panel in the policy editor to make it wider or narrower, or collapse it to give the form more room. -The web console remembers the width you choose. - -For more information, see [Network policy tutorial](../network-policy/policy-tiers/policy-tutorial-ui.mdx). - -#### Rule editor opens under the rule +#### Policy editor improvements -When you edit a rule in the policy editor, the rule editor now opens directly under that rule, instead of at the end of the list of rules. +You can now resize the YAML panel in the policy editor, and the rule editor opens directly under the rule you're editing. ### Deprecated and removed features @@ -40,17 +28,10 @@ When you edit a rule in the policy editor, the rule editor now opens directly un ### Known issues -* You can't connect a cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster uses the `projectcalico.org/v3` CRDs and the cluster doesn't serve the `admissionregistration.k8s.io/v1beta1` API. - Kubernetes 1.36 doesn't provide this API. - On Kubernetes 1.34 and 1.35, the API is turned off by default. - New installations of Calico Open Source 3.33 use the `projectcalico.org/v3` CRDs by default. - If your cluster is affected, $[prodname] refuses the installation and explains why. - To connect the cluster, do one of the following: - * On Kubernetes 1.34 or 1.35, turn on the `admissionregistration.k8s.io/v1beta1` API and the `MutatingAdmissionPolicy` feature gate on the Kubernetes API server. - * Install Calico Open Source with the aggregation API server instead of the `projectcalico.org/v3` CRDs. - For more information, see [Native v3 CRDs](/calico/latest/operations/native-v3-crds) in the Calico Open Source documentation. - - Support for clusters without this API is planned for a later release of $[prodname]. +* $[prodname] can't be installed on a cluster where Calico Open Source uses the [`projectcalico.org/v3` CRDs](/calico/latest/operations/native-v3-crds) and the `admissionregistration.k8s.io/v1beta1` API isn't available. + New installations of Calico Open Source 3.33 on Kubernetes 1.36 are set up this way by default. + Calico Open Source 3.33 uses the v3 CRDs, and Kubernetes 1.36 no longer serves the `v1beta1` API by default, because the API was promoted to `v1` when it became generally available. + To install $[prodname] on one of these clusters, make the `v1beta1` API available or add the Calico API server.

October 13, 2026 (version 24.0.0)

diff --git a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx index 4c06f0a467..0c115157a5 100644 --- a/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-24-1/release-notes/index.mdx @@ -10,23 +10,11 @@ import IconUser from '/img/icons/user-icon.svg';

November 3, 2026 (version 24.1.1)

-Version 24.1.1 is the next release after 24.0.0. -There is no version 24.1.0. - -The web console changes in this release apply to every managed cluster, whatever version of $[prodname] it runs. - ### New features and enhancements -#### Resizable YAML panel in the policy editor - -You can now drag the edge of the YAML panel in the policy editor to make it wider or narrower, or collapse it to give the form more room. -The web console remembers the width you choose. - -For more information, see [Network policy tutorial](../network-policy/policy-tiers/policy-tutorial-ui.mdx). - -#### Rule editor opens under the rule +#### Policy editor improvements -When you edit a rule in the policy editor, the rule editor now opens directly under that rule, instead of at the end of the list of rules. +You can now resize the YAML panel in the policy editor, and the rule editor opens directly under the rule you're editing. ### Deprecated and removed features @@ -40,17 +28,10 @@ When you edit a rule in the policy editor, the rule editor now opens directly un ### Known issues -* You can't connect a cluster to $[prodname] 24.1.1 if Calico Open Source on that cluster uses the `projectcalico.org/v3` CRDs and the cluster doesn't serve the `admissionregistration.k8s.io/v1beta1` API. - Kubernetes 1.36 doesn't provide this API. - On Kubernetes 1.34 and 1.35, the API is turned off by default. - New installations of Calico Open Source 3.33 use the `projectcalico.org/v3` CRDs by default. - If your cluster is affected, $[prodname] refuses the installation and explains why. - To connect the cluster, do one of the following: - * On Kubernetes 1.34 or 1.35, turn on the `admissionregistration.k8s.io/v1beta1` API and the `MutatingAdmissionPolicy` feature gate on the Kubernetes API server. - * Install Calico Open Source with the aggregation API server instead of the `projectcalico.org/v3` CRDs. - For more information, see [Native v3 CRDs](/calico/latest/operations/native-v3-crds) in the Calico Open Source documentation. - - Support for clusters without this API is planned for a later release of $[prodname]. +* $[prodname] can't be installed on a cluster where Calico Open Source uses the [`projectcalico.org/v3` CRDs](/calico/latest/operations/native-v3-crds) and the `admissionregistration.k8s.io/v1beta1` API isn't available. + New installations of Calico Open Source 3.33 on Kubernetes 1.36 are set up this way by default. + Calico Open Source 3.33 uses the v3 CRDs, and Kubernetes 1.36 no longer serves the `v1beta1` API by default, because the API was promoted to `v1` when it became generally available. + To install $[prodname] on one of these clusters, make the `v1beta1` API available or add the Calico API server.

October 13, 2026 (version 24.0.0)

diff --git a/src/___new___/data/ccImageLists.js b/src/___new___/data/ccImageLists.js index 837788c787..de51a34d5d 100644 --- a/src/___new___/data/ccImageLists.js +++ b/src/___new___/data/ccImageLists.js @@ -6,7 +6,6 @@ quay.io/calico/istio-ztunnel:v3.32.0 quay.io/calico/istio-proxyv2:v3.32.0 quay.io/calico/webhooks:v3.32.0 quay.io/tigera/calico:v3.24.0-1.0 -quay.io/tigera/compliance-benchmarker:v3.24.0-1.0 quay.io/tigera/deep-packet-inspection:v3.24.0-1.0 quay.io/tigera/fluentd:v3.24.0-1.0 quay.io/tigera/fluentd-windows:v3.24.0-1.0