You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Some of my applications have docker images which are 30GBs in size, which take a lot of time to pull. The idea was to pull them through Harbor instead, so its inside the cluster network and it should be much faster.
I'm trying to install Harbor in my GKE cluster to use it as a proxy cache. But whatever i try i can't get my apps to pull faster.
What is the expected pull speed that i should be getting from pulling an image from harbor from within the cluster? my pull speed with harbor its the same or worse.
Thanks
The text was updated successfully, but these errors were encountered:
For the first time, the image is not cached in the local harbor, pulling image from harbor proxy cache doesn't faster.
If the image is already cached in the Harbor proxy cache, pulling from the proxy cache should be faster than pulling from the remote registry when the local network is faster.
That's why i tried out harbor proxy cache in the first place. But i can't see the "should be faster" part.
Is there any guideline on how much faster should it be? Should the speed increment be relevant or irrelevant?
Is there any success story in which someone goes from 2gbps to 10gbps in GKE or other cluster?
All of those questions are to answer this one: Should I spend more time debugging this?
Hello,
Some of my applications have docker images which are 30GBs in size, which take a lot of time to pull. The idea was to pull them through Harbor instead, so its inside the cluster network and it should be much faster.
I'm trying to install Harbor in my GKE cluster to use it as a proxy cache. But whatever i try i can't get my apps to pull faster.
What is the expected pull speed that i should be getting from pulling an image from harbor from within the cluster? my pull speed with harbor its the same or worse.
Thanks
The text was updated successfully, but these errors were encountered: