Jaeger-operator: Is the time to take out our images from docker hub?

[jkandasa]

Today I exected e2e tests and hits the image pull limit issue.
I think it is time to take out dependent images from the docker hub.
What do you think?
@objectiser @jpkrohling @kevinearls

Error:

 Failed to pull image "jaegertracing/vertx-create-span:operator-e2e-tests": rpc error: code = Unknown desc = Error reading manifest 
 operator-e2e-tests in docker.io/jaegertracing/vertx-create-span: toomanyrequests: You have reached your pull rate limit. 
 You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[jkandasa]

I believe quay.io could be a right alternate option.
https://www.openshift.com/blog/mitigate-impact-of-docker-hub-pull-request-limits

[kevinearls]

@jkandasa Yes, definitely. It shouldn't take too much work, but let me know if you need any help.

You will need to update some of the Jenkins jobs too.

[jpkrohling]

Image pushed to quay: https://quay.io/repository/jaegertracing/vertx-create-span