--follow option does not work with kubectl logs command for a pod running on ACI virtual node

[atakadams]

kubectl logs --follow <Pod-running-on-ACI-virtual-node> doesn't follow the incoming log output but only shows existing log and then exit, as same as the command without "--follow" option.

Expected behavior:
kubectl logs -f <Pod-running-on-ACI-virtual-node> command shows the latest log already stored and then continues showing new log lines without immediate exit.
(For the pod create with the template attached, latest date appears on every 10 seconds)

Actual behavior:
The command shows the latest log and exits immediately.

How to reproduce:

1. Create an AKS cluster with ACI virtual node enabled
2. Create a pod "log-test-aci" with log-test-aci.yaml in log-test-aci.zip attached.
3. Execute kubectl logs -f log-test-aci

Note:

• I've succesfully reproduced it with the AKS cluster version 1.19.11.

• Similar trial from Azure CLI to ACI container with az container logs --follow command succesfully worked with
  "follow" option showing new-arrived log lines one-by-one, which will mean that the issue is not about ACI itself but
  about virtual node specific part.

• The implementation doesn't seem to refer "Follow" option flag.
  

  azure-aci/provider/aci.go

  Line 994 in a9e1eb6

  cLogs, err := p.aciClient.GetContainerLogs(ctx, p.resourceGroup, cg.Name, containerName, opts.Tail)

[nakazonot]

Is there a plan to resolve the issue?
The problem continues in v1.4.5.