-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.3.0
-
None
Description of problem:
Bridge Operator does not support OCP build and imagestream with Quay
Version-Release number of selected component (if applicable):
quay.io/quay/quay-openshift-bridge-rhel8-operator:v1.0.0-4
quay.io/quay/quay-openshift-bridge-rhel8-operator-catalog:v1.0.0-4
quay.io/quay/quay:v3.3.0-3
How reproducible:
Always
Steps to Reproduce:
1.Setup OCP and Quay
2.Install bridge operator
3.Create QuayIntegration CR
apiVersion: redhatcop.redhat.io/v1alpha1 kind: QuayIntegration metadata: name: example-quayintegration spec: clusterID: openshift credentialsSecretName: quay-bridge/quay-integration quayHostname: https://quay-test33-quay-quay-app.apps.dyan-az0426.qe.azure.devcluster.openshift.com insecureRegistry: true
4.Create an application by template contains BuildConfig, Imagestream and DeployConfig
$ oc create -f rails-postgresql-example.yaml
5.Check namespace and image repo status in Quay
Actual results:
Create organization with openshift prefix, three robot account: default, builder, deployer ,and image repo with the same name with Imagestream. But no image tag existing
Expected results:
The image tag should exist
Additional info:
OCP build still pushes image to internal registry, deploy also pulls image from internal registry