How to install Quay using noobaa standalone object gateway
Issue
-
Using default noobaa.yaml (from the original doc) does not make noobaa object storage connection ready
$ oc get noobaas NAME MGMT-ENDPOINTS S3-ENDPOINTS IMAGE PHASE AGE noobaa ["https://10.0.136.204:31790"] ["https://10.0.136.204:32465"] registry.redhat.io/ocs4/mcg-core-rhel8@sha256:d64bd6b976f4c5e2a03401838c3d710e3035dd1ab8249a55ed1df3c598963729 Connecting 4h18m
-
noobaa-db-pg pod is in CrashLoopBackOff
-
After creating QuayRegistry instance using the default configuration, some of the pods are not created
$ oc get pods NAME READY STATUS RESTARTS AGE example-registry-clair-app-57d8fbd965-pnwwg 0/1 ContainerCreating 0 17m example-registry-clair-postgres-7cdfcc4f66-cp84l 1/1 Running 1 17m example-registry-quay-app-upgrade-7679d6f899-564mx 0/1 Init:0/1 0 17m example-registry-quay-config-editor-6f4978549-rvj8t 0/1 ContainerCreating 0 17m example-registry-quay-database-699c554446-hpd66 1/1 Running 0 17m example-registry-quay-postgres-init-d5x76 0/1 Completed 0 17m
-
Quay pod shows error "MountVolume.SetUp failed for volume "certs": secret "example-registry-quay-config-secret-bdc554db2b" not found"
- All kubernetes objects are not created/updated successfully: failed to create typed patch object: .spec.ObjectBucketName: field not declared in schema
Environment
-
Red Hat OpenShift Container Platform
- 4.7.z
-
Red Hat Quay
- 3.6.z
-
OpenShift Container Storage Operator
-
Noobaa Standalone Object Gateway
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.