Add pull-ingress2gateway-e2e

[johananl]

This PR adds an e2e job for ingress2gateway.

I've set always_run: false and skip_report: true for now until we have confidence in the job.

[k8s-ci-robot]

Hi @johananl. 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.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: johananl
Once this PR has been reviewed and has the lgtm label, please assign robscott for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• config/jobs/kubernetes-sigs/ingress2gateway/OWNERS

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

[johananl]

Depends on merging kubernetes-sigs/ingress2gateway#294. I'm not sure if we can test the Prow job against an unmerged PR.

/hold

[johananl]

/unhold

[johananl]

I wonder how much memory we need for this kind of job.

[Stevenjin8]

depends on how much parallelism we give it.

[Stevenjin8]

/ok-to-test

[k8s-ci-robot]

@Stevenjin8: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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.