Open Match doesn't work in the latest WorkloadIdentity enabled cluster

[yfei1]

We should disable the workload identity feature in our cluster and point out the incompatibility in open-match.dev until GKE team fixes this.

What happened:
gcloud beta container clusters create om-cluster --identity-namespace=$(GCP_PROJECT_ID).svc.id.goog && make install-chart && kubectl get deployment,pod -n open-match

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.extensions/om-backend         0/1     1            0           172m
deployment.extensions/om-demo            1/1     1            1           172m
deployment.extensions/om-evaluator       1/1     1            1           172m
deployment.extensions/om-frontend        0/1     1            0           172m
deployment.extensions/om-function        1/1     1            1           172m
deployment.extensions/om-mmlogic         0/1     1            0           172m
deployment.extensions/om-redis-metrics   1/1     1            1           172m
deployment.extensions/om-swaggerui       1/1     1            1           172m
deployment.extensions/om-synchronizer    0/1     1            0           172m

NAME                                   READY   STATUS    RESTARTS   AGE
pod/om-backend-59bfdc4d85-jfcl2        0/1     Running   0          172m
pod/om-demo-689f67b459-s27qn           1/1     Running   0          172m
pod/om-evaluator-74695f8d88-rplhm      1/1     Running   0          172m
pod/om-frontend-5bd5d695d5-5qjdl       0/1     Running   0          172m
pod/om-function-7db58fddc7-vn9dj       1/1     Running   0          172m
pod/om-mmlogic-5795cf6c6f-bbq4r        0/1     Running   0          172m
pod/om-redis-master-0                  1/1     Running   0          172m
pod/om-redis-metrics-7b689d454-r5wbf   1/1     Running   0          172m
pod/om-redis-slave-0                   0/1     Running   0          172m
pod/om-redis-slave-1                   0/1     Running   0          154m
pod/om-swaggerui-577b5655b-s8dwn       1/1     Running   0          172m
pod/om-synchronizer-6748f5c8f-4cz76    0/1     Running   0          172m

For some reason, the redis-slave is not able to talk to redis master, which results in healthcheck failures of open-match-core components.

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
I was using the latest stable version of gke-1.14 cluster

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.7", GitCommit:"8fca2ec50a6133511b771a11559e24191b1aa2b4", GitTreeState:"clean", BuildDate:"2019-09-18T14:47:22Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.7-gke.17", GitCommit:"81c87c699557fed991e292cd328b2129c2f242a2", GitTreeState:"clean", BuildDate:"2019-10-21T20:05:44Z", GoVersion:"go1.12.11b4", Compiler:"gc", Platform:"linux/amd64"}

Install Method(yaml/helm)::
yaml