Should upgrade test run with all KIngress?

[nak3]

In what area(s)?

/area networking
/area test-and-release

Describe the feature

As per title, we always use net-istio for the upgrade test(e2e-upgrade-tests.sh). It does not support to run it against Kourier or other Ingress solutions actually.

So I would like to request to run e2e-upgrade-tests.sh against other Ingress providers and see the status in test grid.

Is it not good idea?

If we will test against other Kingress, I think we would need following tasks:

1. Update e2e-upgrade-tests.sh to install/configure other KIngress in install_latest_release().
2. Add the test to test-infra's each ingress job.

[nak3]

The background of this request is that downstream (using net-kourier) frequently fails on TestProbe executed by go_test_e2e -tags=preupgrade -timeout=20m ./test/upgrade. We are still not sure about the root cause, but I think the test results could be different among KIngresses as their Ingress reconciliation logic is different.

[mattmoor]

I'd like to be able to run it with any kingress, and I'd imagine the kourier folks would as well.

cc @tcnghia @dprotaso

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[mattmoor]

/lifecycle frozen

@nak3 any interest in trying to make this work post-submit for all kingress?

[nak3]

/assign

Sure, I will try.

[markusthoemmes]

FWIW I did add an upgrade test to Kourier specifically and am planning to move that to knative/networking so each ingress impl. can test their upgrade behavior in isolation.

[evankanderson]

Is this still an issue?

If so, is this something which should go into the networking implementations or the serving repo? It would be nice to have a property that we didn't need bidirectional import/testing dependencies between the repos.

/triage accepted