-
Bug
-
Resolution: Done
-
Critical
-
None
-
False
-
False
-
Undefined
-
-
0
Basically all examples here for various storage provider configs are wrong (see DISTRIBUTED_STORAGE_CONFIG section: https://access.redhat.com/documentation/en-us/red_hat_quay/3.5/html/manage_red_hat_quay/quay-schema
E.g. for OCS/NooBaa it is documented as:
{
"rhocsStorage": [
"RHOCSStorage",
{
"access_key": "access_key"
},
{
"secret_key": "secret_key"
},
{
"bucket_name": "quay-datastore-9b2108a3-29f5-43f2-a9d5-2872174f9a56"
},
{
"hostname": "s3.openshift-storage.svc.cluster.local"
},
{
"is_secure": "true"
},
{
"port": "443"
},
{
"storage_path": "/datastorage/registry"
}
]
}
Where it should actually be:
{
"rhocsStorage": [
"RHOCSStorage",
{
"access_key": "access_key",
"secret_key": "secret_key",
"bucket_name": "quay-datastore-9b2108a3-29f5-43f2-a9d5-2872174f9a56",
"hostname": "s3.openshift-storage.svc.cluster.local",
"is_secure": "true",
"port": "443",
"storage_path": "/datastorage/registry"
}
]
}
This is probably due to the fact that it's easy to oversee in JSON formatting. All examples should be formatted as YAML as this is what the rest of the documentation is using:
rhocsStorage:
- RHOCSStorage
- access_key: access_key
secret_key: secret_key
bucket_name: quay-datastore-9b2108a3-29f5-43f2-a9d5-2872174f9a56
hostname: s3.openshift-storage.svc.cluster.local
is_secure: 'true'
port: '443'
storage_path: /datastorage/registry
- is related to
-
PROJQUAY-1854 Document various storage engine setups for the Quay operator
-
- Closed
-
