-
Bug
-
Resolution: Done
-
Major
-
quay-v3.7.0
-
False
-
None
-
False
Problem Description:
For quay build test against 3.7.0, QE hit some problems. Depending on developer's feedback, the resolution about these problems is to set a suitable value for specific attribute. So file this issue to track quay build document update.
CONTAINER_MEMORY_LIMITS and CONTAINER_MEMORY_REQUEST
- Reference :
PROJQUAY-3351: Quay 3.7.0 build container POD was failed with error "Invalid build token: Signature has expired" - Recommend setting
CONTAINER_MEMORY_LIMITS: 1Gi CONTAINER_MEMORY_REQUEST: 1Gi
JOB_REGISTRATION_TIMEOUT
- Reference : slack chat history
- Recommend setting
JOB_REGISTRATION_TIMEOUT: 600
CORS configuration for AWS and OSP
- Reference:
PROJQUAY-3359Quay 3.7.0 can't start build job by uploading Dockerfile - Recommend setting on AWS
[ { "AllowedHeaders": [ "Authorization" ], "AllowedMethods": [ "GET" ], "AllowedOrigins": [ "*" ], "ExposeHeaders": [], "MaxAgeSeconds": 3000 }, { "AllowedHeaders": [ "Content-Type", "x-amz-acl", "origin" ], "AllowedMethods": [ "PUT" ], "AllowedOrigins": [ "*" ], "ExposeHeaders": [], "MaxAgeSeconds": 3000 } ]
- need to find out the configuration on Openstack and gcp