Chapter 5. Fixed issues Cryostat releases can include fixes for issues that were identified in earlier versions. Review the following notes for details on each issue and its resolution. Issues fixed in Cryostat 3.0.1 The following issues have been resolved in the Cryostat 3.0.1 release: Failure to create or update a Cryostat custom resource due to webhook TLS errors Before Cryostat 3.0.1, if you installed other Operators that were using webhooks in the same namespace as the Cryostat Operator, attempts to create or update Cryostat custom resources could fail. This behavior resulted in the following type of error message: This error occurred because the label selectors on the Cryostat Operator's webhook service were not specific enough and could match other operators. Cryostat 3.0.1 resolves this issue by making the label selector for the Cryostat Operator's webhook service more specific to match the Cryostat Operator pods only. Inability to upload JMC ByteCode Agent instrumentation templates Before Cryostat 3.0.1, Cryostat could not accept bytecode probe definition templates for the JDK Mission Control (JMC) ByteCode Agent integration feature. In this situation, the server received the uploaded template XML file, but the server failed to locate the validation schema and refused the request. Cryostat 3.0.1 resolves this issue by correctly relocating the template schema file, which enables the server to validate and accept uploaded XML files. Parsing failures when uploading archived recordings with labels file When uploading or re-uploading a JDK Flight Recorder (JFR) file from your workstation to the Cryostat storage, you can also select a JSON file containing metadata and label information associated with the uploaded JFR recording. Before Cryostat 3.0.1, the selected JSON file was incorrectly parsed and the label information was not applied to the JFR recording. Cryostat 3.0.1 resolves this issue by correcting the parsing procedure of the supplied metadata file, which ensures that the labels are correctly uploaded to the server and associated with the uploaded JFR recording. Topology view fails to filter target JVMs by label or annotation The Topology view of the Cryostat web console displays a graph or list view of the discovered target JVM applications for the user. The Topology view includes a drop-down menu that you can use to filter these targets based on various properties, including any OpenShift labels or annotations that might be present. Before Cryostat 3.0.1, the Cryostat server processed these labels and annotations incorrectly. In this situation, the server substituted the labels and annotations with [object Object] text, which prevented any filtering based on these attributes. From Cryostat 3.0.1 onward, the Topology view correctly displays any labels and annotations as key-value pairs that you can use to filter the list of target JVMs. Match expressions cannot use the target.agent property API endpoints such as /api/v3/discovery or /api/v3/targets list target JVM objects with various properties, including an agent property. The agent property reflects whether the target JVM uses a JMX connection or a Cryostat agent HTTP connection. Before Cryostat 3.0.1, you could not reference or select the agent property for filtering purposes in the following situations: When creating match expressions for stored credentials or automated rules When graphically filtering target JVMs in the Topology view of the Cryostat web console From Cryostat 3.0.1 onward, you can reference the agent property in match expressions. You can also select the agent property as a filter in the Topology view to show only target JVMs that use the Cryostat agent.

Commands:
Error "failed calling webhook "vcryostat.kb.io": failed to call webhook: Post "https://cryostat-operator-controller-manager-service.openshift-operators.svc:443/validate-operator-cryostat-io-v1beta2-cryostat?timeout=10s": tls: failed to verify certificate: x509: certificate is valid for infinispan-operator-controller-manager-service.openshift-operators, infinispan-operator-controller-manager-service.openshift-operators.svc, not cryostat-operator-controller-manager-service.openshift-operators.svc" for field "undefined".