CAPZ: add "e2e-full" job that includes GPU-based nodes

[mboersma]

kubernetes-sigs/cluster-api-provider-azure#1002 adds a Ginkgo e2e spec to provision and test a GPU-enabled Azure cluster, but skips that test by default. This adds a new pull-cluster-api-provider-azure-e2e-full job that can be run on demand to include the GPU-enabled test spec.

cc: @CecileRobertMichon @devigned

[k8s-ci-robot]

Hi @mboersma. Thanks for your PR.

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

[alexeldeib]

/ok-to-test

[CecileRobertMichon]

is the plan to add this once we've merged the GPU PR and verified the pull job works?

[mboersma]

Yes, or the other way around if we prefer. (Although I need to figure out why this failed first.)

The GPU job has passed Prow CI before it was added to GINKGO_SKIP, so I know it works in general.

[CecileRobertMichon]

Are you rebased off the latest main branch? Could be #19662

[mboersma]

No, I accidentally gave both jobs the same testgrid-tab-name. Fixed now.

[devigned]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: devigned, mboersma

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-azure/OWNERS [devigned]

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]

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

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

In response to this:

kubernetes-sigs/cluster-api-provider-azure#1002 adds a Ginkgo e2e spec to provision and test a GPU-enabled Azure cluster, but skips that test by default. This adds a new pull-cluster-api-provider-azure-e2e-full job that can be run on demand to include the GPU-enabled test spec.

cc: @CecileRobertMichon @devigned

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.