Etcd operator automountServiceAccountToken

Is anyone using auto-injection with Etcd clusters, as created by the etcd operator?
The etcd operator deploys a pod spec with a hard coded “automountServiceAccountToken: false”.
Is there a work around for this in 1.8?
This was/is working just fine for us in Istio 1.4.2, but it seems that istio-proxy now needs to access the token.

In these pods, the istio-proxy is spitting out this error:
2021-01-15T15:10:43.015368Z info xdsproxy connecting to upstream XDS server: istiod.fed-istio.svc:15012
2021-01-15T15:10:43.028056Z error xdsproxy failed to read token file “/var/run/secrets/kubernetes.io/serviceaccount/token”: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2021-01-15T15:10:43.028242Z error xdsproxy failed to create upstream grpc client: rpc error: code = Unauthenticated desc = transport: failed to read token file “/var/run/secrets/kubernetes.io/serviceaccount/token”: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2021-01-15T15:10:43.028255Z info xdsproxy disconnected from XDS server: istiod.fed-istio.svc:15012
2021-01-15T15:10:43.029212Z warning envoy config StreamAggregatedResources gRPC config stream closed: 16, transport: failed to read token file “/var/run/secrets/kubernetes.io/serviceaccount/token”: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2021-01-15T15:10:43.202260Z warn Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected