Hi folks, is there a simple way in the helm chart to disable the grpc ingress but leave the http ingress up? It looks like

separateGrpcIngress: false

will just consolidate them into one ingress rather than selectively disabling it (for context we want to take a downtime window to run a db/bucket migration and want to block new run submissions but leave the http ingress up so we can view flyteconsole)

or maybe just disabling ingress altogether and just port-forward the

flyteconsole

service?

We just tried this, unfortunately it looks like a lot of the actual routing is handled in the ingress setup so the console itself is somewhat bricked if you directly port-forward to this