-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
kubetest2: implement "EKS" deployer, deprecate eks kubetest1 #16890
Conversation
/assign @amwat |
@amwat @BenTheElder Any updates? The |
I am handing off initial reviews of kubetest2 @amwat to loadbalance my PR review assignment overflow. Amit is very familiar with the kubetest2 internals and reviewed a lot of the existing code. feel free to ping me for an approve when this is reviewed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
for the kubetest2 parts
package main | ||
|
||
import ( | ||
"github.com/aws/aws-k8s-tester/eks" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor nit: looks like this is actually the deployer implementation.
this might get confusing later since "tester" has a different meaning in the kubetest2 sense.
might want to rename this later (just something to keep at the back of our minds) .
@amwat PTAL. I would like to get this |
/test pull-test-infra-bazel |
@gyuho: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
we don't have any prowjobs on this yet and currently
and a typical run looks like this:
we are working on standardizing around this soon. |
} | ||
|
||
// newEKS creates a new EKS deployer. | ||
func newEKS(timeout time.Duration, verbose bool) (ekstester.Deployer, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like kubetest main uses this
Lines 243 to 244 in e86e60c
case "eks": | |
return newEKS(timeout, verbose) |
maybe also leave deletion of kubetest1 eks as a follow PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, just fixed it. We are ok to remove kubetest1 now, since it's broken.
Happy to contribute. I will research more to see if we can support other tooling. |
@amwat PTAL. |
ref. kubernetes/test-infra#16890 Signed-off-by: Gyuho Lee <leegyuho@amazon.com>
Signed-off-by: Gyuho Lee <leegyuho@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@BenTheElder Kindly ping :) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, gyuho 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:
Approvers can indicate their approval by writing |
ref. #11380
@BenTheElder Is there any example config to use
kubetest2
?kubetest1
for EKS has not been maintained... We'd like to fix it withkubetest2
.