diff --git a/calico-cloud/get-started/install-cluster.mdx b/calico-cloud/get-started/install-cluster.mdx index 810273c340..496f8ead96 100644 --- a/calico-cloud/get-started/install-cluster.mdx +++ b/calico-cloud/get-started/install-cluster.mdx @@ -17,6 +17,7 @@ You can quickly connect a cluster to Calico Cloud by generating a unique kubectl ## Connect a cluster to Calico Cloud with kubectl +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. @@ -45,6 +46,7 @@ You can quickly connect a cluster to Calico Cloud by generating a unique kubectl ## Connect a cluster to Calico Cloud with Helm +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. diff --git a/calico-cloud/get-started/install-private-registry.mdx b/calico-cloud/get-started/install-private-registry.mdx index 9226a8dbac..c9b0e12721 100644 --- a/calico-cloud/get-started/install-private-registry.mdx +++ b/calico-cloud/get-started/install-private-registry.mdx @@ -26,6 +26,7 @@ You can perform a Helm installation from images stored on a private registry. ## Install Calico Cloud using a private registry +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. We always recommend the latest version, which is installed by default. diff --git a/calico-cloud/get-started/setup-private-registry.mdx b/calico-cloud/get-started/setup-private-registry.mdx index d3e093def8..2c675ee272 100644 --- a/calico-cloud/get-started/setup-private-registry.mdx +++ b/calico-cloud/get-started/setup-private-registry.mdx @@ -42,6 +42,7 @@ Add the required $[prodname] images to a private registry. ### Set up registry credentials 1. Log into $[prodname] and navigate to "Managed Clusters". +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. Get the "Registry Credentials" by clicking on the icon. ![registry credentials](/img/calico-cloud/private-registry-icon.png) 1. Apply the credentials so the $[prodname] images can be accessed. diff --git a/calico-cloud/get-started/upgrade-cluster.mdx b/calico-cloud/get-started/upgrade-cluster.mdx index 0b697cfc53..3085316087 100644 --- a/calico-cloud/get-started/upgrade-cluster.mdx +++ b/calico-cloud/get-started/upgrade-cluster.mdx @@ -4,9 +4,10 @@ description: Steps to upgrade to the latest version of Calico Cloud. # Upgrade Calico Cloud -To upgrade managed clusters to the latest version of $[prodname]: +To upgrade a managed cluster to the latest version of $[prodname]: -1. From the web console, go to **Managed Clusters**. +1. From the web console, go to the **Managed Clusters** page. +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. For the cluster you want to upgrade, select **Actions** > **Reinstall**. 1. In the **Reinstall Cluster** dialog, select a newer version of $[prodname] from the list, click **Reinstall**, and copy the generated kubectl command.
diff --git a/calico-cloud/observability/dashboards.mdx b/calico-cloud/observability/dashboards.mdx index 36ffcf2e62..2066482832 100644 --- a/calico-cloud/observability/dashboards.mdx +++ b/calico-cloud/observability/dashboards.mdx @@ -11,6 +11,7 @@ import IconGripLines from '/img/icons/grip-lines.svg'; Dashboards help you see what's going on in your cluster. See how your cluster is performing and visualize your system's log data. + ## About dashboards $[prodname] provides a set of dashboards to help you understand the activity in your cluster. @@ -18,7 +19,24 @@ Each dashboard is made up of graphs, charts, and diagrams that visually represen To view your dashboards, sign in to the web console and click the **Dashboards** icon. -Not all users have access to dashboards. +You can also create your own arrangement by creating a custom dashboard. +With a custom dashboard, you can combine and arrange cards from any of the other dashboards. + +Creating custom dashboards is limited to users with Owner, Admin, or Dashboards Admin permissions. + +## Role access to dashboards + +The following user roles have access to all information in an organization's dashboards: + +* Owner +* Admin +* Dashboards Admin +* Devops +* Security +* Viewer + +Users must be assigned one of the standard roles above, or a custom role with dashboard permissions, to access dashboards. +Administrators can limit dashboard access for custom roles, for example to specific clusters or namespaces in a cluster. ### Cluster Health diff --git a/calico-cloud/observability/kibana.mdx b/calico-cloud/observability/kibana.mdx index 3dd17e077b..6b12672014 100644 --- a/calico-cloud/observability/kibana.mdx +++ b/calico-cloud/observability/kibana.mdx @@ -4,6 +4,14 @@ description: Learn the basics of using Elasticsearch logs and Kibana to gain vis # Kibana dashboards and logs +:::warning[deprecation and removal notice] + +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](create-custom-dashboard.mdx) using Calico Cloud's built-in dashboards. + +::: + ## Kibana Kibana is the frontend for $[prodname] Elasticsearch, which is the logging infrastructure that centrally stores logs from all managed clusters. Kibana provides an interface to explore Elasticsearch logs and gain insights into workload communication traffic volume, performance, and other key aspects of cluster operations. Log data is also summarized in custom dashboards. diff --git a/calico-cloud/tutorials/calico-cloud-features/projects.mdx b/calico-cloud/tutorials/calico-cloud-features/projects.mdx new file mode 100644 index 0000000000..da65482095 --- /dev/null +++ b/calico-cloud/tutorials/calico-cloud-features/projects.mdx @@ -0,0 +1,59 @@ +--- +description: About projects +--- + +import Screenshot from '/src/___new___/components/Screenshot'; + + +# Projects + +You can use projects to organize your managed clusters into logical groupings. + + + +## About projects + +In $[prodname], a *project* is a logical grouping of one or more managed clusters. +You can use projects to organize your managed clusters in ways that are useful for your organization. +For example, you can use projects to segregate clusters by product teams, or by geo location. + +When you view observability tools in Calico Cloud, you see only what is available for the current project. + +All Calico Cloud organizations start with a single default project. +You can have up to three projects at a given time. + +## Create a project + +**Prerequisites** + +* You have Admin or Owner privileges. + +**Procedure** + +1. From any page in the web console, click the **Project** menu and then click **Manage Projects**. +1. On the **Projects** page, click **Add Project**. +1. Enter a name and description for the project, and then click the **Add Project** button. + + Provisioning the new project takes a few minutes. + When provisioning is complete, you can begin connecting clusters. + +## Connect a cluster to a project + +* To connect a cluster to a specific project, make sure you have selected the project you want as you follow the procedure to [connect your cluster to Calico Cloud](../../get-started/install-cluster.mdx). + +## Move a managed cluster to another project + +You can move a managed cluster to another project by removing it from the original project and connecting it to the new project. + +:::warning +Log data held by Calico Cloud will be deleted when you remove your cluster from the original project. +When you reconnect your cluster to Calico Cloud as part of the new project, flow logs will start to be collected again. +You will not be able to restore access to the old logs. + +If you need to retain logs, contact [our support team](https://tigeraio.my.site.com/community/s/login/). +::: + +1. To remove your cluster from Calico Cloud, find your cluster on the **Managed Clusters** page, and then click **Actions > Delete**. + After a moment, the cluster is removed from the list. +1. Move to the new project by clicking the **Projects** menu and selecting your project. +1. To reconnect your cluster, follow the guide to [connect your cluster to Calico Cloud](../../get-started/install-cluster.mdx). diff --git a/calico-cloud/users/create-and-assign-custom-roles.mdx b/calico-cloud/users/create-and-assign-custom-roles.mdx index a0c35e0f73..59aa5c69b0 100644 --- a/calico-cloud/users/create-and-assign-custom-roles.mdx +++ b/calico-cloud/users/create-and-assign-custom-roles.mdx @@ -18,6 +18,7 @@ But in some cases these global roles can be too broad. By creating and assigning custom roles, you can be much more discriminating about what permissions you give users. For example, you could create a role that allows the user to modify network policy for a particular tier and namespace and gives view access to all other network policies. +Or you can add permissions for a user to view dashboards that show data from only one namespace in a cluster. Permissions are assigned on a cluster-by-cluster basis. ## Required permissions for common $[prodname] features @@ -28,7 +29,7 @@ Certain permissions are required for a user to access common $[prodname] feature | --| -- | -- | | Alerts | • **View Alerts**
and
•**View All Logs** | | | Compliance reports | • **View Compliance Reports** | | -| Dashboard | • **View All Logs**
and
• **View Global Network Sets** or **View Network Sets**
and (optional)
• **View Compliance Reports** | These permissions are required for the dashboard to fully populate. All users are granted limited dashboard metrics by having access to a cluster. | +| Dashboard | • **View All Logs**
and
• **View Global Network Sets** or **View Network Sets**
and (optional)
• **View Compliance Reports** | These permissions are required for the dashboard to fully populate. All users are granted limited dashboard metrics by having access to a cluster. Users with **View Network Sets** have access to dashboards that show data only from namespaces that they have been explicitly given access to. | | Network policies | • **View** or **Modify Policies**
or
• **View** or **Modify Global Policies**
and (optional)
• **View Audit Logs** or **View All Logs** | The **Policies** permissions apply to one or more namespaces. The **Global Policies** permissions apply to the whole cluster. These permissions are also scoped by [policy tier](../network-policy/policy-tiers/tiered-policy.mdx).

The optional **View Audit Logs** or **View All Logs** let users view the change history on the policies. | | Service graph | • **View All Logs**
and
• **View** or **Modify Network Sets**
and (optional)
• **View** or **Modify Packet Captures** | Network sets can be restricted to a namespace or set to all namespaces to see all flows. | | Threat feeds | • **View** or **Modify Threat Feeds** | | diff --git a/calico-cloud_versioned_docs/version-22-2/get-started/install-cluster.mdx b/calico-cloud_versioned_docs/version-22-2/get-started/install-cluster.mdx index 810273c340..496f8ead96 100644 --- a/calico-cloud_versioned_docs/version-22-2/get-started/install-cluster.mdx +++ b/calico-cloud_versioned_docs/version-22-2/get-started/install-cluster.mdx @@ -17,6 +17,7 @@ You can quickly connect a cluster to Calico Cloud by generating a unique kubectl ## Connect a cluster to Calico Cloud with kubectl +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. @@ -45,6 +46,7 @@ You can quickly connect a cluster to Calico Cloud by generating a unique kubectl ## Connect a cluster to Calico Cloud with Helm +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. diff --git a/calico-cloud_versioned_docs/version-22-2/get-started/install-private-registry.mdx b/calico-cloud_versioned_docs/version-22-2/get-started/install-private-registry.mdx index 9226a8dbac..c9b0e12721 100644 --- a/calico-cloud_versioned_docs/version-22-2/get-started/install-private-registry.mdx +++ b/calico-cloud_versioned_docs/version-22-2/get-started/install-private-registry.mdx @@ -26,6 +26,7 @@ You can perform a Helm installation from images stored on a private registry. ## Install Calico Cloud using a private registry +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. From the **Managed Clusters** page, click **Connect Cluster**. 1. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**. 1. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. We always recommend the latest version, which is installed by default. diff --git a/calico-cloud_versioned_docs/version-22-2/get-started/setup-private-registry.mdx b/calico-cloud_versioned_docs/version-22-2/get-started/setup-private-registry.mdx index d3e093def8..2c675ee272 100644 --- a/calico-cloud_versioned_docs/version-22-2/get-started/setup-private-registry.mdx +++ b/calico-cloud_versioned_docs/version-22-2/get-started/setup-private-registry.mdx @@ -42,6 +42,7 @@ Add the required $[prodname] images to a private registry. ### Set up registry credentials 1. Log into $[prodname] and navigate to "Managed Clusters". +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. Get the "Registry Credentials" by clicking on the icon. ![registry credentials](/img/calico-cloud/private-registry-icon.png) 1. Apply the credentials so the $[prodname] images can be accessed. diff --git a/calico-cloud_versioned_docs/version-22-2/get-started/upgrade-cluster.mdx b/calico-cloud_versioned_docs/version-22-2/get-started/upgrade-cluster.mdx index 0b697cfc53..3085316087 100644 --- a/calico-cloud_versioned_docs/version-22-2/get-started/upgrade-cluster.mdx +++ b/calico-cloud_versioned_docs/version-22-2/get-started/upgrade-cluster.mdx @@ -4,9 +4,10 @@ description: Steps to upgrade to the latest version of Calico Cloud. # Upgrade Calico Cloud -To upgrade managed clusters to the latest version of $[prodname]: +To upgrade a managed cluster to the latest version of $[prodname]: -1. From the web console, go to **Managed Clusters**. +1. From the web console, go to the **Managed Clusters** page. +1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of. 1. For the cluster you want to upgrade, select **Actions** > **Reinstall**. 1. In the **Reinstall Cluster** dialog, select a newer version of $[prodname] from the list, click **Reinstall**, and copy the generated kubectl command.
diff --git a/calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx b/calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx index b2a782f1c9..3ffe03485b 100644 --- a/calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx +++ b/calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx @@ -11,6 +11,7 @@ import IconGripLines from '/img/icons/grip-lines.svg'; Dashboards help you see what's going on in your cluster. See how your cluster is performing and visualize your system's log data. + ## About dashboards Calico Cloud provides a set of dashboards to help you understand the activity in your cluster. @@ -21,8 +22,21 @@ To view your dashboards, sign in to the web console and click the February 3, 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 @@ -288,7 +318,7 @@ For more information, see [Configure an ingress gateway](../networking/ingress-g #### 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. +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). diff --git a/calico-cloud_versioned_docs/version-22-2/tutorials/calico-cloud-features/projects.mdx b/calico-cloud_versioned_docs/version-22-2/tutorials/calico-cloud-features/projects.mdx new file mode 100644 index 0000000000..da65482095 --- /dev/null +++ b/calico-cloud_versioned_docs/version-22-2/tutorials/calico-cloud-features/projects.mdx @@ -0,0 +1,59 @@ +--- +description: About projects +--- + +import Screenshot from '/src/___new___/components/Screenshot'; + + +# Projects + +You can use projects to organize your managed clusters into logical groupings. + + + +## About projects + +In $[prodname], a *project* is a logical grouping of one or more managed clusters. +You can use projects to organize your managed clusters in ways that are useful for your organization. +For example, you can use projects to segregate clusters by product teams, or by geo location. + +When you view observability tools in Calico Cloud, you see only what is available for the current project. + +All Calico Cloud organizations start with a single default project. +You can have up to three projects at a given time. + +## Create a project + +**Prerequisites** + +* You have Admin or Owner privileges. + +**Procedure** + +1. From any page in the web console, click the **Project** menu and then click **Manage Projects**. +1. On the **Projects** page, click **Add Project**. +1. Enter a name and description for the project, and then click the **Add Project** button. + + Provisioning the new project takes a few minutes. + When provisioning is complete, you can begin connecting clusters. + +## Connect a cluster to a project + +* To connect a cluster to a specific project, make sure you have selected the project you want as you follow the procedure to [connect your cluster to Calico Cloud](../../get-started/install-cluster.mdx). + +## Move a managed cluster to another project + +You can move a managed cluster to another project by removing it from the original project and connecting it to the new project. + +:::warning +Log data held by Calico Cloud will be deleted when you remove your cluster from the original project. +When you reconnect your cluster to Calico Cloud as part of the new project, flow logs will start to be collected again. +You will not be able to restore access to the old logs. + +If you need to retain logs, contact [our support team](https://tigeraio.my.site.com/community/s/login/). +::: + +1. To remove your cluster from Calico Cloud, find your cluster on the **Managed Clusters** page, and then click **Actions > Delete**. + After a moment, the cluster is removed from the list. +1. Move to the new project by clicking the **Projects** menu and selecting your project. +1. To reconnect your cluster, follow the guide to [connect your cluster to Calico Cloud](../../get-started/install-cluster.mdx). diff --git a/calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx b/calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx index a0c35e0f73..59aa5c69b0 100644 --- a/calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx +++ b/calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx @@ -18,6 +18,7 @@ But in some cases these global roles can be too broad. By creating and assigning custom roles, you can be much more discriminating about what permissions you give users. For example, you could create a role that allows the user to modify network policy for a particular tier and namespace and gives view access to all other network policies. +Or you can add permissions for a user to view dashboards that show data from only one namespace in a cluster. Permissions are assigned on a cluster-by-cluster basis. ## Required permissions for common $[prodname] features @@ -28,7 +29,7 @@ Certain permissions are required for a user to access common $[prodname] feature | --| -- | -- | | Alerts | • **View Alerts**
and
•**View All Logs** | | | Compliance reports | • **View Compliance Reports** | | -| Dashboard | • **View All Logs**
and
• **View Global Network Sets** or **View Network Sets**
and (optional)
• **View Compliance Reports** | These permissions are required for the dashboard to fully populate. All users are granted limited dashboard metrics by having access to a cluster. | +| Dashboard | • **View All Logs**
and
• **View Global Network Sets** or **View Network Sets**
and (optional)
• **View Compliance Reports** | These permissions are required for the dashboard to fully populate. All users are granted limited dashboard metrics by having access to a cluster. Users with **View Network Sets** have access to dashboards that show data only from namespaces that they have been explicitly given access to. | | Network policies | • **View** or **Modify Policies**
or
• **View** or **Modify Global Policies**
and (optional)
• **View Audit Logs** or **View All Logs** | The **Policies** permissions apply to one or more namespaces. The **Global Policies** permissions apply to the whole cluster. These permissions are also scoped by [policy tier](../network-policy/policy-tiers/tiered-policy.mdx).

The optional **View Audit Logs** or **View All Logs** let users view the change history on the policies. | | Service graph | • **View All Logs**
and
• **View** or **Modify Network Sets**
and (optional)
• **View** or **Modify Packet Captures** | Network sets can be restricted to a namespace or set to all namespaces to see all flows. | | Threat feeds | • **View** or **Modify Threat Feeds** | | diff --git a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json index 4b236f7ef3..d7c2a5f994 100644 --- a/calico-cloud_versioned_sidebars/version-22-2-sidebars.json +++ b/calico-cloud_versioned_sidebars/version-22-2-sidebars.json @@ -78,7 +78,8 @@ "items": [ "tutorials/calico-cloud-features/tour", "tutorials/calico-cloud-features/service-graph", - "tutorials/calico-cloud-features/networksets" + "tutorials/calico-cloud-features/networksets", + "tutorials/calico-cloud-features/projects" ] }, { diff --git a/sidebars-calico-cloud.js b/sidebars-calico-cloud.js index 72787ed3d9..eeb0e0105f 100644 --- a/sidebars-calico-cloud.js +++ b/sidebars-calico-cloud.js @@ -62,6 +62,7 @@ module.exports = { 'tutorials/calico-cloud-features/tour', 'tutorials/calico-cloud-features/service-graph', 'tutorials/calico-cloud-features/networksets', + 'tutorials/calico-cloud-features/projects', ], }, { diff --git a/static/img/calico-cloud/calico-cloud-projects.png b/static/img/calico-cloud/calico-cloud-projects.png new file mode 100644 index 0000000000..27f25132a1 Binary files /dev/null and b/static/img/calico-cloud/calico-cloud-projects.png differ