etcd: always run fuzzing-v3rpc presubmit job

[ivanvc]

The job works as expected: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/directory/pull-etcd-fuzzing-v3rpc/1887584670061694976

I also intentionally triggered a failure to verify that it generates the expected artifacts:

• https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/directory/pull-etcd-fuzzing-v3rpc/1887664356443820032
• https://gcsweb.k8s.io/gcs/kubernetes-ci-logs/pr-logs/pull/etcd-io_etcd/19357/pull-etcd-fuzzing-v3rpc/1887664356443820032/artifacts/

/cc @ahrtr

[ahrtr]

/lgtm
/approve

Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, ivanvc

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/etcd/OWNERS [ahrtr]

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

[k8s-ci-robot]

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

• key etcd-presubmits.yaml using file config/jobs/etcd/etcd-presubmits.yaml

In response to this:

The job works as expected: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/directory/pull-etcd-fuzzing-v3rpc/1887584670061694976

I also intentionally triggered a failure to verify that it generates the expected artifacts:

• https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/directory/pull-etcd-fuzzing-v3rpc/1887664356443820032
• https://gcsweb.k8s.io/gcs/kubernetes-ci-logs/pr-logs/pull/etcd-io_etcd/19357/pull-etcd-fuzzing-v3rpc/1887664356443820032/artifacts/

/cc @ahrtr

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.