router-0 pod is in Init:CrashLoopBackOff

[naveenspen14]

Describe the bug
While deploying kubecf on AWS kubeadm cluster (no EKS) the pod router-0 always in CrashLoopBackOff state.

router-0 0/7 Init:CrashLoopBackOff

To Reproduce
Direct deployment of kubecf 2.7.12.

1. helm install cf-operator --namespace cf-operator --set "global.singleNamespace.name=kubecf" cf-operator.tgz
2. helm install kubecf --namespace kubecf --values values.yaml kubecf_release.tgz
3. ingress set to false.

Expected behavior
it should deploy kubecf on AWS kubernetes cluster

Environment
kubernetes version : 1.18.4
cf version 6.53.0+8e2b70a4a.2020-10-01

Additional context
no logs available for router-0 pod. As I said above, I'm deploying kubecf on AWS.

k get pods -n kubecf
NAME READY STATUS RESTARTS AGE
api-0 17/17 Running 1 4h4m
auctioneer-0 6/6 Running 1 4h4m
cc-worker-0 6/6 Running 0 4h4m
cf-apps-dns-747456bc6-s7dx5 1/1 Running 0 4h7m
coredns-quarks-866dff75df-cbhn7 1/1 Running 0 4h6m
coredns-quarks-866dff75df-kp2cb 1/1 Running 0 4h6m
credhub-0 8/8 Running 0 4h4m
database-0 2/2 Running 0 4h5m
database-seeder-d77d9a8451cb30da-k9pvr 0/2 Completed 0 4h6m
diego-api-0 9/9 Running 2 4h4m
diego-cell-0 12/12 Running 2 4h4m
diego-cell-1 12/12 Running 2 3h55m
doppler-0 6/6 Running 0 4h4m
log-api-0 9/9 Running 0 4h4m
log-cache-0 10/10 Running 0 4h4m
nats-0 7/7 Running 0 4h4m
router-0 0/7 Init:CrashLoopBackOff 51 4h4m
routing-api-0 6/6 Running 0 4h4m
scheduler-0 12/12 Running 1 4h4m
singleton-blobstore-0 8/8 Running 0 4h4m
tcp-router-0 7/7 Running 0 4h4m
uaa-0 9/9 Running 0 4h4m

[mari0theminer]

@naveenspen14 did you get it working,? I have the same issue.