Oathkeeper fails to start if secret is disabled about k8s

[Demonsthere]

Hello there!
I think this might rather be a documentation issue. We enforce that a secret will be present, whether created by the chart or by the user.
The logic used by all of the charts is as follows:

secret:
  # -- switch to false to prevent creating the secret
  enabled: true
  # -- Provide custom name of existing secret, or custom name of secret to be created
  nameOverride: ""

default option - the chart creates a secret with default name

secret:
  # -- switch to false to prevent creating the secret
  enabled: true
  # -- Provide custom name of existing secret, or custom name of secret to be created
  nameOverride: "my-secret"

custom name - the chart creates a secret with specified name

secret:
  # -- switch to false to prevent creating the secret
  enabled: false
  # -- Provide custom name of existing secret, or custom name of secret to be created
  nameOverride: ""

custom secret - we expect a secret with the default name will be present and can be used

secret:
  # -- switch to false to prevent creating the secret
  enabled: false
  # -- Provide custom name of existing secret, or custom name of secret to be created
  nameOverride: "my-secret"

custom name and secret - the chart expects that a secret with the custom name will be present and can be used

[IxDay]

Indeed, I will close this as a won't fix