CatalogSource object does not have link to the grpc url of the corresponding registry pod. I setup a new cluster on aws ( Release: 4.0.0-0.alpha-2019-02-18-164603 ). I installed `ectd` from community operators. Later, updates were pushed to quay for community operators. The following morning, I no longer see community operators in Operator Hub UI. If I do `kubectl get packagemanifests` no community operators show up. I check the the corresponding `CatalogSource` object and it does not have the grpc link in its staus. kubectl get catsrc -n openshift-operators installed-community-global-operators -o yamlapiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: creationTimestamp: 2019-02-18T20:05:02Z generation: 3 name: installed-community-global-operators namespace: openshift-operators ownerReferences: - apiVersion: marketplace.redhat.com/v1alpha1 blockOwnerDeletion: true controller: true kind: CatalogSourceConfig name: installed-community-global-operators uid: 79f19939-33b8-11e9-875d-0a15c177e3ee resourceVersion: "189876" selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-operators/catalogsources/installed-community-global-operators uid: 7a08d70f-33b8-11e9-aae7-065b5489c51a spec: address: 172.30.240.11:50051 displayName: Community Operators icon: base64data: "" mediatype: "" publisher: Community sourceType: grpc status: lastSync: 2019-02-18T23:46:09Z registryService: createdAt: 2019-02-18T23:46:09Z protocol: grpc
*** This bug has been marked as a duplicate of bug 1677329 ***
`CatalogSource` object does have the grpc link, it's in spec.