Maximum size of a image pushed to project. #15485
Unanswered
prashi2202
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Did you try to upload it already? |
Beta Was this translation helpful? Give feedback.
1 reply
-
This happened to me because nginx stores the transient pod in memory. I solved this issue by bypassing the nginx with
Maybe you have the same problem. After this i had no issues uploading big images, with much less memory actually Your original error tho, is that you are exceeding the quota assigned to your NS, it seems. you have a limit of 2GB max that you can use for ALL your pods, and in this pod you are asking for 4 times more memory. So.... start with less and within your quota limits |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
We are testing harbor setup on EKS cluster and we need to know should be the resource size to push a large image (75GB) into a given project within harbor instance.
Current configuration
Cluster EKS:
$ kubectl get pods --kubeconfig kubeconfig-readonly.yaml
NAME READY STATUS RESTARTS AGE
harbor-chartmuseum-7c8f9cbb55-46mn8 1/1 Running 0 15h
harbor-core-5d4f6ff85-mnzxv 1/1 Running 0 15h
harbor-jobservice-68d965b75b-b9sm7 1/1 Running 0 13h
harbor-jobservice-68d965b75b-ssjxb 1/1 Running 1 15h
harbor-notary-server-f5798db99-rsnht 1/1 Running 0 15h
harbor-notary-signer-6d4b6768f-9g778 1/1 Running 0 15h
harbor-portal-5647cf8d45-gcclj 1/1 Running 0 15h
harbor-redis-0 1/1 Running 0 15h
harbor-registry-66c88cb8f9-hnsq7 2/2 Running 0 15h
harbor-registry-676b988d75-zd8kg 2/2 Running 0 15h
harbor-trivy-0 1/1 Running 0 15h
Registry resource size:
vas:harbor-registry-676b988d75-zd8kg
registry:2Gi
registryctl:2Gi
vas:harbor-registry-676b988d75-zd8kg
registry:100m
registryctl:100m
Beta Was this translation helpful? Give feedback.
All reactions