Description:

This is an issue found when deploy quay with quay operator, now when choose to use managed Route and managed TLS components, the TLS certificate generated by Quay Operator is not correct, and in mirror images jobs, hit error message "x509: certificate is valid for *.apps.quay-perf-738.perfscale.devcluster.openshift.com, not demo-quay-quay360818.router-default.apps.quay-perf-738.perfscale.devcluster.openshift.com""

While on the same OCP Cluster, with Quay 3.5.5 Operator(use managed Route), the TLS Cert generated by Quay Operator is correct, Mirror images Job works well.

Quay 3.6.0 Mirror image Job was failed with TLS Cert error:

time="2021-08-18T01:41:44Z" level=fatal msg="Error trying to reuse blob sha256:540db60ca9383eac9e418f78490994d0af424aab7bf6d0e47ac8ed4e2e9bcbba at destination: error pinging docker registry demo-quay-quay360818.router-default.apps.quay-perf-738.perfscale.devcluster.openshift.com: Get \"https://demo-quay-quay360818.router-default.apps.quay-perf-738.perfscale.devcluster.openshift.com/v2/\": x509: certificate is valid for *.apps.quay-perf-738.perfscale.devcluster.openshift.com, not demo-quay-quay360818.router-default.apps.quay-perf-738.perfscale.devcluster.openshift.com"

Quay 3.5.5:

Quay 3.6.0: