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

Automate Docker Validation Process #57

Closed
12 of 16 tasks
aronchick opened this issue Jul 22, 2016 · 15 comments
Closed
12 of 16 tasks

Automate Docker Validation Process #57

aronchick opened this issue Jul 22, 2016 · 15 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone

Comments

@aronchick
Copy link
Contributor

aronchick commented Jul 22, 2016

EDITED by @dchen1107 on Sept 23, 2016

Description

Currently, Docker (https://www.docker.com/) is the default container runtime used by Kubernetes. Kubernetes release quality is significantly affected by Docker release quality.

The container technology evolves very rapidly, and so does Docker. Kubernetes can’t stick with a specific Docker version because

  • Customers might ask for new features in new Docker release.
  • Each Docker release solves some known issues and enhances the overall reliability and performance.

Docker releases per month, and before each release there are also several pre-releases. To ensure Kubernetes compatible with new Docker release, every quarter we had to invest at least 2-week engineer time to manually validate Docker release quality. For example, for 1.3 Kubernetes release, Kubernetes engineer manually validated

but we still couldn't cover all Docker (pre)release.

Thus, we developed the automated docker validation framework. It is a framework automatically validates newest Docker (pre)release against Kubernetes HEAD everyday, the validation includes functionality validation and performance validation.

Progress Tracker

@aronchick aronchick added this to the v1.4 milestone Jul 22, 2016
@idvoretskyi
Copy link
Member

cc @kubernetes/sig-node

@idvoretskyi idvoretskyi added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Jul 25, 2016
@timothysc
Copy link
Member

Same comment on this one regarding full description.

@dchen1107
Copy link
Member

  • Built the infrastructure to run node e2e tests against nightly docker build on GCI. Now we test docker nightly builds and generate the reports.

TODO:
Need to enable performance tests to validate docker nightly build too.

@philips
Copy link
Contributor

philips commented Aug 17, 2016

@dchen1107 Do you have a link to these test runs people should watch?

@dchen1107
Copy link
Member

I just updated the initial issue description to reflect the current progress on the project. cc/ @philips @aronchick

There are more to be done, especially on docker specific tests side. But I decided to punt on those since we are working on CRI, and those tests can be very easy to implement against the new API.

@janetkuo
Copy link
Member

janetkuo commented Sep 2, 2016

@Random-Liu @dchen1107 Are the docs ready? Please update the docs in https://github.com/kubernetes/kubernetes.github.io, and then add PR numbers and check the docs box in the issue description

@Random-Liu
Copy link
Member

Status Update: The test result will be exposed in kubernetes/test-infra#523.

@Random-Liu
Copy link
Member

The validation result is shown in testgrid now. https://k8s-testgrid.appspot.com/docker

@jaredbhatti
Copy link

Ping on docs. Can you give an update and/or a docs PR?

@dchen1107
Copy link
Member

Status updates:

  • Docker performance validation test are done, but only limiting to CREATE operation. DELETE, LIST, INSPECT operations will be added later.
  • The test results can be accessed publicly at: https://k8s-testgrid.appspot.com/docker

@jaredbhatti
Copy link

@dchen1107 @aronchick @Random-Liu Another ping for docs. Any PRs you can point me to?

@dchen1107
Copy link
Member

For validation test framework, I don't think we need any doc except release notes mentioning which docker version being qualified.

@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 7, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

howardjohn pushed a commit to howardjohn/enhancements that referenced this issue Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests