switch some more images to gcr for reliability

[brendandburns]

@quinton-hoole @ixdy

[ghost]

LGTM. We probably want some hierarchy under gcr.io/google_containers (e.g. to separate the custom Kubernetes-built ones from the generic ones like busybox). I assume that all of the images in this PR have been uploaded to gcr.io?

[ghost]

Oh, and are all of their dependencies in gcr.io also?

[k8s-bot]

GCE e2e build/test passed for commit c3f4b3f.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[thockin]

Other than the ones we build from code, who is keeping this nginx (for example) up to date?

[ghost]

Agreed. I discussed this with @brendandburns offline. Seems we
could/should fix that problem as a separate issue. Pretty sure it exists
independently of this PR.

On Tue, Jun 16, 2015 at 2:06 PM, Tim Hockin notifications@github.com
wrote:

Other than the ones we build from code, who is keeping this nginx (for
example) up to date?

—
Reply to this email directly or view it on GitHub
#9887 (comment)
.

[satnam6502]

Any idea why this test failed? http://kubekins.dls.corp.google.com/job/kubernetes-e2e-gce/7046/testReport/junit/(root)/Kubernetes%20e2e%20suite/EmptyDir_volumes_should_support_r_w/

[ghost]

It looks like getContainerOutputInNamespace() failed to get the logs from the container (hence empty string):

Expected
:
to contain substring
: mount type of "/test-volume": tmpfs

I doubt whether that has anything to do with this PR.

[ghost]

Closes #8849