-
Notifications
You must be signed in to change notification settings - Fork 40k
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
cluster/eks: initial commit #71322
cluster/eks: initial commit #71322
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gyuho If they are not already assigned, you can assign the PR to them by writing 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 |
Add EKS e2e script. Signed-off-by: Gyuho Lee <leegyuho@amazon.com>
/cc @shyamjvs |
To give more background on this PR, we've recently added EKS test plugin to kubetest, but haven't been able to get the kubectl to work. And find out it was calling Line 34 in 2b0212d
Which calls kubernetes/cluster/kube-util.sh Line 39 in 2b0212d
I hope having this script helps us debug the Thanks! EDIT: This is the error message that I was getting:
|
Can kubetest call kubectl directly? This seems like a pretty round about way of fixing the stated issue. Note that cluster/kubectl.sh has been deprecated for 4 years #9342 . Please also see the deprecation notice in https://github.com/kubernetes/kubernetes/blob/master/cluster/README.md and #49213. How does this work for GKE? |
ouch by default kubectl is from the image (which is from gcloud sdk), and cluster/kubectl.sh is from the extracted k8s tarball and we were not mucking with PATH :-\ We probably can change how skew tests work, cc @pwittrock @mengqiy @fejta on thoughts |
@gyuho: The following tests 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. |
That would make things easier for us as provider plugin maintainers.
Yeah, I would like to specify the kubectl path and all the flags (e.g. |
Found out kubetest is setting I tried to overwrite this envs inside our plugin, but still does not work
It would be great if there's a way to pass these env vars to
|
Sorry for spamming. There are so many unknowns for a new kubetest plugin provider.
Error from kubernetes/test/e2e/framework/test_context.go Lines 371 to 385 in 2b0212d
That requires kubernetes/test/e2e/framework/provider.go Lines 79 to 99 in 2b0212d
Do we still require Thanks. |
I agree with @mikedanese that we should really stop using and adding to cluster/ :/ we should fix kubetest instead.
|
Yeah
Sounds good. Please let me know if you need any help! Looks like they are hardcoded in https://github.com/kubernetes/test-infra/blob/master/kubetest/e2e.go#L52. |
Help would definitely be appreciated! I'm still trying to help review work here but not really working on kubetest these days, mostly kind. We definitely want to get this working nicely with out of tree and without the cluster/* scripts as much as possible ... OTOH, @krzyzacy and I have some rough plans for a kubetest rewrite that would avoid these from the start, we might get to that in the spring (?) ... |
@BenTheElder Yes, I will create a proposing PR to allow provider to pass kubectl paths, in kubetest package. I think we can make changes in |
/hold |
We've added |
Add EKS e2e script.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Kubernetes e2e tests require each provider to implement its own util script, and EKS does not have one (fix aws/aws-k8s-tester#12).
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Trying to fix aws/aws-k8s-tester#12.
Special notes for your reviewer:
@krzyzacy @BenTheElder
ref. kubernetes/test-infra#9814
Does this PR introduce a user-facing change?: