fix registry prefix in push-manifest

[lizhuqi]

What type of PR is this?
/kind bug

What this PR does / why we need it:
registry_fix shall be empty for non dockerhub registries. Currently it returns docker.io for some registry like gcr.io/xyz

Special notes for your reviewer:

Release note:

none

[k8s-ci-robot]

Hi @lizhuqi. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coveralls]

Pull Request Test Coverage Report for Build 904493148

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 86.805%

---

Totals
Change from base Build 902364184:	0.0%
Covered Lines:	796
Relevant Lines:	917

---

💛 - Coveralls

[andyzhangx]

/ok-to-test

[lizhuqi]

/test pull-csi-driver-smb-e2e-gce

[andyzhangx]

/retest

[lizhuqi]

/retest

[lizhuqi]

/test pull-csi-driver-smb-e2e-windows

[lizhuqi]

/retest pull-csi-driver-smb-e2e-gce

[k8s-ci-robot]

@lizhuqi: The /retest command does not accept any targets.
The following commands are available to trigger jobs:

• /test pull-csi-driver-smb-verify
• /test pull-csi-driver-smb-unit
• /test pull-csi-driver-smb-sanity
• /test pull-csi-driver-smb-integration
• /test pull-csi-driver-smb-windows-build
• /test pull-csi-driver-smb-e2e
• /test pull-csi-driver-smb-e2e-vmss
• /test pull-csi-driver-smb-e2e-windows
• /test pull-csi-driver-smb-external-e2e
• /test pull-csi-driver-smb-e2e-gce

Use /test all to run the following jobs:

• pull-csi-driver-smb-verify
• pull-csi-driver-smb-unit
• pull-csi-driver-smb-sanity
• pull-csi-driver-smb-windows-build
• pull-csi-driver-smb-e2e
• pull-csi-driver-smb-e2e-vmss
• pull-csi-driver-smb-e2e-windows
• pull-csi-driver-smb-external-e2e

In response to this:

/retest pull-csi-driver-smb-e2e-gce

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.

[lizhuqi]

/test pull-csi-driver-smb-e2e-gce

[k8s-ci-robot]

@lizhuqi: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-csi-driver-smb-e2e-gce	84f6f54	link	/test pull-csi-driver-smb-e2e-gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[lizhuqi]

@andyzhangx Hi Andy, can you approve this PR? I will fix the test failure separately. Thanks!

[andyzhangx]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, lizhuqi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment