Cryostat 3.0 Release
Azores, Andrew
Hello everyone,
We are pleased to announce the release of Cryostat 3.0!
What’s new in 3.0?
Quarkus: the main Cryostat container has been reimplemented using Quarkus, moving from the previous implementation of Eclipse Vert.x. This is to take advantage of the Quarkus’ strengths and features so that Cryostat can provide higher performance access to your JDK Flight recorder data.
Postgres database by default: A lightly customized postgres database is now deployed instead of a H2 file-based database. This is used for storing Automated Rules definitions, discovered targets and discovery plugins.
S3-compatible object storage: An S3-compatible storage provider has been integrated for binary large objects such as Archived Flight Recordings and Custom Event Templates.
Reverse proxy architecture: Cryostat operator and helm chart deployments include an oauth2 proxy. This proxy provides unified access control and handles user sessions for the Cryostat Web UI as well as the Grafana dashboards.
Operator changes:
Cluster-wide installation only: Cluster-wide installation is the preferred mode for the Operator Lifecycle Manager and per-namespace installations are a deprecated feature, which our Operator has now dropped.
ClusterCryostat removal: 1beta1/Cryostat and v1beta1/ClusterCryostat are now unified in the v1beta2/Cryostat custom resource, simplifying the configuration of Cryostat instances.
More details on these feature highlights can be found in our blog.
Where can I get the latest version of Cryostat?
You can install Cryostat using our Kubernetes operator on OperatorHub.io or via a Helm Chart.
Upstream guide
Blogs
We’re always adding new blogs! Stay up to date with us for feature spotlights and more.
Feedback
Our team is very excited to present this update to Cryostat and we look forward to your feedback. Please reach out to the Cryostat group at cryostat-d...@googlegroups.com or create a discussion in GitHub with any questions or comments.