September 18, 2023

Cryostat 2.3.1 is Released!

---

Table of Contents

• Table of Contents
• What’s Fixed in 2.3.1?
• Where can I get the latest version of Cryostat?
• Feedback

---

Hello everyone,

We are pleased to announce the release of Cryostat 2.3.1! This is a minor bugfix release addressing some issues uncovered with the previous 2.3.0 feature release.

What’s Fixed in 2.3.1?

1. routine maintenance: dependency version updates and container base image version updates
2. “Log Out” from the Cryostat Web UI was previously broken on OCP 4.12+:
   • cryostat#1489
   • cryostat-web#1059
   • cryostat-operator#599
3. Deleting an OpenShift Namespace containing a Cryostat installation could hang:
   • cryostat-operator#584
   • cryostat-operator#593
4. Cryostat Web dashboard configuration could become broken and fail to reload cards:
   • cryostat-web#1024
5. Cryostat could fail to discover target applications if the application takes some time to become ready and JMX-connectable:
   • cryostat#1577
   • cryostat#1593
6. Cryostat could fail to start Flight Recordings on some target application JVMs:
   • cryostat#1516
   • cryostat-core#228
   • cryostat#1525
7. Cryostat would fail to connect to GraalVM native images:
   • cryostat-core#217
   • cryostat-core#222
   • cryostat-core#228
   • cryostat#1525
8. Cryostat Agent would create Stored Credentials with a Match Expression that could result in the credentials being erroneously used for JMX connections to the attached host JVM:
   • cryostat-agent#133
   • cryostat-agent#134
   • cryostat-agent#154
   • cryostat-agent#156
9. Cryostat Agent would publish itself as a Discovery Node with the wrong JMX port number in its annotations:
   • cryostat-agent#153
   • cryostat-agent#157
10. Cryostat would incorrectly fail validation of certain JMC Agent probe templates, and after validation failures would reject further template creation requests:
    • cryostat-core#238
    • cryostat-core#239
    • cryostat-core#241
    • cryostat-core#243
11. Cryostat would refuse Automated Rules creation requests using multipart/form-data:
    • cryostat#1490
    • cryostat#1499
12. Cryostat Helm chart instances would use a hardcoded credentials secret name, which would conflict if multiple instances were installed to the same namespace:
    • cryostat-helm#62
    • cryostat-helm#65
13. Cryostat environment variable CRYOSTAT_DISABLE_SSL was handled inconsistently and would not always disable server SSL as expected:
    • cryostat#1507
    • cryostat#1570
14. Cryostat environment variable CRYOSTAT_DISABLE_BUILTIN_DISCOVERY would also disable Custom Targets, and could break server startup in some scenarios:
    • cryostat#1505
    • cryostat#1506
15. Cryostat built-in discovery mechanisms could block server startup if they failed to activate:
    • cryostat#1546
    • cryostat#1549
16. Some minor graphical fixups in Cryostat Web:
    • cryostat-web#1019
    • cryostat-web#1041
    • cryostat-web#1049

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 . As always, you can also run Cryostat in other environments with a little more manual setup.

If this is your first time installing Cryostat on Kubernetes, you can Get Started right here on this website.

If you had previously installed Cryostat Operator 2.3.0 with OLM, then you may have already been upgraded to 2.3.1, or else you should be able to approve and install the upgrade.

Feedback

Please reach out to the Cryostat mailing list or GitHub Discussion with any questions or comments.