Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for additional test infrastructure providers #3033

Open
evankanderson opened this issue Jan 24, 2022 · 3 comments
Open

Add support for additional test infrastructure providers #3033

evankanderson opened this issue Jan 24, 2022 · 3 comments
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Milestone

Comments

@evankanderson
Copy link
Member

e.g. Equinix, AWS, etc.

Adding this to the roadmap, but it will definitely need some longer-term design and discussion with the CNCF test infrastructure community to make sure that we're building on supported foundations. (kubetest2? boskos?).

There's no urgent need for this; this is a tracking issue in case we discover that we either want broader k8s coverage or better stability / performance / cost in the future. (i.e. @dprotaso is currently tracking down upgrade test failures on GKE 1.21 that aren't present on GKE 1.20, and it would be interesting to see if the same errors are present on other clouds / infrastructure.)

@chizhg
Copy link
Member

chizhg commented Jan 24, 2022

/cc @kvmware

@chizhg chizhg moved this from Needs Design to In Design/Discussion in Infra (Productivity) Apr 7, 2022
@github-actions
Copy link

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 25, 2022
@chizhg
Copy link
Member

chizhg commented Apr 25, 2022

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 25, 2022
@upodroid upodroid added kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels May 20, 2022
@upodroid upodroid added this to the Icebox milestone May 20, 2022
@upodroid upodroid added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

3 participants