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 EKS periodic jobs, upgrade "awstester" vendor #9940

Merged
merged 4 commits into from
Oct 30, 2018
Merged

*: add EKS periodic jobs, upgrade "awstester" vendor #9940

merged 4 commits into from
Oct 30, 2018

Conversation

gyuho
Copy link
Member

@gyuho gyuho commented Oct 27, 2018

ref. #9814

  • Upgrade "awstester" dependency
  • Add "eks" to "kubetest --deployment" flag
  • Add initial EKS e2e tests as periodic

/cc @krzyzacy @d-nishi

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. area/config Issues or PRs related to code in /config labels Oct 27, 2018
@krzyzacy
Copy link
Member

instead of kubernetes/eks, this probably need to be under kubernetes/sig-foo

does eks belongs to sig-aws?

@gyuho
Copy link
Member Author

gyuho commented Oct 27, 2018

@krzyzacy
Copy link
Member

Also instead of a postsubmit, I would run it as a periodic job instead. You shouldn't need to checkout any repo?

kubernetes/kubernetes:

# Run Kubernetes e2e tests with EKS prod build 1.10
- name: pull-kubernetes-e2e-tip-aws-eks-1.10-prod
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use pull- for presubmits, this should be something like ci-

kubernetes/kubernetes:

# Run Kubernetes 1.10 branch e2e tests with EKS prod build 1.10
- name: pull-kubernetes-e2e-1.10-aws-eks-1.10-prod
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BenTheElder
Copy link
Member

Does this need to be a post-submit? What about a periodic / cron job?
Most (nearly all) of our CI end to end testing consumes (downloads and uses) continuously pre-built binaries, which cuts out a lot of compute / memory in the build cluster.

@gyuho
Copy link
Member Author

gyuho commented Oct 27, 2018

@BenTheElder @krzyzacy

consumes (downloads and uses) continuously pre-built

I see. Yes, then we can switch to periodic jobs. Since this is the very beginning to us, we do not want to use all the computing resources for every merge :)

Will update this PR shortly.

@gyuho gyuho mentioned this pull request Oct 28, 2018
12 tasks
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 28, 2018
@gyuho gyuho changed the title *: add EKS post-submit jobs, upgrade "awstester" vendor *: add EKS periodic jobs, upgrade "awstester" vendor Oct 28, 2018
@d-nishi
Copy link

d-nishi commented Oct 28, 2018

@gyuho - this can be sig-aws

@justinsb are you ok supporting the idea of kubernetes/sig-aws? we are integrating CI signal for the SIG-AWS subprojects. Thoughts please?

@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 29, 2018
@gyuho
Copy link
Member Author

gyuho commented Oct 29, 2018

@krzyzacy @BenTheElder Addressed. Now these are periodic jobs. PTAL. Thanks!

@justinsb
Copy link
Member

I'm fine with the name change cc @d-nishi !

Copy link
Member

@krzyzacy krzyzacy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make all shared env into one preset. Also maybe you can merge the three jobs into a single yaml file?

preset-service-account: "true"
preset-k8s-ssh: "true"
preset-ci-kubernetes-e2e-1-10-aws-eks-1-10: "true"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

babynit: unnecessary new line

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed. Thanks.

name: ci-kubernetes-e2e-1-10-aws-eks-1-10-prod
labels:
preset-service-account: "true"
preset-k8s-ssh: "true"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you won't need the ssh key as that's for gce

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed. Thanks.


spec:
containers:
- image: 607362164682.dkr.ecr.us-west-2.amazonaws.com/awstester-e2e:20181029-141d7d02b498
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this image public?

Copy link
Member Author

@gyuho gyuho Oct 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be accessible with the credential that's used here. We can make it public if that's required :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hummm, wonder how prow will be able to access it as the credential is still in the secret. ImagePulling happens in pod init time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or we can try and see :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krzyzacy Just listed it as a public image. Let's try! Thanks!

Copy link
Member

@krzyzacy krzyzacy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 7eb26c82a316e6c2d27ce735b5c610fb0da6efaf

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 30, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gyuho, krzyzacy

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 30, 2018
@k8s-ci-robot k8s-ci-robot merged commit 27957ef into kubernetes:master Oct 30, 2018
@k8s-ci-robot
Copy link
Contributor

@gyuho: Updated the job-config configmap using the following files:

  • key k8s-aws-eks-1.10.yaml using file config/jobs/kubernetes/sig-aws/eks/k8s-aws-eks-1.10.yaml

In response to this:

ref. #9814

  • Upgrade "awstester" dependency
  • Add "eks" to "kubetest --deployment" flag
  • Add initial EKS e2e tests as periodic

/cc @krzyzacy @d-nishi

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.

@gyuho gyuho deleted the eks branch October 30, 2018 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/testgrid cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants