Elliott Baron

I just meant something simpler than that. Just a `--openshift` flag that overrides the routes detection, so this function always returns true: https://github.com/cryostatio/cryostat-operator/blob/d7b0379122b9129a76b0c25ffa29923fe4ca433a/internal/main.go#L212-L214

> Ahh thanks I guess I was wondering what if `--openshift false`, that means no openshift or auto discovery? Not sure if there is a way with `flag.Bool` without providing...

Thanks @tthvo!

The OAuth proxy lets us use a custom OAuthClient, but I'm not sure how useful this would be since it limits the permission check to one in the `openshift-delegate-urls` option....

For now, I think it's enough to allow users to provide a secret through the Cryostat CRD containing the credentials in the format expected by Cryostat's BasicAuthManager. From the [Cryostat...

Hey @jaadbarg! This is the issue I had in mind.

Here's how the API could look: ```go // CryostatSpec defines the desired state of Cryostat. type CryostatSpec struct { // ... // Options to configure how Cryostat authenticates users. //...

I think this is still outstanding, it was done in the Helm Chart but not in the operator.

Hi @mcombi, is a Limit Range defined for this namespace that is setting the CPU limit?

Thanks @mcombi, so if I'm reading correctly, the containers all receive a default limit of `500m`, but this can be increased. Perhaps it's worthwhile for our operator to query Limit...