Set CAPV e2e-full test timeout to 3h

[sbueringer]

We recently set the ginkgo timeout in CAPV to 3h. We also have to increase the job timeout accordingly (default is 2h)

xref: kubernetes-sigs/cluster-api-provider-vsphere#2567

Signed-off-by: Stefan Büringer [email protected]

[sbueringer]

/assign @chrischdi @fabriziopandini

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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-sigs/cluster-api-provider-vsphere/OWNERS [sbueringer]

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

[randomvariable]

/lgtm

[k8s-ci-robot]

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

• key cluster-api-provider-vsphere-periodics-main.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-main.yaml
• key cluster-api-provider-vsphere-presubmits-main.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-main.yaml

In response to this:

We recently set the ginkgo timeout in CAPV to 3h. We also have to increase the job timeout accordingly (default is 2h)

xref: kubernetes-sigs/cluster-api-provider-vsphere#2567

Signed-off-by: Stefan Büringer [email protected]

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.