Andrew Azores

Possibly. I don't really know that we have any downstream infra that we are able/approved to use that way.

Related: https://github.com/cryostatio/cryostat/issues/808

The main Cryostat logs as well as the -web logs from the browser developer console, please!

In that case I think the best current approach is something similar to what @heubeck was describing before. Deploy Cryostat without authz enabled, but place it behind a proxy that...

I'm seeing the same problem as here: https://bugzilla.redhat.com/show_bug.cgi?id=1934177 My CRC environment does use 4.7, so I think it is the exact same failure scenario. I have tried many permutations of...

This may be better suited for a separate bug, but `DEPLOY_NAMESPACE=foo make undeploy` will also attempt to destroy the `foo` namespace. That's probably *not good* if a user is trying...

I addressed the Namespace creation/deletion in my operator-sdk 1.5.0 PR (linked above). If a user tries to manually deploy to a namespace that doesn't exist then the deployment will simply...

- Updating `kube-rbac-proxy` to v0.8.0 and setting `runAsNonRoot: true` for its container: ``` --- a/config/default/manager_auth_proxy_patch.yaml +++ b/config/default/manager_auth_proxy_patch.yaml @@ -10,7 +10,7 @@ spec: spec: containers: - name: kube-rbac-proxy - image: gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0...

- Updating `kube-rbac-proxy` to v0.8.0 and setting `runAsNonRoot: true` for the deployment: ``` --- a/config/default/manager_auth_proxy_patch.yaml +++ b/config/default/manager_auth_proxy_patch.yaml @@ -8,9 +8,11 @@ metadata: spec: template: spec: + securityContext: + runAsNonRoot: true...

- The current situation as-is upstream, with `kube-rbac-proxy` v0.5.0 and no other modifications to the deployment/containers fails in the `default` namespace with the following reason: `Error: container has runAsNonRoot and...