I’m trying to deploy SATOSA on Kubernetes, and I want to add a liveness probe to my deployment.

I noticed that SATOSA only becomes truly available after it receives data from the identity provider. Therefore, the following Kubernetes liveness probe:

livenessProbe:
  httpGet:
    path: /liveness
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10

is not sufficient.

If SATOSA takes a long time to receive data from the identity provider, the server does not start until it has received that data, and the port is therefore not accessible until the server is fully up.

Is it possible to add a /liveness route that returns "ok" or something else only after data has been received from the identity provider?

Thanks