Reuse workflow CI

[rikatz]

What this PR does / why we need it:

We've been repeating some parts of CI A LOT. Instead, we can reuse some workflow parts (like e2e tests) and keep it simple when we want to change something on this workflow

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	388fc74
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/65a16e039bef8c00086acdb8

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz

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:

• OWNERS [rikatz]

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

[rikatz]

/hold

[rikatz]

/hold cancel

[rikatz]

/hold

I will add image building and push here as well

[tao12345666333]

The inputs.run_e2e is used to manually run the e2e test workflow. If we remove this condition, not all steps will be executed.

[rikatz]

it was triggering the test for anything. I would say that maybe for e2e just on those corner case, people can do a stupid change on .go files :)

[strongjz]

i use it for testing and would like to keep it, when CI is broken on branches its nice to be able to just run github action e2e.

[rikatz]

/hold cancel

[strongjz]

i thought we were keeping the cloudbuilds and adding the GHA functionality?

[rikatz]

I have removed just from this image, as it is a bit borked and the name from it is different from folder, etc etc

[strongjz]

/cherry-pick release-1.9

[k8s-infra-cherrypick-robot]

@strongjz: #10826 failed to apply on top of branch "release-1.9":

Applying: Reuse workflow CI
.git/rebase-apply/patch:453: trailing whitespace.
 
.git/rebase-apply/patch:601: new blank line at EOF.
+
.git/rebase-apply/patch:665: new blank line at EOF.
+
warning: 3 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	.github/workflows/ci.yaml
M	images/cfssl/rootfs/Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging images/cfssl/rootfs/Dockerfile
CONFLICT (content): Merge conflict in images/cfssl/rootfs/Dockerfile
Auto-merging .github/workflows/ci.yaml
CONFLICT (content): Merge conflict in .github/workflows/ci.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Reuse workflow CI
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.9

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.