don't use custom projects for sig-network jobs

[aojea]

After moving to the community projects, jobs started to fail because the custom projects does not exist there https://github.com/kubernetes/test-infra/pull/30761/files

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea

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/sig-network/OWNERS [aojea]

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

[cadmuxe]

/lgtm

[bowei]

Did we check to make sure these don't have larger quotas?

[aojea]

the one with large quota was ci-ingress-gce-e2e-scale IIRC

We are in a try and see mode, but we can always go back

[k8s-ci-robot]

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

• key ingress-gce-e2e.yaml using file config/jobs/kubernetes/sig-network/ingress-gce-e2e.yaml
• key sig-network-misc.yaml using file config/jobs/kubernetes/sig-network/sig-network-misc.yaml

In response to this:

After moving to the community projects, jobs started to fail because the custom projects does not exist there https://github.com/kubernetes/test-infra/pull/30761/files

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.

[ameukam]

Ref: kubernetes/k8s.io#1093