diff --git a/calico-cloud_versioned_docs/version-23-2/get-started/system-requirements.mdx b/calico-cloud_versioned_docs/version-23-2/get-started/system-requirements.mdx index ac32b7b1c7..75baaeddc5 100644 --- a/calico-cloud_versioned_docs/version-23-2/get-started/system-requirements.mdx +++ b/calico-cloud_versioned_docs/version-23-2/get-started/system-requirements.mdx @@ -38,16 +38,22 @@ The Calico Cloud installer may be able to successfully connect ## Kubernetes versions To install Calico Cloud $[cloudUserVersion], your Kubernetes distribution must be based on one of the following Kubernetes versions: + +* Kubernetes 1.36 +* Kubernetes 1.35 * Kubernetes 1.34 -* Kubernetes 1.33 -* Kubernetes 1.32 -* Kubernetes 1.31
Kubernetes compatibility for older versions of Calico Cloud | Calico Cloud version | Kubernetes versions | |-----------------------|---------------------| + | 23.0.0 | 1.34-1.36 | + | 22.5.0 | 1.31-1.35 | + | 22.4.1 | 1.31-1.35 | + | 22.4.0 | 1.31-1.34 | + | 22.3.0 | 1.31-1.34 | + | 22.2.0 | 1.31-1.34 | | 22.1.0 | 1.31-1.34 | | 22.0.1 | 1.31-1.33 | | 22.0.0 | 1.31-1.33 | @@ -61,12 +67,6 @@ To install Calico Cloud $[cloudUserVersion], your Kubernetes distribution must b | 20.1.0 | 1.28-1.30 | | 20.0.1 | 1.28-1.30 | | 20.0.0 | 1.28-1.30 | - | 19.4.1 | 1.27-1.29 | - | 19.4.0 | 1.27-1.29 | - | 19.3.0 | 1.27-1.29 | - | 19.2.0 | 1.26-1.29 | - | 19.1.0 | 1.26-1.29 | - | 19.0.0 | 1.26-1.28 |
diff --git a/calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx b/calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx index 9d302a22f3..8371ff642c 100644 --- a/calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx +++ b/calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx @@ -4,8 +4,492 @@ title: Calico Cloud release notes sidebar_label: Release notes --- +import IconUser from '/img/icons/user-icon.svg'; + # Calico Cloud release notes +

July 28, 2026 (version 23.0.0)

+ +### New features and enhancements + +#### Programmatic access to usage data + +You can now create a read-only API key in the web console and use it to call the $[prodname] Usage API. +The API returns the same vCPU usage and managed cluster data shown on the Usage Metrics page, so you can pull it into your own capacity planning, FinOps, and license-compliance workflows. + +For more information, see [Access usage data programmatically](../operations/usage-api.mdx). + +#### Maglev load balancing for services + +$[prodname] now supports Maglev consistent-hash load balancing for external traffic to services. +Maglev lets your nodes act as a distributed, horizontally scalable load balancer, so external connections can fail over to another node when a node goes down. +This is useful when you advertise service IPs to your network as ECMP routes. +You enable Maglev per service with an annotation. + +For more information, see [Add Maglev load balancing to a service](../networking/configuring/add-maglev-load-balancing.mdx). + +#### L2 reachability for pods and services without BGP + +You can now make pod IPs and LoadBalancer service VIPs reachable on a flat layer 2 network without BGP or an overlay. +When you enable `localSubnetL2Reachability`, $[prodname] runs a userspace ARP/NDP responder that answers for local pod IPs and LoadBalancer VIPs that share the host subnet. +This is useful for on-premises, edge, and other environments where you can't configure the upstream router. + +For more information, see [L2 reachability for pods and services without BGP](../networking/configuring/local-subnet-l2-reachability.mdx). + +#### Host IP support for egress gateways + +You can now configure egress gateways to use the host node's IP as the source address for outbound traffic, instead of the gateway's pod IP. +This gives external firewalls and services a stable, well-known set of source IPs to allowlist, and lets many application pods share a small fixed set of gateways. +Host IP mode is most useful for on-premises clusters where pod IPs aren't routable outside the cluster. + +For more information, see [Configure egress gateways with host IP support](../networking/egress/egress-gateway-host-ip.mdx). + +#### Load balancer node maintenance + +You can now mark a node for maintenance so the eBPF data plane stops sending new service traffic to its pods while existing connections finish. +This lets you drain nodes for upgrades, repairs, or capacity changes without dropping in-flight sessions or stateful workloads. +This feature is supported on the eBPF data plane only. + +For more information, see [Mark a load balancer node for maintenance](../networking/configuring/mark-lb-node-for-maintenance.mdx). + +#### Support for Kubernetes 1.36 + +This release adds support for Kubernetes 1.36. + +### Deprecated and removed features + +* Image Assurance, Container Threat Detection, and Kibana are removed in this release. + These features were previously deprecated and are no longer available in $[prodname] 23. + +

June 22, 2026 (version 22.5.0)

+ +### New features and enhancements + +* Security Updates + +

June 9, 2026 (version 22.4.1)

+ +### New features and enhancements + +* Adds support for Kubernetes 1.35. + +

May 19, 2026 (version 22.4.0)

+ +### New features and enhancements + +#### Audit logs + +$[prodname] now records audit events for user activity, including user sign-ins and group assignments. +To view them in the web console, go to **Activity > Audit logs**. + +#### Enhancements + +* The **Usage Metrics** page now includes a per-project breakdown of vCPU hours. + +

April 7, 2026 (version 22.3.0)

+ +### New features and enhancements + +#### Notifications for cluster connections + +Administrators can now set up notifications to receive alerts when managed clusters connect to or disconnect from $[prodname]. +This helps platform teams stay informed about cluster availability and take action quickly when clusters become disconnected or unhealthy. + +To configure notifications, click the user icon **> Notifications**. + +

March 5, 2026 (version 22.2.0)

+ +### New features and enhancements + +#### Istio Ambient Mode (tech preview) + +$[prodname] now provides a bundled version of Istio in ambient mode, a sidecarless architecture that delivers robust mTLS encryption and service mesh security while significantly reducing resource consumption and operational overhead. +This implementation, managed by the Tigera Operator, features an enhanced zTunnel proxy that preserves original destination ports so existing Calico and Kubernetes network policies continue to function seamlessly without requiring rewrites. + +For more information, see [Istio Ambient Mode](../compliance/istio/about-istio-ambient.mdx). + +#### Enhancements + +* Enhancements to Calico Cloud dashboards. + +

February 5, 2026 (web console update)

+ +### New features and enhancements + +#### Projects + +This release introduces self-service Projects, allowing you to organize managed clusters into logical groups based on team, environment, or geographic location. +You can now create up to three projects, select hosting regions, and scope observability tools to specific project environments. + +For more information, see [Projects](../tutorials/calico-cloud-features/projects.mdx). + +#### Namespaced access to dashboards + +Administrators can now provide users with namespaced access to dashboards. +This ensures that users view logs and information only for the specific areas they are authorized to manage. +Namespaced access to dashboards can be managed by specifying namespaces in the **View Network Sets** custom role permission. + +:::important +Changes in this release may cause some users to lose access to dashboard data. +To restore access, administrators must edit users' custom roles to add the **View Global Network Sets** permission or the **View Network Sets** permission with the appropriate namespaces. +::: + +For more information, see [Create and assign custom roles](../users/create-and-assign-custom-roles.mdx). + +### Deprecated and removed features + +* Kibana dashboards are deprecated and will be removed in an upcoming release. + During the deprecation period, you will have read-only access to Kibana dashboards. + You can still [create custom dashboards](../observability/create-custom-dashboard.mdx) using Calico Cloud's built-in dashboards. + +

December 1, 2025 (version 22.1.0)

+ +### New features and enhancements + +#### Dashboards are GA + +Calico Cloud's built-in observability dashboards are now generally available. +These integrated views provide cluster operators with a detailed view of network operations, including metrics on traffic flows, policy decisions, and layer 7 (HTTP) requests. +You can supplement the default dashboards by creating your own custom dashboards to suit your specific needs. + +For more information, see [Dashboards](../observability/dashboards.mdx). + +#### Enhancements + +* Added various user experience improvements to dashboards in the web console. + +### Bug fixes + +* Fixed a problem with time range filters for packet captures in Service Graph. +* Fixed a bug that caused incorrect operands to appear when you added ports to a network policy in the web console. + +#### Support for Kubernetes 1.34 + +This release adds support for Kubernetes 1.34. + +### Known issues + +:::warning[breaking change for windows nodes] +Pod networking fails if you install or upgrade to Calico Cloud 22.1.0 on a cluster that has the following: +* The cluster has Windows nodes. +* The cluster's `IPPool` resource has `spec.encapsulation` set to `None`. + +Updating a cluster with Windows nodes and no encapsulation causes pod networking to fail on Windows nodes. + +This issue will be fixed in an upcoming release. +::: + +

October 21, 2025 (web console update)

+ +### New features and enhancements + +* Improved search and user experience for the **Policies** page in the Calico Cloud Free Tier web console. + +### Bug fixes + +* Added various user experience fixes and improvements to dashboards in the web console. + +

October 6, 2025 (version 22.0.1)

+ +### Bug fixes + +* Removed an unnecessary impersonate permission for the calico-guardian ClusterRole. + The guardian now uses direct permissions instead of impersonation, improving cluster security. + +

September 8, 2025 (version 22.0.0)

+ +### New features and enhancements + +#### Calico Ingress Gateway is GA + +Calico Ingress Gateway is now supported with general availability. +Calico Ingress Gateway is an enterprise-hardened, 100% upstream distribution of Envoy Gateway. Envoy Gateway is an implementation of the Kubernetes Gateway API with several extensions that provide advanced security and traffic management features. + +For more information, see [Configure an ingress gateway](../networking/ingress-gateway/about-calico-ingress-gateway.mdx). + +#### External load balancers for Calico Ingress Gateway + +This release adds customization options for specifying external load balancers for `Gateway` resources in your cluster. + +For more information, see [Customize gateway deployment and features](../networking/ingress-gateway/about-calico-ingress-gateway.mdx). + +#### Web application firewall for Calico Ingress Gateway + +The release adds the ability to configure a web application firewall for Calico Ingress Gateway. + +For more information, see [Deploying WAF with an ingress gateway](../threat/deploying-waf-ingress-gateway.mdx). + +#### Enhanced visibility for denied pre-DNAT traffic + +This update delivers flow logs specifically for denied traffic by Calico pre-DNAT policies. +Now, you can quickly identify and understand why certain traffic is being blocked at the earliest stage of packet processing, greatly simplifying troubleshooting and providing assurance that your pre-DNAT policies are effectively enforcing your desired access controls. + +For more information, see [Apply policy to forwarded traffic](../network-policy/hosts/host-forwarded-traffic.mdx). + +#### HTTP header-based matching for application layer policies + +This release includes support for HTTP header-based matching for application layer policies. +You can now write deny and allow rules for L7 ingress traffic by matching values in HTTP headers. + +For more information, see [Global network policy](../reference/resources/globalnetworkpolicy.mdx#httpheadermatch). + +#### Enhancements + +* To support a minimal footprint and simplify resource management, the API server component and its associated resources have been moved from the `tigera-system` namespace to the `calico-system` namespace. + +### Version support + +You can now install or upgrade to the following versions: + +* Calico Cloud 22 +* Calico Cloud 21 +* Calico Cloud 20 + +{/* ### Bug fixes */} + +

August 5, 2025 (web console update)

+ +### New features and enhancements + +#### Predefined user roles for Entra ID groups + +We added support for granting predefined role permissions to Entra ID security groups. +This allows platform administrators to bulk assign access to the Calico Cloud web console without having to create custom roles. + +For more information, see [Give role-based access to an Entra ID group](../users/create-custom-role-for-entra-id-group.mdx). + +

June 23, 2025 (version 21.3.0)

+ +### New features and enhancements + +#### Policy recommendations for Calico Cloud Free Tier + +We added support for policy recommendations for Calico Cloud Free Tier. +The policy recommendations tool provides a set of recommended network policies based on the traffic patterns in your cluster. +When you get a recommendation, you can review, stage, and test the policy before applying it to your cluster. + +For more information, See [Policy recommendations](../free/overview.mdx#policy-recommendations). + +#### Support for WireGuard encryption between clusters + +We added support for WireGuard encryption between federated services and endpoints in different clusters. + +For more information, see [Creating the cluster mesh](../multicluster/kubeconfig.mdx). + + +#### Improvements to flow log reporting for staged network policies + +This release introduces changes to improve how staged network policies are reported in flow logs. +Previously, a flow log reported the action of staged network policy rules at the time a connection was initiated. +For long-lived connections, changing a staged policy did not affect the reported action. +Now, flow logs report the action that represents the current policy rules. +Flow logs report an action that reflects how a new connection would interact with the current staged policies. + +As part of this, we've also added more granular information about policies in the flow logs. +For more information, see [Flow log data types](../observability/elastic/flow/datatypes.mdx). + +#### Security event webhooks for Alertmanager + +We added support for using webhooks to post security alerts directly to Alertmanager. + +For more information, see [Webhooks for security event alerts](../threat/configuring-webhooks.mdx). + +#### View rule details for Web Application Firewall + +You can now use the web console to view details of the default rule set used by Web Application Firewall. +From the **Web Application Firewall** page, click the **Rulesets** tab to open a list of default rules. + +#### Enhancements + +* Added web console support for `AdminNetworkPolicy` and `BaseAdminNetworkPolicy` tiers (view-only). +* Performance and user experience improvements to custom dashboards. + +#### Support for Kubernetes 1.32 and 1.33 + +This release adds support for Kubernetes 1.32 and 1.33. + +### Known issues + +* If your managed cluster includes nodes running Bottlerocket OS, you may encounter installation errors and network connectivity issues when updating to $[prodname] 21.3.0. + + To prevent or resolve these issues, modify the Felix configuration resource by setting the `dnsPolicyMode` parameter to `DelayDeniedPacket`. Apply this patch either before or after updating to $[prodname] 21.3.0: + + ```bash + kubectl patch --type json felixconfigurations.projectcalico.org default -p '[{"op":"add","path":"/spec/dnsPolicyMode","value":"DelayDeniedPacket"}]' + ``` + + This issue is caused by a new default value for the `dnsPolicyMode` parameter in the Felix configuration. + In version 21.3.0, if not explicitly set, `dnsPolicyMode` defaults to `Inline`, which is incompatible with Bottlerocket OS and leads to the described problems. + + This issue will be addressed in an upcoming release. + +## May 5, 2025 (web console update) + +### New features and enhancements + +#### Introducing Calico Cloud Free Tier + +We are excited to introduce Calico Cloud Free Tier, a new offering designed to provide users of Calico Open Source with powerful observability tools at no cost. +If you're running Calico Open Source, you can now connect a cluster to our cloud-based web console to visualize network traffic, understand policy interactions, and gain essential insights into your Kubernetes networking. + +Calico Cloud Free Tier offers a selection of core observability features from the full Calico Cloud platform, focused on helping you understand what's happening within your Calico Open Source cluster. +It leverages Calico's flow logs API (introduced in Calico Open Source 3.30) to securely stream aggregated flow log data from your cluster to the Calico Cloud console. + +Key features include: +* Dashboards. Access pre-built dashboards visualizing traffic volume, DNS activity, and network performance based on the last 24 hours of flow data. +* Service Graph. Get a dynamic, topographical map of service-to-service communication and endpoint flows within your cluster, making it easy to visualize connections and troubleshoot issues. +* Policy board. Inspect your network policies and staged network policies to make sure they're working as you expect. + +To get started, [sign up for a free Calico Cloud account](https://calicocloud.io). + +For more information about Calico Cloud Free Tier, see the [overview](../free/overview.mdx) or the [quickstart guide](../free/quickstart.mdx). + +

April 29, 2025 (version 21.2.0)

+ +### New features and enhancements + +#### New pre-defined user roles + +We added two new pre-defined user roles to help you manage access to Calico Cloud: +* The *User Admin* role has the ability to manage team members and their assigned roles. +* The *Cluster Connection Admin* role has the ability to manage cluster connections and their settings. + +For more information, see [Set up users](../users/user-management.mdx). + +#### Improvements to Dashboards + +This release includes various improvements to the look and performance of the dashboards. +Several dashboards have been renamed to better reflect their content. +* The Data Volume dashboard is now called the Traffic Volume dashboard. +* The L7 dashboard is now called the HTTP Traffic dashboard. +* The TCP Performance dashboard is now called the Network Performance dashboard. + +For more information, see [Dashboards](../observability/dashboards.mdx). + +

April 1, 2025 (version 21.1.0)

+ +### Updated pricing structure + +We've updated our pricing structure to make it easier to understand and manage. +Now we calculate usage based on your vCPU hours, rather than node hours. +And we stopped charging for log data ingestion. + +When you upgrade, you'll notice a few changes: +* The previous metrics (node hours and ingested log data) are gone. +* The historical consumption data will continue to show your older metrics. + +For more information, see [Usage and billing](../operations/usage-metrics.mdx). + +### Changes to version availability + +Beginning with this release, users will not have access to versions of Calico Cloud that are older than the latest version at the time they joined. +For example, if you start using Calico Cloud with version 21.1.0, you will not be able to install version 19.4.0 or version 20.0.0. +As new versions are released, you will have access to all versions released after the version you joined with. + +### Deprecated and removed features + +The Image Assurance and container threat detection features are deprecated and will be removed in a future release. +Not all users will be able to use these deprecated features from this version onward: + +* For users who start using Calico Cloud in April 2025 or later, these feature are not available. +* Legacy users, who started using Calico Cloud before April 2025, can continue to use these features until they are removed in a future release. + +This split availability applies also to the compliance reports feature, which was deprecated in release 20.3.0. + +### Upgrade instructions for users of deprecated features + +By default, new installations and upgrades to Calico Cloud 21.1.0 will disable Image Assurance, container threat detection, and compliance reporting. + +Additional steps are required to enable these features for legacy users who started using Calico Cloud before April 2025. + +For more information, see [Install Calico Cloud](../get-started/install-cluster.mdx) and [Upgrade Calico Cloud](../get-started/upgrade-cluster.mdx). + +

March 10, 2025 (version 21.0.0)

+ +### New features and enhancements + +#### Custom dashboards (tech preview) + +You can now build your own dashboard visualizations by creating new charts and queries in a custom dashboard. +For simple changes, you can import one of the many standard charts and make edits to the query parameters as needed. +Advanced users can create custom charts from scratch to display information from our flow, DNS, and L7 logs. + +For more information, see [Create a custom dashboard](../observability/create-custom-dashboard.mdx). + +#### Introducing Calico Ingress Gateway (tech-preview) + +Calico Cloud now includes the ability to deploy Calico Ingress Gateway which is an Enterprise hardened, 100% upstream distribution of Envoy Gateway. Envoy Gateway is an implementation of the Kubernetes Gateway API with several extensions that provide advanced security and traffic management features. + +For more information, see [Configure an ingress gateway](../networking/ingress-gateway/about-calico-ingress-gateway.mdx). + +#### IPAM for load balancers + +Calico Cloud now extends its IPAM capabilities to support service LoadBalancer IP allocation, providing a centralized, automated approach to managing LoadBalancer IPs within Kubernetes clusters. + +For more information, see [LoadBalancer IP address management](../networking/ipam/service-loadbalancer.mdx). + +#### Enhancements + +* We improved how the web console performs in cases where there are a large number of policy tiers for managed clusters. +To see these optimizations, make sure your managed clusters are running Calico Cloud 21.0.0 or later. + +Calico Cloud versions 18 and earlier are no longer supported. + +For information about upgrading, see [Upgrade Calico Cloud](../get-started/upgrade-cluster.mdx). + +### Deprecated and removed features + +* The admission controller feature, which had been in tech preview, was removed. + +### Version support + +You can now install or upgrade to the following versions: + +* Calico Cloud 21 +* Calico Cloud 20 +* Calico Cloud 19 + +

February 11, 2025 (version 20.4.0)

+ +### New features and enhancements + +#### Exporting custom dashboard cards as CSV files + +You can now export data from your custom dashboard cards as CSV files. +This allows you to analyze the exported data using spreadsheet software or data analysis libraries. + +#### Support for Kubernetes 1.31 + +This release adds support for Kubernetes 1.31. + +#### Control-plane label customization for AKS + +We added support for customizing the namespace labels on AKS clusters. +By default we apply a `control-plane` label to namespaces so that they are exempt from Azure Policy. +If you wish to apply Azure Policy to our namespaces, you can now override this label. + +## January 9, 2025 (web console update) + +### New features and enhancements + +#### Secure web console access with IP allowlists + +We've added support for restricting access to the web console by IP address. +You can now define a list of allowed IP addresses or ranges. +For example, you can allow users to access the web console only from your corporate network. + +To configure an IP allowlist, [open a support ticket](https://tigeraio.my.site.com/community/s/login/). + +

December 19, 2024 (version 20.3.1)

+ +### Bug fixes + +* Previously, updating Calico Cloud introduced breaking changes for some users who had defined network policy tiers with orders higher than the default value. + This was caused by a change to the default tier order to 1,000,000. + Now, during upgrades, the installation script checks to see whether the change in default tier order will cause problems. + If necessary, the script blocks the new installation and prompts the user to adjust their tier order. +* Fixed an issue so that guardian picks up refreshed Service Account tokens which caused an issue on some AKS configurations due to a token expiration change. + ## December 17, 2024 (web console update) ### New features and enhancements @@ -22,6 +506,11 @@ For more information, see [Dashboards](../observability/dashboards.mdx). ## December 3, 2024 (version 20.3.0) +:::info[upgrade notice] +Because of a breaking change, this version is no longer available. +Upgrade instead to Calico Cloud 20.3.1 or later. +::: + ### New features and enhancements #### Image Assurance scan result management @@ -69,6 +558,14 @@ For more information see [Deploy a dual ToR cluster](../networking/configuring/d * All compliance reporting features are deprecated and will be removed in a future release. We're building a new compliance reporting system that will eventually replace the current one. +### Updating + +* ***Breaking change:*** Previously, the default tier had no order and was always evaluated last. + Starting with Calico Cloud 20.3.0, the default tier now has an order of 1,000,000. + When upgrading, you must ensure that existing tiers have a lower order or else policy decisions may be affected. + For more information, see [Get started with policy tiers](../network-policy/policy-tiers/tiered-policy.mdx). + + ## November 6, 2024 (version 20.2.0) ### New features and enhancements @@ -99,15 +596,11 @@ We've provided better access to the detectors we use as part of our Container Th You can now view the complete list of detectors and turn them on or off as you see fit. Detectors can also be configured as part of a new RuntimeSecurity custom resource. -For more information, see Update detector settings. - #### Create Security Event exceptions for known processes We added a way to create Security Event exceptions for processes in your cluster that you know to be safe. This can be a helpful way to eliminate noise and false positives in your alerts. -For more information, see Exclude a process from Security Events alerts. - #### Added EPSS data to Image Assurance results Image Assurance scans results now include information using the [Exploit Prediction Scoring System (EPSS)](https://www.first.org/epss/). @@ -185,8 +678,6 @@ For information about upgrading, see [Upgrade Calico Cloud](../get-started/upgra We added a way to efficiently add large numbers of vulnerability exceptions to your Image Assurance scan results. Instead of creating exceptions one by one, you can add them all at once by uploading a CSV file with the vulnerability definitions. -For more information, see Exclude vulnerabilities from scan results. - ### Bug fixes * Previously, defining new values for the crawdad daemon by using the ImageAssurance custom resource had no effect, and the default values remained in place. @@ -202,9 +693,6 @@ For more information, see Exclude vulnerabilities from scan results. We added a way to create and assign Jira issues directly from your Image Assurance scan results page. You can filter and prioritize vulnerabilities, and then assign the remediation work to members of your team. Calico Cloud populates the information you need, including a CSV file with detailed information about the vulnerabilities in your packages. - -For more information, see Creating Jira issues for scan results. - #### Security events dashboard A new dashboard summarizes security events and helps practitioners easily understand how events map across namespaces, MITRE techniques, event types, and attack phases. This allows first responders to quickly make sense of potential threats, engage the right stakeholders, and start the incident response and investigation process. @@ -272,9 +760,6 @@ For more information, see [Connect a cluster to Calico Cloud](../get-started/ins We added the ability to exclude namespaces from image scanning and runtime view. By excluding certain namespaces, you can reduce noise in your scan results and focus attention on higher priority workloads. - -For more information, see Configure exclusions for image scanning. - ## April 2, 2024 (version 19.1.0) ### Bug fixes @@ -376,7 +861,6 @@ Using a list of prioritized recommended actions, you can start to take steps to Because the dashboard is based on existing Calico Cloud data, no configuration is required. You can start improving the security posture of your Kubernetes cluster immediately. - #### Support for RKE2 This release comes with support for connecting RKE2 clusters to Calico Cloud. @@ -417,9 +901,6 @@ This failed installation message can be disregarded. #### Image Assurance registry scanner The Image Assurance feature adds the ability to scan images in container registries at any time, on any infrastructure, including Kubernetes. This is ideal protection for images that don’t go through a pipeline (for example, third-party images), but are published to a registry. If CVEs are missed in your build pipeline, you can catch them before they are deployed. - -For more information, see Scan images in container registries. - #### Security event management We've added a new Security event management dashboard for threat detection. @@ -530,7 +1011,7 @@ As a workaround, label the CRD so that it is managed by Helm by running the foll ```bash kubectl patch crd installers.operator.calicocloud.io -p '{"metadata": {"annotations": {"meta.helm.sh/release-name":"calico-cloud-crds","meta.helm.sh/release-namespace":"calico-cloud"},"labels":{"app.kubernetes.io/managed-by":"Helm"}}}' - ``` +``` This allows you to successfully reinstall or upgrade to Calico Cloud by following the procedure in [Upgrade Calico Cloud](../get-started/upgrade-cluster.mdx). @@ -723,9 +1204,6 @@ New CLI will now check that it is compatible with the latest Image Assurance API Release of Container Threat Detection With Container Threat Detection, you can monitor container activity using eBPF. Enable this feature to receive alerts based on file and process activity for known malicious and suspicious behavior. Alert events can be viewed on the Alerts page in the web console. - -To get started, see Container Threat Detection. - ## September 26, 2022 ### New feature: Helm @@ -764,8 +1242,6 @@ We've made it easier for platform operators to share Image Assurance scan result * Export one row per image or one row per image and CVE. * Export CSV or JSON files. -To get started, see Image Assurance. - ### Malware detection is GA Malware detection is now released for general availability. @@ -774,9 +1250,6 @@ Calico Cloud's malware detection identifies malicious files in your cluster and Calico Cloud uses eBPF-based monitoring to log file hashes of programs running in your cluster. If there's a match to known malware from our threat intelligence library, you receive an alert. You can view your alerts on the _Alerts_ page on the web console. - -To get started, see Malware Detection. - ## July 27, 2022 Improvement: Export logs to a SIEM @@ -857,6 +1330,4 @@ The $[prodname] installation process will now require running a `kubectl apply` ![tech-preview](/img/calico-cloud/tech-preview.svg) -$[prodname] introduces Image Assurance in tech preview, enabling DevOps and platform teams to scan images in public and private registries, and images that are automatically discovered in connected clusters. Image Assurance provides a runtime view into risk, based on discovered vulnerabilities. It also offers admission controller policies to enforce how vulnerable images are used to create resources within Kubernetes. - -To get started, see Image Assurance. +$[prodname] introduces Image Assurance in tech preview, enabling DevOps and platform teams to scan images in public and private registries, and images that are automatically discovered in connected clusters. Image Assurance provides a runtime view into risk, based on discovered vulnerabilities. It also offers admission controller policies to enforce how vulnerable images are used to create resources within Kubernetes. \ No newline at end of file diff --git a/calico-cloud_versioned_docs/version-23-2/variables.js b/calico-cloud_versioned_docs/version-23-2/variables.js index f6bdf06973..d1392045e8 100644 --- a/calico-cloud_versioned_docs/version-23-2/variables.js +++ b/calico-cloud_versioned_docs/version-23-2/variables.js @@ -1,28 +1,28 @@ const releases = require('./releases.json'); const variables = { - releaseTitle: 'v3.21.0-1.0', - cloudUserVersion: 'v20.4.0', + releaseTitle: 'v3.23.1', + cloudUserVersion: 'v23.0.0', prodname: 'Calico Cloud', + manifestsUrl: 'https://raw.githubusercontent.com/projectcalico/calico/v3.32.0', prodnamedash: 'calico-cloud', baseUrl: '/calico-cloud', filesUrl: 'https://docs.calicocloud.io', - filesUrl_CE: 'https://downloads.tigera.io/ee/v3.21.0-1.0', + filesUrl_CE: 'https://downloads.tigera.io/ee/v3.23.1', tutorialFilesURL: 'https://docs.tigera.io/files', prodnameWindows: 'Calico Enterprise for Windows', rootDirWindows: 'C:\\TigeraCalico', nodecontainer: 'cnx-node', noderunning: 'calico-node', - cloudversion: 'v3.21.0-1.0-4', - clouddownloadurl: 'https://installer.calicocloud.io/manifests/v3.21.0-1.0-4', + cloudversion: 'v3.23.1-4', + clouddownloadurl: 'https://installer.calicocloud.io/manifests/v3.23.1-4', clouddownloadbase: 'https://installer.calicocloud.io', cloudoperatorimage: 'quay.io/tigera/cc-operator', - imageassuranceversion: 'v1.22.6', tigeraOperator: releases[0]['tigera-operator'], dikastesVersion: releases[0].components.dikastes.version, releases, registry: 'quay.io/', - envoyVersion: '1.5.0', + envoyVersion: '1.8.0', imageNames: { node: 'tigera/cnx-node', kubeControllers: 'tigera/kube-controllers', diff --git a/docusaurus.config.js b/docusaurus.config.js index 0d0523bfea..af82a25e09 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -500,14 +500,14 @@ export default async function createAsyncConfig() { routeBasePath: 'calico-cloud', editCurrentVersion: true, //To see builds for unreleased versions, remove comments in the next line. - onlyIncludeVersions: [...nextVersion, '22-2'], + onlyIncludeVersions: [...nextVersion, '23-2'], versions: { current: { label: 'Next', path: 'next', banner: 'unreleased', }, - '22-2': { + '23-2': { path: '/', banner: 'none', }, diff --git a/src/___new___/data/ccImageLists.js b/src/___new___/data/ccImageLists.js index e63026cba4..2a20397a7c 100644 --- a/src/___new___/data/ccImageLists.js +++ b/src/___new___/data/ccImageLists.js @@ -1,6 +1,63 @@ const ccImageLists = { + // curl -0 https://installer.calicocloud.io/manifests/v3.23.1-4/image-list + 'v23.0.0 (latest)': `quay.io/calico/istio-pilot:v3.32.1 +quay.io/calico/istio-install-cni:v3.32.1 +quay.io/calico/istio-ztunnel:v3.32.1 +quay.io/calico/istio-proxyv2:v3.32.1 +quay.io/calico/webhooks:v3.32.1 +quay.io/tigera/apiserver:v3.23.1 +quay.io/tigera/compliance-benchmarker:v3.23.1 +quay.io/tigera/compliance-controller:v3.23.1 +quay.io/tigera/compliance-reporter:v3.23.1 +quay.io/tigera/compliance-snapshotter:v3.23.1 +quay.io/tigera/key-cert-provisioner:v3.23.1 +quay.io/tigera/deep-packet-inspection:v3.23.1 +quay.io/tigera/ui-apis:v3.23.1 +quay.io/tigera/fluentd:v3.23.1 +quay.io/tigera/fluentd-windows:v3.23.1 +quay.io/tigera/guardian:v3.23.1 +quay.io/tigera/intrusion-detection-controller:v3.23.1 +quay.io/tigera/waf-http-filter:v3.23.1 +quay.io/tigera/webhooks-processor:v3.23.1 +quay.io/tigera/manager:v3.23.1 +quay.io/tigera/packetcapture:v3.23.1 +quay.io/tigera/policy-recommendation:v3.23.1 +quay.io/tigera/egress-gateway:v3.23.1 +quay.io/tigera/l7-collector:v3.23.1 +quay.io/tigera/gateway-l7-collector:v3.23.1 +quay.io/tigera/envoy:v3.23.1 +quay.io/tigera/prometheus:v3.23.1 +quay.io/tigera/prometheus-service:v3.23.1 +quay.io/tigera/alertmanager:v3.23.1 +quay.io/tigera/queryserver:v3.23.1 +quay.io/tigera/kube-controllers:v3.23.1 +quay.io/tigera/node:v3.23.1 +quay.io/tigera/node-windows:v3.23.1 +quay.io/tigera/typha:v3.23.1 +quay.io/tigera/cni:v3.23.1 +quay.io/tigera/cni-windows:v3.23.1 +quay.io/tigera/es-gateway:v3.23.1 +quay.io/tigera/linseed:v3.23.1 +quay.io/tigera/dikastes:v3.23.1 +quay.io/tigera/l7-admission-controller:v3.23.1 +quay.io/tigera/pod2daemon-flexvol:v3.23.1 +quay.io/tigera/csi:v3.23.1 +quay.io/tigera/node-driver-registrar:v3.23.1 +quay.io/tigera/envoy-gateway:v3.23.1 +quay.io/tigera/envoy-proxy:v3.23.1 +quay.io/tigera/envoy-ratelimit:v3.23.1 +quay.io/tigera/istio-pilot:v3.23.1 +quay.io/tigera/istio-install-cni:v3.23.1 +quay.io/tigera/istio-ztunnel:v3.23.1 +quay.io/tigera/istio-proxyv2:v3.23.1 +quay.io/tigera/webhooks:v3.23.1 +quay.io/tigera/operator:v1.42.4 +quay.io/tigera/cc-core:v0.3.8 +quay.io/tigera/prometheus-operator:v3.23.1 +quay.io/tigera/prometheus-config-reloader:v3.23.1 +quay.io/tigera/cc-cni-config-scanner:v0.7.3`, // curl -0 https://installer.calicocloud.io/manifests/v3.22.6-0/image-list - 'v22.5.0 (latest)': `quay.io/tigera/apiserver:v3.22.6 + 'v22.5.0': `quay.io/tigera/apiserver:v3.22.6 quay.io/tigera/compliance-benchmarker:v3.22.6 quay.io/tigera/compliance-controller:v3.22.6 quay.io/tigera/compliance-reporter:v3.22.6 @@ -637,278 +694,6 @@ quay.io/tigera/cc-core:v0.2.16 quay.io/tigera/prometheus-operator:v3.21.0-1.0 quay.io/tigera/prometheus-config-reloader:v3.21.0-1.0 quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.1-2/image-list - 'v20.4.0': `quay.io/tigera/cnx-apiserver:v3.20.1 -quay.io/tigera/compliance-benchmarker:v3.20.1 -quay.io/tigera/compliance-controller:v3.20.1 -quay.io/tigera/compliance-reporter:v3.20.1 -quay.io/tigera/compliance-snapshotter:v3.20.1 -quay.io/tigera/key-cert-provisioner:v3.20.1 -quay.io/tigera/deep-packet-inspection:v3.20.1 -quay.io/tigera/fluentd:v3.20.1 -quay.io/tigera/fluentd-windows:v3.20.1 -quay.io/tigera/guardian:v3.20.1 -quay.io/tigera/intrusion-detection-controller:v3.20.1 -quay.io/tigera/webhooks-processor:v3.20.1 -quay.io/tigera/packetcapture:v3.20.1 -quay.io/tigera/policy-recommendation:v3.20.1 -quay.io/tigera/egress-gateway:v3.20.1 -quay.io/tigera/l7-collector:v3.20.1 -quay.io/tigera/envoy:v3.20.1 -quay.io/tigera/prometheus:v3.20.1 -quay.io/tigera/prometheus-service:v3.20.1 -quay.io/tigera/alertmanager:v3.20.1 -quay.io/tigera/cnx-queryserver:v3.20.1 -quay.io/tigera/kube-controllers:v3.20.1 -quay.io/tigera/cnx-node:v3.20.1 -quay.io/tigera/cnx-node-windows:v3.20.1 -quay.io/tigera/typha:v3.20.1 -quay.io/tigera/cni:v3.20.1 -quay.io/tigera/cni-windows:v3.20.1 -quay.io/tigera/es-gateway:v3.20.1 -quay.io/tigera/linseed:v3.20.1 -quay.io/tigera/dikastes:v3.20.1 -quay.io/tigera/l7-admission-controller:v3.20.1 -quay.io/tigera/pod2daemon-flexvol:v3.20.1 -quay.io/tigera/csi:v3.20.1 -quay.io/tigera/node-driver-registrar:v3.20.1 -quay.io/tigera/operator:v1.36.5 -quay.io/tigera/image-assurance-admission-controller:v1.22.6 -quay.io/tigera/image-assurance-operator:v1.22.6 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.22.6 -quay.io/tigera/image-assurance-cluster-scanner:v1.22.6 -quay.io/tigera/runtime-security-operator:v1.23.0 -quay.io/tigera/skimble:v1.23.0 -quay.io/tigera/cc-core:v0.2.15 -quay.io/tigera/prometheus-operator:v3.20.1 -quay.io/tigera/prometheus-config-reloader:v3.20.1 -quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.0-2.0-10/image-list - 'v20.3.1': `quay.io/tigera/cnx-apiserver:v3.20.0-2.0 -quay.io/tigera/compliance-benchmarker:v3.20.0-2.0 -quay.io/tigera/compliance-controller:v3.20.0-2.0 -quay.io/tigera/compliance-reporter:v3.20.0-2.0 -quay.io/tigera/compliance-snapshotter:v3.20.0-2.0 -quay.io/tigera/key-cert-provisioner:v3.20.0-2.0 -quay.io/tigera/deep-packet-inspection:v3.20.0-2.0 -quay.io/tigera/fluentd:v3.20.0-2.0 -quay.io/tigera/fluentd-windows:v3.20.0-2.0 -quay.io/tigera/guardian:v3.20.0-2.3 -quay.io/tigera/intrusion-detection-controller:v3.20.0-2.0 -quay.io/tigera/webhooks-processor:v3.20.0-2.0 -quay.io/tigera/packetcapture:v3.20.0-2.0 -quay.io/tigera/policy-recommendation:v3.20.0-2.0 -quay.io/tigera/egress-gateway:v3.20.0-2.0 -quay.io/tigera/l7-collector:v3.20.0-2.0 -quay.io/tigera/envoy:v3.20.0-2.0 -quay.io/tigera/prometheus:v3.20.0-2.0 -quay.io/tigera/prometheus-service:v3.20.0-2.0 -quay.io/tigera/alertmanager:v3.20.0-2.0 -quay.io/tigera/cnx-queryserver:v3.20.0-2.0 -quay.io/tigera/kube-controllers:v3.20.0-2.0 -quay.io/tigera/cnx-node:v3.20.0-2.0 -quay.io/tigera/cnx-node-windows:v3.20.0-2.0 -quay.io/tigera/typha:v3.20.0-2.0 -quay.io/tigera/cni:v3.20.0-2.0 -quay.io/tigera/cni-windows:v3.20.0-2.0 -quay.io/tigera/es-gateway:v3.20.0-2.0 -quay.io/tigera/linseed:v3.20.0-2.0 -quay.io/tigera/dikastes:v3.20.0-2.0 -quay.io/tigera/l7-admission-controller:v3.20.0-2.0 -quay.io/tigera/pod2daemon-flexvol:v3.20.0-2.0 -quay.io/tigera/csi:v3.20.0-2.0 -quay.io/tigera/node-driver-registrar:v3.20.0-2.0 -quay.io/tigera/operator:v1.36.1.1 -quay.io/tigera/image-assurance-admission-controller:v1.22.1 -quay.io/tigera/image-assurance-operator:v1.22.1 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.22.1 -quay.io/tigera/image-assurance-cluster-scanner:v1.22.1 -quay.io/tigera/runtime-security-operator:v1.23.0 -quay.io/tigera/skimble:v1.23.0 -quay.io/tigera/cc-core:v0.2.13 -quay.io/tigera/prometheus-operator:v3.20.0-2.0 -quay.io/tigera/prometheus-config-reloader:v3.20.0-2.0 -quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.0-1.0-18/image-list - 'v20.2.0': `quay.io/tigera/operator:v1.35.2 -quay.io/tigera/cnx-apiserver:v3.20.0-1.0 -quay.io/tigera/compliance-benchmarker:v3.20.0-1.0 -quay.io/tigera/compliance-controller:v3.20.0-1.0 -quay.io/tigera/compliance-reporter:v3.20.0-1.0 -quay.io/tigera/compliance-snapshotter:v3.20.0-1.0 -quay.io/tigera/key-cert-provisioner:v3.20.0-1.0 -quay.io/tigera/deep-packet-inspection:v3.20.0-1.0 -quay.io/tigera/fluentd:v3.20.0-1.0 -quay.io/tigera/fluentd-windows:v3.20.0-1.0 -quay.io/tigera/guardian:v3.20.0-1.5 -quay.io/tigera/intrusion-detection-controller:v3.20.0-1.0 -quay.io/tigera/webhooks-processor:v3.20.0-1.6 -quay.io/tigera/packetcapture:v3.20.0-1.0 -quay.io/tigera/policy-recommendation:v3.20.0-1.0 -quay.io/tigera/egress-gateway:v3.20.0-1.0 -quay.io/tigera/l7-collector:v3.20.0-1.0 -quay.io/tigera/envoy:v3.20.0-1.0 -quay.io/tigera/prometheus:v3.20.0-1.0 -quay.io/tigera/prometheus-service:v3.20.0-1.0 -quay.io/tigera/alertmanager:v3.20.0-1.0 -quay.io/tigera/cnx-queryserver:v3.20.0-1.0 -quay.io/tigera/kube-controllers:v3.20.0-1.0 -quay.io/tigera/cnx-node:v3.20.0-1.0 -quay.io/tigera/cnx-node-windows:v3.20.0-1.0 -quay.io/tigera/typha:v3.20.0-1.0 -quay.io/tigera/cni:v3.20.0-1.0 -quay.io/tigera/cni-windows:v3.20.0-1.0 -quay.io/tigera/es-gateway:v3.20.0-1.0 -quay.io/tigera/linseed:v3.20.0-1.0 -quay.io/tigera/dikastes:v3.20.0-1.0 -quay.io/tigera/pod2daemon-flexvol:v3.20.0-1.0 -quay.io/tigera/csi:v3.20.0-1.0 -quay.io/tigera/node-driver-registrar:v3.20.0-1.0 -quay.io/tigera/image-assurance-admission-controller:v1.21.0 -quay.io/tigera/image-assurance-operator:v1.21.0 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.21.0 -quay.io/tigera/image-assurance-cluster-scanner:v1.21.0 -quay.io/tigera/runtime-security-operator:v1.22.0 -quay.io/tigera/skimble:v1.22.0 -quay.io/tigera/cc-core:v0.2.9 -quay.io/tigera/prometheus-operator:v3.20.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.20.0-1.0 -quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.0-1.0-13/image-list - 'v20.1.0': `quay.io/tigera/operator:v1.35.1 -quay.io/tigera/cnx-apiserver:v3.20.0-1.0 -quay.io/tigera/compliance-benchmarker:v3.20.0-1.0 -quay.io/tigera/compliance-controller:v3.20.0-1.0 -quay.io/tigera/compliance-reporter:v3.20.0-1.0 -quay.io/tigera/compliance-snapshotter:v3.20.0-1.0 -quay.io/tigera/key-cert-provisioner:v3.20.0-1.0 -quay.io/tigera/deep-packet-inspection:v3.20.0-1.0 -quay.io/tigera/fluentd:v3.20.0-1.0 -quay.io/tigera/fluentd-windows:v3.20.0-1.0 -quay.io/tigera/guardian:v3.20.0-1.5 -quay.io/tigera/intrusion-detection-controller:v3.20.0-1.0 -quay.io/tigera/webhooks-processor:v3.20.0-1.0 -quay.io/tigera/packetcapture:v3.20.0-1.0 -quay.io/tigera/policy-recommendation:v3.20.0-1.0 -quay.io/tigera/egress-gateway:v3.20.0-1.0 -quay.io/tigera/l7-collector:v3.20.0-1.0 -quay.io/tigera/envoy:v3.20.0-1.0 -quay.io/tigera/prometheus:v3.20.0-1.0 -quay.io/tigera/prometheus-service:v3.20.0-1.0 -quay.io/tigera/alertmanager:v3.20.0-1.0 -quay.io/tigera/cnx-queryserver:v3.20.0-1.0 -quay.io/tigera/kube-controllers:v3.20.0-1.0 -quay.io/tigera/cnx-node:v3.20.0-1.0 -quay.io/tigera/cnx-node-windows:v3.20.0-1.0 -quay.io/tigera/typha:v3.20.0-1.0 -quay.io/tigera/cni:v3.20.0-1.0 -quay.io/tigera/cni-windows:v3.20.0-1.0 -quay.io/tigera/es-gateway:v3.20.0-1.0 -quay.io/tigera/linseed:v3.20.0-1.0 -quay.io/tigera/dikastes:v3.20.0-1.0 -quay.io/tigera/pod2daemon-flexvol:v3.20.0-1.0 -quay.io/tigera/csi:v3.20.0-1.0 -quay.io/tigera/node-driver-registrar:v3.20.0-1.0 -quay.io/tigera/image-assurance-admission-controller:v1.20.3 -quay.io/tigera/image-assurance-operator:v1.20.3 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.20.3 -quay.io/tigera/image-assurance-cluster-scanner:v1.20.3 -quay.io/tigera/runtime-security-operator:v1.21.0 -quay.io/tigera/skimble:v1.21.0 -quay.io/tigera/cc-core:v0.2.7 -quay.io/tigera/prometheus-operator:v3.20.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.20.0-1.0 -quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.0-1.0-10/image-list - 'v20.0.1': `quay.io/tigera/operator:v1.35.1 -quay.io/tigera/cnx-apiserver:v3.20.0-1.0 -quay.io/tigera/compliance-benchmarker:v3.20.0-1.0 -quay.io/tigera/compliance-controller:v3.20.0-1.0 -quay.io/tigera/compliance-reporter:v3.20.0-1.0 -quay.io/tigera/compliance-snapshotter:v3.20.0-1.0 -quay.io/tigera/key-cert-provisioner:v3.20.0-1.0 -quay.io/tigera/deep-packet-inspection:v3.20.0-1.0 -quay.io/tigera/fluentd:v3.20.0-1.0 -quay.io/tigera/fluentd-windows:v3.20.0-1.0 -quay.io/tigera/guardian:v3.20.0-1.5 -quay.io/tigera/intrusion-detection-controller:v3.20.0-1.0 -quay.io/tigera/webhooks-processor:v3.20.0-1.0 -quay.io/tigera/packetcapture:v3.20.0-1.0 -quay.io/tigera/policy-recommendation:v3.20.0-1.0 -quay.io/tigera/egress-gateway:v3.20.0-1.0 -quay.io/tigera/l7-collector:v3.20.0-1.0 -quay.io/tigera/envoy:v3.20.0-1.0 -quay.io/tigera/prometheus:v3.20.0-1.0 -quay.io/tigera/prometheus-service:v3.20.0-1.0 -quay.io/tigera/alertmanager:v3.20.0-1.0 -quay.io/tigera/cnx-queryserver:v3.20.0-1.0 -quay.io/tigera/kube-controllers:v3.20.0-1.0 -quay.io/tigera/cnx-node:v3.20.0-1.0 -quay.io/tigera/cnx-node-windows:v3.20.0-1.0 -quay.io/tigera/typha:v3.20.0-1.0 -quay.io/tigera/cni:v3.20.0-1.0 -quay.io/tigera/cni-windows:v3.20.0-1.0 -quay.io/tigera/es-gateway:v3.20.0-1.0 -quay.io/tigera/linseed:v3.20.0-1.0 -quay.io/tigera/dikastes:v3.20.0-1.0 -quay.io/tigera/pod2daemon-flexvol:v3.20.0-1.0 -quay.io/tigera/csi:v3.20.0-1.0 -quay.io/tigera/node-driver-registrar:v3.20.0-1.0 -quay.io/tigera/image-assurance-admission-controller:v1.19.5 -quay.io/tigera/image-assurance-operator:v1.19.5 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.19.5 -quay.io/tigera/image-assurance-cluster-scanner:v1.19.5 -quay.io/tigera/runtime-security-operator:v1.20.0 -quay.io/tigera/skimble:v1.20.0 -quay.io/tigera/cc-core:v0.2.7 -quay.io/tigera/prometheus-operator:v3.20.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.20.0-1.0 -quay.io/tigera/cc-cni-config-scanner:v0.3`, - // curl -0 https://installer.calicocloud.io/manifests/v3.20.0-1.0-9/image-list - 'v20.0.0': `quay.io/tigera/operator:v1.35.0 -quay.io/tigera/cnx-apiserver:v3.20.0-1.0 -quay.io/tigera/compliance-benchmarker:v3.20.0-1.0 -quay.io/tigera/compliance-controller:v3.20.0-1.0 -quay.io/tigera/compliance-reporter:v3.20.0-1.0 -quay.io/tigera/compliance-snapshotter:v3.20.0-1.0 -quay.io/tigera/key-cert-provisioner:v3.20.0-1.0 -quay.io/tigera/deep-packet-inspection:v3.20.0-1.0 -quay.io/tigera/fluentd:v3.20.0-1.0 -quay.io/tigera/fluentd-windows:v3.20.0-1.0 -quay.io/tigera/guardian:v3.20.0-1.0 -quay.io/tigera/intrusion-detection-controller:v3.20.0-1.0 -quay.io/tigera/webhooks-processor:v3.20.0-1.0 -quay.io/tigera/packetcapture:v3.20.0-1.0 -quay.io/tigera/policy-recommendation:v3.20.0-1.0 -quay.io/tigera/egress-gateway:v3.20.0-1.0 -quay.io/tigera/l7-collector:v3.20.0-1.0 -quay.io/tigera/envoy:v3.20.0-1.0 -quay.io/tigera/prometheus:v3.20.0-1.0 -quay.io/tigera/prometheus-service:v3.20.0-1.0 -quay.io/tigera/alertmanager:v3.20.0-1.0 -quay.io/tigera/cnx-queryserver:v3.20.0-1.0 -quay.io/tigera/kube-controllers:v3.20.0-1.0 -quay.io/tigera/cnx-node:v3.20.0-1.0 -quay.io/tigera/cnx-node-windows:v3.20.0-1.0 -quay.io/tigera/typha:v3.20.0-1.0 -quay.io/tigera/cni:v3.20.0-1.0 -quay.io/tigera/cni-windows:v3.20.0-1.0 -quay.io/tigera/es-gateway:v3.20.0-1.0 -quay.io/tigera/linseed:v3.20.0-1.0 -quay.io/tigera/dikastes:v3.20.0-1.0 -quay.io/tigera/pod2daemon-flexvol:v3.20.0-1.0 -quay.io/tigera/csi:v3.20.0-1.0 -quay.io/tigera/node-driver-registrar:v3.20.0-1.0 -quay.io/tigera/image-assurance-admission-controller:v1.19.5 -quay.io/tigera/image-assurance-operator:v1.19.5 -quay.io/tigera/image-assurance-container-runtime-adaptor:v1.19.5 -quay.io/tigera/image-assurance-cluster-scanner:v1.19.5 -quay.io/tigera/runtime-security-operator:v1.20.0 -quay.io/tigera/skimble:v1.20.0 -quay.io/tigera/cc-core:v0.2.7 -quay.io/tigera/prometheus-operator:v3.20.0-1.0 -quay.io/tigera/prometheus-config-reloader:v3.20.0-1.0 -quay.io/tigera/cc-cni-config-scanner:v0.2`, }; export default ccImageLists;