Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi. I am getting my feet wet with Oathkeeper but have problems running it in Kubernetes with a minimal config and empty access rules. Not sure what I am missing as the error isn't super helpful. The `/health/ready` endpoint returns a 503 *healthx.swaggerNotReadyStatus a few times before getting killed.

Full error:
```time=2023-10-11T07:52:57Z level=error msg=An error occurred while handling a request audience=application error=map[message:The requested resource could not be found stack_trace:stack trace could not be recovered from error type *healthx.swaggerNotReadyStatus] http_request=map[headers:map[accept:*/* accept-encoding:gzip connection:close user-agent:kube-probe/1.24] host:127.0.0.1 method:GET path:/health/ready query:&lt;nil&gt; remote:127.0.0.6:42323 scheme:http] http_response=map[status_code:503] service_name=ORY Oathkeeper service_version=v0.40.6```

Apparently at least one rule must be added for the health/ready check to work. `[]`  is not enough.