Unable to use NooBaa as Storage Backend

[quay]

Unable to use NooBaa as Storage Backend

[sabre1041]

@kurtismullins during testing, defined the following CR and was able to successfully make use of OCS (using Quay v3.1.3)

spec:
  quay:
    registryBackends:
      - name: rhocs
        rhocs:
          accessKey: OMITTED
          bucketName: quay-0dd68a8a-457f-4da9-9807-ca5c4c941e99
          secretKey: OMITTED
          hostname: OMITTED
          secure: true
          port: 443

[kurtismullins]

@sabre1041

Thank you for updating the documentation.

Additional testing has been done with the updated documentation and operator. From what I understand, the Quay pod is not deployed when configuring S3 or Google Cloud with secrets in a secrets file.

However, it does appear to work correctly if the secrets are included in the CR directly.

Error Output:

{"level":"info","ts":1576830630.295516,"logger":"controller_quayecosystem","msg":"Reconciling QuayEcosystem","Request.Namespace":"quay-app","Request.Name":"quay-test-320"}
{"level":"error","ts":1576830630.295652,"logger":"controller_quayecosystem","msg":"Secret Validation","Namespace":"quay-app","Name":"s3-account","error":"Failed to validate provided secret with required parameters","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/travis/gopath/pkg/mod/github.com/go-logr/[email protected]/zapr.go:128\ngithub.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/validation.validateSecret\n\t/home/travis/gopath/src/github.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/validation/validate.go:525\ngithub.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/validation.Validate\n\t/home/travis/gopath/src/github.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/validation/validate.go:236\ngithub.com/redhat-cop/quay-operator/pkg/controller/quayecosystem.(*ReconcileQuayEcosystem).Reconcile\n\t/home/travis/gopath/src/github.com/redhat-cop/quay-operator/pkg/controller/quayecosystem/quayecosystem_controller.go:126\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/travis/gopath/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:216\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/travis/gopath/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:192\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/home/travis/gopath/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:171\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/home/travis/gopath/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/travis/gopath/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/home/travis/gopath/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:88"}

[sabre1041]

Resolved per #120

[gorantornqvist]

Still receive this error, config

spec:
    registryBackends:
      - name: rhocs
        rhocs:
          credentialsSecretName: s3-credentials
          bucketName: quay-bucket-2649ee59-66cd-4ebd-92cf-223533aa3b78
          hostname: s3.openshift-storage.svc
          secure: true
          port: 443

Specifying accessKey/secretKey gets passed thru the validation:

#          credentialsSecretName: s3-credentials
          accessKey: *******
          secretKey: *******