kubernetes-csi: test csi-release-tools against csi-driver-host-path

[pohly]

Only csi-driver-host-path uses the csi-sanity support in
prow.sh. Because it wasn't tested, a regression slipped through pull
testing (kubernetes-csi/csi-release-tools#148 (comment)).

[xing-yang]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pohly, xing-yang

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:

• config/jobs/kubernetes-csi/OWNERS [xing-yang]

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

[pohly]

/assign @msau42

For approval.

[pohly]

Looks like I was racing with the bot... the PR is approved. I only saw the LGTM tag.

[k8s-ci-robot]

@pohly: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key csi-release-tools-config.yaml using file config/jobs/kubernetes-csi/csi-release-tools/csi-release-tools-config.yaml

In response to this:

Only csi-driver-host-path uses the csi-sanity support in
prow.sh. Because it wasn't tested, a regression slipped through pull
testing (kubernetes-csi/csi-release-tools#148 (comment)).

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.