Andrew Azores

Deprioritized for this release. https://github.com/cryostatio/cryostat-grafana-dashboard/pull/68 will get us back onto a non-deprecated path at least, which is enough to continue on with the same jfr-datasource/grafana-dashboard setup. This issue is more...

Yea, something like that - it was initially @jiekang's idea here, but I think the thought is just to have something as close to a "one-click install" as possible directly...

Worth noting that this still hasn't been implemented because the Cryostat use-case only deploys this as a container within the Cryostat Pod, and the container's ports are not exposed by...

Related: https://github.com/cryostatio/cryostat-core/issues/95 https://github.com/cryostatio/cryostat/issues/666

We do have the `app.kubernetes.io/name` label which is applied to the ContainerJFR Deployment. Are these labels also on the Jaeger Deployment? Are there any other resources or component associated with...

Where is this "ResourceKind instance" from? I'm not sure how I can tell which things are linked together in the way you're talking about.

Ah, okay I see what you mean. I'm not sure how the console is populating that list that you're seeing. It might be coming from the OperatorHub ClusterServiceVersion, but this...

When you delete the ContainerJFR resource instance, the Operator is what sees this and cleans up the associated Deployment/ReplicaSet. If the ContainerJFR itself owned these resources then it would... somehow...

@dependabot rebase