The Nexus Repository HA Operator needs to be installed first from the Operator Hub in an OpenShift project. After installing the operator, a custom resource definition (CRD) for NexusRepo needs to be created and configured with details like ingress settings, Docker repository subdomain/ingress, TLS settings, and the Nexus Repository license. The installation seems to complete successfully with the pod running, but no service or route is created to access the Nexus dashboard. This could be due to not providing the Nexus Repository Pro license in the CRD. To resolve the issue, the Nexus Repository Pro license needs to be properly configured in the CRD by base64 encoding the license file and adding it to the spec.license.fileContentBase64 field. Alternatively, Sonatype support can be contacted for assistance.

[DannyFranklin]

The Nexus Repository HA Operator needs to be installed first from the Operator Hub in an OpenShift project.
After installing the operator, a custom resource definition (CRD) for NexusRepo needs to be created and configured with details like ingress settings, Docker repository subdomain/ingress, TLS settings, and the Nexus Repository license.
The installation seems to complete successfully with the pod running, but no service or route is created to access the Nexus dashboard. This could be due to not providing the Nexus Repository Pro license in the CRD.
To resolve the issue, the Nexus Repository Pro license needs to be properly configured in the CRD by base64 encoding the license file and adding it to the spec.license.fileContentBase64 field.
Alternatively, Sonatype support can be contacted for assistance.