Open andrewsykim opened 5 years ago
/priority important-soon
Join the testing-commons subproject under sig-testing to be more involved in this effort.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/lifecycle frozen
Hey @andrewsykim, what's the status of this effort? Seems fairly paused? Is there some documentation somewhere for sig-testing? I'm looking to make some improvements to the AWS e2e Cloud Provider and want to make sure I'm doing so in line with the direction of the project.
In the past few releases we've been focused on migrating in-tree cloud providers (
k8s.io/kubernetes/pkg/cloudprovider/providers
) out-of-tree but we've neglected the providers that are a part of the e2e framework (https://github.com/kubernetes/kubernetes/tree/master/test/e2e/framework/providers
) which also needs to be removed before we can stop vendoring cloud SDKs. There's a lot of refactoring needed in the e2e framework before this is possible so this will likely take a few releases.This is mainly just a tracking issue for https://github.com/kubernetes/kubernetes/issues/75604 & https://github.com/kubernetes/kubernetes/issues/75601.
cc @timothysc @stevesloka @neolit123 @pohly