The Red Hat build of Cryostat 2.3 introduces an agent as well as multi-namespace support. This new functionality allows Cryostat to monitor more complex cluster configurations.

This article lists some best practices when creating Cryostat instances in these cluster configurations.

Use cases:

Using Cryostat to monitor applications deployed in a single namespace

If one or more applications are deployed in a single namespace, the recommended configuration is to create a Cryostat instance in the same namespace.

Example:

• Tenant A has applications A, B, C deployed in Namespace A.

Setting up the Cryostat instance:

• Create Cryostat instance A in Namespace A.

Using Cryostat to monitor applications deployed in multiple namespaces in a multi-tenant cluster

A single tenant within a cluster is defined by the boundaries of its namespaces, all the applications deployed within those namespaces, and all the users who have access to those applications and namespaces.

A multi-tenant cluster contains multiple single tenants. In this scenario, each single tenant should have its own Cryostat instance created in one of the tenant’s own namespaces within that cluster.

This ensures that the data collected by the Cryostat instance is available to all users belonging to that single tenant.

Recommended configuration steps:

1. Create a Cryostat instance in its own namespace.

2. In the Target Namespaces option, specify all the namespaces the Cryostat instance should be able to connect and collect data.

Example:

• Tenant A has applications A, B deployed in Namespaces A, B respectively.
• Tenant C has an application C deployed in Namespace C.

Setting up the Cryostat instance:

• Create Cryostat instance AB in Namespace cryostat-AB with target Namespaces A, B.
• Create Cryostat instance C in Namespace cryostat-C with target Namespace C.