Elliott Baron
Elliott Baron
Using an existing JFR file uploaded to Cryostat, we should be able to generate an automated analysis report and compare its JSON against what we expect it to be.
We should revisit adding a Scorecard test similar to `cryostat-recording` that uses built-in Kubernetes discovery instead of a custom target. We encountered some strange networking failures on the Cryostat end...
Right now the Scorecard tests only use Cryostat itself as a target, it would be nice to have them operate on sample applications as well. The sample applications used by...
Some CRD options no longer make sense for Cryostat 3.0. These include: - [x] #728 - [x] #729 - [x] #730 - [x] #732
Currently, Cryostat only authenticates users by default when run in OpenShift. We should configure password authentication when running on Kubernetes, perhaps generating credentials prior to deployment.
#166 adds a configurable PVC spec. Once created, it's not possible to edit the PVC spec without deleting and recreating it. It would be useful to respond to an editted...
In order to allow Cryostat to get a scoped token across additional namespaces, we can't use a Service Account as an OAuth client. > I've been able to track down...
It should be possible to run the scorecard tests locally, provided you're logged into a suitable Kubernetes cluster. This would give a faster turnaround time on testing changes. Something like...
Other operators may want to reuse the Insights setup we've created using APICast. The work is fairly self-contained already. We would have to fully decouple it from Cryostat and then...
Our Helm chart currently allows users to install Cryostat using only Services for networking, with some additional post-install steps required. It would be useful if the operator could also support...