Chapter 1. Cryostat migration overview As a cluster administrator in Red Hat OpenShift, you can upgrade from Cryostat 2.4 to Cryostat 3.0. This guide covers new updates available in the Cryostat 3.0 release, deprecated and unsupported features, and any required application and Operator configuration updates to maintain consistent behavior. Before you begin the migration process , complete the following steps: Review the major Cryostat Operator changes in Cryostat 3.0 . Review the application configuration changes . Review migration recommendations . 1.1. Major Cryostat Operator changes Red Hat build of Cryostat 3.0 includes major updates to the installation mode of the Cryostat Operator as well as the types of provided APIs. Installation mode changes Red Hat build of Cryostat version Installation modes 2.4 and earlier All namespaces on the cluster (default) A specific namespace on the cluster 3.0 All namespaces on the cluster (default) In Red Hat OpenShift, the Cryostat Operator can now only be installed on a cluster-wide basis ( All namespaces on the cluster ) rather than into a subset of cluster namespaces. Cluster-wide installation is the preferred mode for the Operator Lifecycle Manager and per-namespace installations are a deprecated feature. Figure 1.1. Installation modes in Cryostat 3.0 Provided API changes Red Hat build of Cryostat version Provided APIs 2.4 and earlier ClusterCryostat Cryostat 3.0 Cryostat ClusterCryostat and Cryostat APIs have now been unified into a singular Cryostat API. You can use the Cryostat API and its optional Target Namespaces field to create one or more Cryostat instances that correspond to namespaces or groups of namespaces that contain your applications. Figure 1.2. Provided APIs available in Cryostat 3.0 1.2. Application configuration changes For applications that are deployed with the Cryostat agent, an updated 0.4.0 version of the agent is available and required for using Red Hat build of Cryostat 3.0. For information about the latest available build version of the Cryostat agent, refer to the Red Hat Maven repository . In addition to upgrading the agent, some of the agent configuration properties have changed: Agent configuration property Cryostat 2.4 value Cryostat 3.0 value Details CRYOSTAT_AGENT_BASEURI http://cryostat.mynamespace.mycluster.svc:8181 http://cryostat.mynamespace.mycluster.svc:4180 Service port has changed from 8181 to 4180. CRYOSTAT_AGENT_AUTHORIZATION Bearer Base64 token Bearer raw (plain-text) token Bearer token no longer needs to be Base64-encoded. For more information about agent configuration changes and other new features and enhancements, see the Release notes for the Red Hat build of Cryostat 3.0 . Note For applications that are using remote JMX connections, Red Hat build of Cryostat does not include any configuration changes. 1.3. Migration recommendations Before migrating, consider backing up any Cryostat data to ensure that customizations can be restored after upgrading. This data includes: Custom profile templates Custom dashboard layouts Active and archived recordings Custom automated rules If there are SSL certificates and stored credentials configurations, ensure that these are available during migration.

Commands: