Elliott Baron

Thanks @tthvo! I will keep this epic open and add any such changes to it.

Yeah I think we're done with API changes for 3.0 at this point

There's a couple of options I've found for this sort of thing. 1. Reloader operator (https://github.com/stakater/Reloader). Probably easiest to implement, but adds a dependency on an additional operator that watches...

This should work for both the certificates managed issued by cert-manager, and also any secrets provided by the user in `ContainerJFR.Spec.TrustedCertSecrets`.

Some relevant Kubebuilder documentation: https://book.kubebuilder.io/reference/watching-resources/externally-managed.html

We will need to be careful about `CRYOSTAT_SSL_PROXIED` and distinguishing between HTTP/HTTPS. See: https://github.com/cryostatio/cryostat-helm/pull/36

Hi Florian, do you have any options in particular that you'd like to be able to set? Some of these variables need to be controlled by the operator. For example,...

For now, when running on OpenShift the operator will use the OpenShift authentication mechanism, which requires some additional setup and permissions on the operator's part. In Kubernetes, the operator uses...

Are you using OpenShift or Kubernetes? The operator currently works either using Routes on OpenShift or Ingress on Kubernetes. For the latter, there's some [manual setup](https://github.com/cryostatio/cryostat-operator/blob/main/docs/config.md#network-options) that must be done...

I don't expect that configuration to work on Kubernetes without setting the Ingress configs in the [CR](https://github.com/cryostatio/cryostat-operator/blob/main/docs/config.md#network-options). The empty login screen is somewhat unexpected though, would you be able to...