cAdvisor E2Es should run on the same images as the Kubernetes node E2Es

[timstclair]

If possible, we should simply reuse the e2e-node images. If not, we should at least add a containervm-v20160321 node to cAdvisor, and move coreos-beta to coreos-stable.

cAdvisor image list:

• e2e-cadvisor-ubuntu-trusty
• e2e-cadvisor-container-vm-v20151215
• e2e-cadvisor-container-vm-v20160127
• e2e-cadvisor-rhel-7
• e2e-cadvisor-coreos-beta (temporarily disabled)

k8s e2e_node list:

• e2e-node-ubuntu-trusty-docker9-v1-image
• e2e-node-ubuntu-trusty-docker10-v1-image
• e2e-node-coreos-stable20160622-image
• e2e-node-containervm-v20160321-image

/cc @vishh @pwittrock

[vishh]

+1. This will reduce maintenance overhead.

On Thu, Jun 30, 2016 at 5:04 PM, Tim St. Clair notifications@github.com
wrote:

If possible, we should simply reuse the e2e-node images. If not, we should
at least add a containervm-v20160321 node to cAdvisor, and move coreos-beta
to coreos-stable.

cAdvisor image list

cadvisor/build/jenkins_e2e.sh

Line 28 in 5a28a0c

e2e-cadvisor-ubuntu-trusty

:

• e2e-cadvisor-ubuntu-trusty
• e2e-cadvisor-container-vm-v20151215
• e2e-cadvisor-container-vm-v20160127
• e2e-cadvisor-rhel-7
• e2e-cadvisor-coreos-beta (temporarily disabled)

k8s e2e_node list
https://github.com/kubernetes/kubernetes/blob/23e7b6653fe37cf597c1ed4a11b8c66c771059a0/test/e2e_node/jenkins/jenkins-ci.properties#L6
:

• e2e-node-ubuntu-trusty-docker9-v1-image
• e2e-node-ubuntu-trusty-docker10-v1-image
• e2e-node-coreos-stable20160622-image
• e2e-node-containervm-v20160321-image

/cc @vishh https://github.com/vishh @pwittrock
https://github.com/pwittrock

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1361, or mute the thread
https://github.com/notifications/unsubscribe/AGvIKLBKHOGA7DZcL7sJF8PAxRBBekw3ks5qRFl0gaJpZM4JCtFp
.