expose GRPC conformance client as in interface

[snehachhabria]

What type of PR is this?
/kind test
/area conformance

What this PR does / why we need it:
The reason for this PR is explained in github issue: #3093

Which issue(s) this PR fixes:
Fixes # #3093

Does this PR introduce a user-facing change?:

Yes
Exposing grpc client interface as a option in the conformance suite

[k8s-ci-robot]

Hi @snehachhabria. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Details

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-sigs/prow repository.

[keithmattix]

LGTM

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: keithmattix, snehachhabria

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• conformance/OWNERS [keithmattix]

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

[keithmattix]

/ok-to-test

[keithmattix]

Let's try this again
/lgtm

[keithmattix]

/cherry-pick release-1.1

[snehachhabria]

If possible, could this be cherry-picked into release v1.1.0?

cc @robscott

[robscott]

We actually just hadn't created the release-1.1 branch otherwise I think that cherry pick command should have worked.

/cherry-pick release-1.1

could this be cherry-picked into release v1.1.0

We'll need to do a patch release, usually we try to accumulate a few things over a couple of weeks so we don't end up with too many patch releases, let's aim for early June?

[k8s-infra-cherrypick-robot]

@robscott: new pull request created: #3104

Details

In response to this:

We actually just hadn't created the release-1.1 branch otherwise I think that cherry pick command should have worked.

/cherry-pick release-1.1

could this be cherry-picked into release v1.1.0

We'll need to do a patch release, usually we try to accumulate a few things over a couple of weeks so we don't end up with too many patch releases, let's aim for early June?

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-sigs/prow repository.

[snehachhabria]

We actually just hadn't created the release-1.1 branch otherwise I think that cherry pick command should have worked.

/cherry-pick release-1.1

could this be cherry-picked into release v1.1.0

We'll need to do a patch release, usually we try to accumulate a few things over a couple of weeks so we don't end up with too many patch releases, let's aim for early June?

sounds good to me, I am in no hurry we can use the commit from the release branch to unblock us.

thanks a lot @robscott and @keithmattix for the quick turn around