Elliott Baron

Hi @petr-postulka, sorry for the late response. I can't say for sure if we can prioritize this for 2.3, but I'll ensure we discuss it when planning our tasks for...

Hi all, we did discuss this feature yesterday during our planning meeting for 2.3. We decided to prioritize work on multi-namespace support https://github.com/cryostatio/cryostat/issues/760, which will require substantial changes both in...

The Kubebuilder book has some good examples of testing controllers with envtest: https://book.kubebuilder.io/cronjob-tutorial/writing-tests.html

Something like a big YAML file with all the resources in one? Then you can just `kubectl/oc apply -f big.yaml`? This is what cert-manager does, and how we install it...

It might be a good idea to check for the certificate/secret objects and delete them if cert-manager is disabled.

Hi Simon, thanks for creating this PR. In this example, should the links to go in the opposite direction? The front-end will call the Space API first, followed by the...

@stooke I agree with making the authorization information available only on request. For example, if we want the space API to return authorized URLs/methods for the deployments API, this will...

It looks like #2218 deals with golden files (expected test output), but not go-vcr cassettes (mock HTTP responses for tests). The `/oapi/v1/selfsubjectrulesreviews` API used in #2207 returns a lot of...

@alexeykazakov My reasoning was, if we add some code that requires an additional permission (e.g. delete imagestream), we will have to be careful to restore that part of the go-vcr...

Hi, any update on getting this fixed? Our workaround of removing the v1beta1 CRD from alm-examples is generating the following warning with each build/test: `Warning: Value operator.cryostat.io/v1beta1, Kind=Cryostat: provided API...