search

cloudfoundry / cf-for-k8s

The open source deployment manifest for Cloud Foundry on Kubernetes
Apache License 2.0
300 stars 115 forks source link

Move smoke-tests docker image to cloudfoundry org to avoid rate limiting #580

Closed davewalter closed 3 years ago

davewalter commented 3 years ago

Describe the bug

Smoke tests sometimes fail due to dockerhub rate limiting when pulling the cfrouting/httpbin image. We should either move it into the cloudfoundry org, or replace it with a maintained image in that org.

To Reproduce

Steps to reproduce the behavior:

  1. Deploy cf-for-k8s
  2. Repeatedly run smoke-tests
[2020-11-20 22:41:52.41 (UTC)]> cf push cf-for-k8s-smoke-1-app-a4ed0a269257d188 -o cfrouting/httpbin 
Pushing app cf-for-k8s-smoke-1-app-a4ed0a269257d188 to org cf-for-k8s-smoke-1-org-98f4fc3d9276e663 / space cf-for-k8s-smoke-1-space-69f7668a2f00b771 as admin...

Staging app and tracing logs...
StagingError - Staging error: failed to get image config: failed to fetch image metadata: failed to get image source: Error reading manifest latest in docker.io/cfrouting/httpbin: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
FAILED

Expected behavior

The smoke tests are reliable and not affected by dockerhub rate limiting.