-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
Description:
This is an issue found when use Quay TNG Operator to deploy Quay, after Quay was deployed successfully, found "Quay route" endpoint is not accessible, see screenshot.
Quay Catalogsoure Image:
quay.io/quay/quay-operator-catalog:v3.4.0-osbs
Quay image: quay.io/quay/quay:v3.4.0-osbs
OCP Version: 4.5.0
Steps:
- Deploy Quay TNG Operator Operator on OCP
- Create new Quay QuayRegistry CR
- Run "oc get route" to get quay route
- Access Quay route endpoint
Quay CR:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quaydemo
Expected Results:
Quay Rout can be accessed successfully.
Actual Results:
Quay Rout is not accessible.
Quay Route:
lizhang@lzha-mac quay3.4 % oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD quaydemo-quay quaydemo-quay-quay0340.apps.quay-perf-384.perf-testing.devcluster.openshift.com quaydemo-quay-app https passthrough/Redirect None quaydemo-quay-config-editor quaydemo-quay-config-editor-quay0340.apps.quay-perf-384.perf-testing.devcluster.openshift.com quaydemo-quay-config-editor http edge/Redirect None
