Description:
This is an issue found when using Quay 3.3 RC operator image "quay-operator:v1.1.0-rc1" to deploy Quay ENV, with specifying externalAccess as Ingress or NodePort, after create QuayEcosystem CR, the QuayEcosystem CR was stuck at "Reconciling QuayEcosystem", and Quay operator log only show the following logs:
"

{"level":"info","ts":1586416718.0010867,"logger":"controller_quayecosystem","msg":"Reconciling QuayEcosystem","Request.Namespace":"quay-enterprise","Request.Name":"demo3-quayecosystem"}

"

{"level":"info","ts":1586416840.5826783,"logger":"controller_quayecosystem","msg":"Reconciling QuayEcosystem","Request.Namespace":"quay-enterprise","Request.Name":"demo4-quayecosystem"}

Note: Compared with specifying externalAccess as loadbalancer, with this config in CR quay QuayEcosystem CR can be deployed successfully.
ENV:
Quay imge: quay.io/quay/quay:3.2.1-1
Quay Operator: quay-operator:v1.1.0-rc1
Steps:
1. Deploy Quay Operator with the following steps.
Modify the file "deploy/operator.yaml" to replace the image with
"quay.io/kmullins/quay-operator:v1.1.0-rc1"
Run the following commands to deploy the Operator to OpenShift:
$ oc new-project quay-enterprise
$ oc create -f deploy/crds/redhatcop.redhat.io_quayecosystems_crd.yaml
$ oc create -f deploy/service_account.yaml
$ oc create -f deploy/cluster_role.yaml
$ oc create -f deploy/cluster_role_binding.yaml
$ oc create -f deploy/role.yaml
$ oc create -f deploy/role_binding.yaml
$ oc create -f deploy/operator.yaml
2. Deploy Quay ENV by running "oc create -f quayecosystem_cr_20200409_ingress.yaml"
Expected Result:
Quay ENV will be deployed successfully using new Operator.
Actual Results:
Quay ENV deployment was stuck at "Reconciling QuayEcosystem".
OCP ENV:
https://console-openshift-console.apps.lzha0409.qe.devcluster.openshift.com
kubeadmin, password: niGyF-iER4z-nYWLK-ks3dW
The following is the CR file used:
lizhang@lzha-mac deploy % cat quayecosystem_cr_20200409_ingress.yaml
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
name: demo3-quayecosystem
spec:
quay:
imagePullSecretName: redhat-pull-secret
image: quay.io/quay/quay:3.2.1-1
keepConfigDeployment: true
enableRepoMirroring: true
externalAccess:
type: Ingress
annotations:
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
resources:
requests:
memory: "2048Mi"
cpu: "2000m"
limits:
memory: "4096Mi"
cpu: "4000m"
database:
image: registry.access.redhat.com/rhscl/postgresql-96-rhel7:1
volumeSize: 30Gi
envVars:

• name: DEBUGLOG
  value: "true"
  clair:
  enabled: true
  image: quay.io/quay/clair-jwt:v3.2.1-1
  imagePullSecretName: redhat-pull-secret
  updateInterval: "60m"
  database:
  image: registry.access.redhat.com/rhscl/postgresql-96-rhel7:1
  resources:
  requests:
  memory: "2048Mi"
  cpu: "2000m"
  limits:
  memory: "4096Mi"
  cpu: "4000m"
  volumeSize: 30Gi
  lizhang@lzha-mac deploy % cat quayecosystem_cr_20200409_nodeport.yaml
  apiVersion: redhatcop.redhat.io/v1alpha1
  kind: QuayEcosystem
  metadata:
  name: demo4-quayecosystem
  spec:
  quay:
  imagePullSecretName: redhat-pull-secret
  image: quay.io/quay/quay:3.2.1-1
  keepConfigDeployment: true
  enableRepoMirroring: true

• externalAccess:
  type: NodePort
  nodePort: 30100
  configNodePort: 30101*
  resources:
  requests:
  memory: "2048Mi"
  cpu: "2000m"
  limits:
  memory: "4096Mi"
  cpu: "4000m"
  database:
  image: registry.access.redhat.com/rhscl/postgresql-96-rhel7:1
  volumeSize: 30Gi
  envVars:

• name: DEBUGLOG
  value: "true"
  clair:
  enabled: true
  image: quay.io/quay/clair-jwt:v3.2.1-1
  imagePullSecretName: redhat-pull-secret
  updateInterval: "60m"
  database:
  image: registry.access.redhat.com/rhscl/postgresql-96-rhel7:1
  resources:
  requests:
  memory: "2048Mi"
  cpu: "2000m"
  limits:
  memory: "4096Mi"
  cpu: "4000m"
  volumeSize: 30Gi