-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Comments
cc @kubernetes/sig-node |
Same comment on this one regarding full description. |
TODO: |
@dchen1107 Do you have a link to these test runs people should watch? |
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. |
@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 |
Status Update: The test result will be exposed in kubernetes/test-infra#523. |
The validation result is shown in testgrid now. https://k8s-testgrid.appspot.com/docker |
Ping on docs. Can you give an update and/or a docs PR? |
Status updates:
|
@dchen1107 @aronchick @Random-Liu Another ping for docs. Any PRs you can point me to? |
For validation test framework, I don't think we need any doc except release notes mentioning which docker version being qualified. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
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
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
The text was updated successfully, but these errors were encountered: