Elliott Baron

> Our 2.1.0 release has `06a7974` listed for version as reported by Cryostat. I think there are a couple of problems here: > > 1. The CI build does not...

That sounds about right, other than we need to request the `user:info` scope. I think all users by default are able to query `users/~`, but I'm not sure if this...

Hi @mgohashi, in Cryostat 2.0 the health check is indeed using the Route URL. With the upcoming 2.1 release, this will be done using a host alias to the loopback...

> Installation with kubeclt https://cryostat.io/get-started/ doesnt work at it has wrong URL in `k apply` command - and it's for 1.0.0 Hi @agilob, is there a problem with: `kubectl apply...

> @ebaron oh interesting, didn't know it. This command doesn't work in zsh, but works in bash. > > To make it work on zsh: `kubectl apply -d 'github.com/cryostatio/cryostat-operator//config/default?ref=v1.0.0'` url...

I feel like this could be risky from a security perspective. This may be better suited for the operator, or have the user manually edit the Cryostat deployment. For example,...

I feel like the `pod/exec` subresource captures what we're doing here with recordings. The `create pod/exec` permission allows you to run arbitrary commands in the pod using `kubectl exec`.

I think the subscription is the only way to do it at the bundle level. It's probably worth increasing the limit. Judging from the log, it didn't get very far....

From https://github.com/cryostatio/cryostat-operator/pull/474#issuecomment-1279347320: > Just a question: What about the case where the user switch from custom secret to default one? The default secret will take place and still make Cryostat...

> Hey @ebaron, is there any planned for 3.0 tasks that I can help you here? Hey @tthvo, I think there may be some additional breaking changes that will follow...