You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I intend to deploy this into a GKE cluster and would like to use its Ingress instead of Nginx. One of the GKE ingress requirements is to have all services return a 200 at '/' or a readinessProbe on a path that returns a 200 (1), otherwise the backend will be seen as unhealthy.
For key-submission, I can set up a readinessProbe like the following:
Hi,
I intend to deploy this into a GKE cluster and would like to use its Ingress instead of Nginx. One of the GKE ingress requirements is to have all services return a 200 at '/' or a
readinessProbe
on a path that returns a 200 (1), otherwise the backend will be seen as unhealthy.For key-submission, I can set up a
readinessProbe
like the following:I can't find out a way to do for key-retrieval though.
Can you please advise if there is a recommended way to make the server work with GKE Ingress? Thanks.
The text was updated successfully, but these errors were encountered: