oathkeeper /health/ready not found

[ghost]

I feel like I'm missing something obvious here, but after deploying what I figured was a rather tame sample config of oathkeeper, I can't seem to get the pods in kubernetes to become ready.

The specific error is

time=2023-07-06T04:13:41Z 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:*/* connection:close
user-agent:kube-probe/1.27+] host:127.0.0.1 method:GET path:/health/ready query:<nil> remote:10.11.242.173:43818
scheme:http] http_response=map[status_code:503] service_name=ORY Oathkeeper service_version=v0.40.3

I'm using version 0.33.4 of the oathkeeper helm chart.

the values.yaml I'm using is below

serve:
  proxy:
    port: 4455 # run the proxy at port 4455
  api:
    port: 4456 # run the api at port 4456

deployment:
  extraEnv:
    - name: LOG_LEVEL
      value: debug

errors:
  fallback:
    - json
  handlers:
    json:
      enabled: true
      config:
        verbose: true
    redirect:
      enabled: true
      config:
        to: https://www.ory.sh/docs

mutators:
  header:
    enabled: true
    config:
      headers:
        X-User: "{{ print .Subject }}"
  noop:
    enabled: true

authorizers:
  allow:
    enabled: true
  deny:
    enabled: true

authenticators:
  anonymous:
    enabled: true
    config:
      subject: guest

anyone have any ideas? I don't need to override the health checks in the base helm chart, do I?

[vinckr]

Hello @teedrupp
It's not clear what could be causing the issue you're experiencing - my guess would be it is related to your k8s setup.

However, from the top of my head here are a few things you could check:

• Configuration: Ensure that your values.yaml file is correctly formatted and all the necessary fields are filled out. The configuration you provided seems to be fine.
• Version Compatibility: You mentioned that you're using version 0.33.4 of the Ory Oathkeeper Helm chart. Ensure that this version is compatible with the version of Ory Oathkeeper you're using.
• Kubernetes Secrets: In a production environment, it's recommended to provide the JSON Web Keys as a Kubernetes Secret mounted in a directory. If you're running in a production environment, this could be something to consider.

[xshadowlegendx]

I feel like I'm missing something obvious here, but after deploying what I figured was a rather tame sample config of oathkeeper, I can't seem to get the pods in kubernetes to become ready.

The specific error is

time=2023-07-06T04:13:41Z 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:*/* connection:close
user-agent:kube-probe/1.27+] host:127.0.0.1 method:GET path:/health/ready query:<nil> remote:10.11.242.173:43818
scheme:http] http_response=map[status_code:503] service_name=ORY Oathkeeper service_version=v0.40.3

I'm using version 0.33.4 of the oathkeeper helm chart.

the values.yaml I'm using is below

serve:
  proxy:
    port: 4455 # run the proxy at port 4455
  api:
    port: 4456 # run the api at port 4456

deployment:
  extraEnv:
    - name: LOG_LEVEL
      value: debug

errors:
  fallback:
    - json
  handlers:
    json:
      enabled: true
      config:
        verbose: true
    redirect:
      enabled: true
      config:
        to: https://www.ory.sh/docs

mutators:
  header:
    enabled: true
    config:
      headers:
        X-User: "{{ print .Subject }}"
  noop:
    enabled: true

authorizers:
  allow:
    enabled: true
  deny:
    enabled: true

authenticators:
  anonymous:
    enabled: true
    config:
      subject: guest

anyone have any ideas? I don't need to override the health checks in the base helm chart, do I?

I was having this issue on fresh install, then I tried installing the demo mode and it works, this gives me hint that my config is having some error, then I tried looking at the logs and saw error saying "authorizer.handler" can not be empty, and I went and fix that and it is working fine now, so I think maybe check oathkeeper's pod logs and find the error