Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi all, we have a flyte-core deployment running on GKE since this winter, version 1.2.0. Been trying to upgrade us towards 1.8.0, but the helm_release terraform block isn’t completing due to flyteconsole’s health check. We have load-balancers with ingress class “gce-internal” at the moment, and I think it is the load balancer’s health check that is failing. Has anyone had any similar problems upgrading in the past six months?

Eventually got it to work - changed the liveliness probe to ping /console, but don’t think this made any difference. But should be good for now.

I also encountered this problem recently, as a temporary workaround I created a `BackendConfig` CRD (https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-configuration#configuring_ingress_features_through_backendconfig_parameters) with a custom healthcheck specification:
```
apiVersion: cloud.google.com/v1
kind: BackendConfig
metadata:
  name: "flyte-flyteconsole"
spec:
  healthCheck:
    requestPath: /console/healthz
    port: 80
```