Tim Krause

I can replicate this behaviour on Kubernetes 1.25 even without his custom values. Setting both: ```yaml podSecurityContext: enabled: false containerSecurityContext: enabled: false ``` Allows the pod to start normally, but...

@dgomezleon Any Progress on this? The Helm chart does not work with its default settings.

@dgomezleon Well yes for openshift you explicitly disable the offending parameters see common/_compatibility.yaml ```yaml {{- define "common.compatibility.renderSecurityContext" -}} {{- $adaptedContext := .secContext -}} {{- if (((.context.Values.global).compatibility).openshift) -}} {{- if or...

For the next guy on how to enable metrics the mean time with the networkPolicy enabled: ``` extraContainerPorts: - name: metrics containerPort: 9000 protocol: TCP extraEnvVars: - name: KC_METRICS_ENABLED value:...

@nix-power then you are probably running a older keycloak version, starting with 24 it is not served on the standart web server anymore, but instead on the management port (hence...

Still broken with latest (`70.7.0`)

Still relevant

As a "workaround": You can deploy the newer versions, but you will have to either live with the broken metrics for 30d Or you can use the [prometheus admin api](https://prometheus.io/docs/prometheus/latest/querying/api/#delete-series)...