Should upgrade test run with all KIngress?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
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:
- Update e2e-upgrade-tests.sh to install/configure other KIngress in
install_latest_release(). - Add the test to test-infra's each ingress job.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with e2e-upgrade-tests.sh, especially install_latest_release(), to understand how net-istio is installed and configured. Then inspect test-infra's ingress jobs and the linked test grid. Done means the upgrade test runs against other KIngress providers and their status appears in the relevant test grid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- ci-cd, networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100