#3730 [Docs] The GCP deployment docs should fix/remove the instructions to use the GCP Ingress controller Issue created by fg91 Description The SSL Certificate section in the GCP deployment guide documents both the use of a GKE

ManagedCertificate

in combination with the GKE ingress controller as well as the use of cert manager with the nginx ingress controller. However, when using the GCP ingress, the

flyteadmin

backend will always be shown as unhealthy (even though it isn't) as the GKE ingress controller cannot interpret probes of type

exec.command

which flyteadmin uses and which are recommended for gRPC services. Instead, the GKE ingress would need to either get a path + port where the app returns 200 if it is healthy or it needs to be given a TCP port where it will try to open a socket. (The way the GKE ingress checks for health can be customized with a so-called backend config. (In the Flyte Slack, users have reported that they used this mechanism to fix the broken health check.) The documentation should either provide instructions for using the GKE ingress controller that work out of the box or remove references to it and instead only recommend the nginx ingress controller. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte