Closed mailman-2097 closed 1 month ago
Hi,
This is due to an upstream change by Red Hat. If you remove the existing community operators catalogsource and add this one, you should be good.
apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: community-operators namespace: openshift-marketplace spec: displayName: Community Operators image: quay.io/operatorhubio/catalog:latest publisher: operatorhubio sourceType: grpc
Not sure if you’ve seen this or not…
https://okd.io/blog/2024/06/01/okd-future-statement/
In short, we’ve shifted focus to OKD 4.16 SCOS and greater. We’re working on testing and documenting a clear path from 4.15 FCOS to 4.16 SCOS and then 4.17 SCOS. Stay tuned for that.
Many thanks for your response.
I was able to setup the okd 4.16. The operator hub is working now.
Describe the bug OKD OperatorHub is not operational as no operators are being displayed
Version This is OKD Single Node Cluster created with UPI install on Proxmox VE running on HP MiniPC i7-10700T CPU @ 2.00GHz, 32GB Ram, NVME SSD.
How reproducible This should be reproducible easily.
Log bundle https://www.dropbox.com/scl/fi/9ji7cf1z50z01u18xt6s3/must-gather.local.3668016615067012211.tar.gz?rlkey=5lwqwxlftecdtr3r3esld4dqj&st=gn19kf9w&dl=0