Hi, I haven't found it in the docs... When deploying oathkeeper using helm it get stuck while doing the readiness check.

time=2023-06-23T11:59:12Z level=error msg=An error occurred while handling a request audience=application error=map[message:The requested resource could not be found] http_request=map[headers:map[accept:*/* connection:close user-agent:kube-probe/1.26] host:127.0.0.1 method:GET path:/health/ready query:<nil> remote:10.0.7.121:50646 scheme:http] http_response=map[status_code:503] service_name=ORY Oathkeeper service_version=v0.40.3

and in k8s it looks like:

NAME                                                 READY   STATUS    RESTARTS      AGE

auth-oathkeeper-794445566d-9l9r8                     0/1     Running   3 (27s ago)   3m30s

auth-oathkeeper-oathkeeper-maester-d96c4f46b-mlf89   1/1     Running   0             3m30s

Do I miss something in the default helm values.yaml? Or why is he sending a 503? After a while:

NAME                                                 READY   STATUS             RESTARTS      AGE

auth-oathkeeper-794445566d-9l9r8                     0/1     CrashLoopBackOff   5 (45s ago)   6m48s

auth-oathkeeper-oathkeeper-maester-d96c4f46b-mlf89   1/1     Running            0             6m48s

Did you include some access rules? If the oathkeeper does not get any access rules then the probes will fail.

Ah, thanks, I haven't jet. But I'll give it a try. Thanks