Can we cherry-pick #1339 to release-0.7

[RainbowMango]

After I updated v0.7.2, I found the DATA RACE issue as described on #1337, and it has been fixed by #1339.

This issue also presents on release-0.7, can we cherry-pick and tag a new release?

cc @vincepri

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[RainbowMango]

/close
since I've updated to v0.8.3.

[k8s-ci-robot]

@RainbowMango: Closing this issue.

In response to this:

/close
since I've updated to v0.8.3.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.