Created attachment 1692957 [details] bug screenshot Description of problem: Create a OpenShift Serverless Operator, then go to create Knative Eventing and check the creation page. Under Registry there is a message for registry form but should not be a super link. Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-27-202943 How reproducible: Always Steps to Reproduce: 1. Create a OpenShift Serverless Operator, then go to Knative Eventing creation page 2. Expand Registry form field and check the helper message. example-registry.io/custom/path/${NAME}:custom-tag Actual results: Message contains a super link with "example-registry.io/custom/path/${NAME}:custom-tag" Expected results: "example-registry.io/custom/path/${NAME}:custom-tag" should not be a super link. Additional info: Also the super link in the right-side panel: Schema > spec > registry
I believe knative belongs to dev console.
Moving to management console because this looks like an issue with the form generation.
Working on PR feedback. Should be ready to merge first thing next sprint.
`registry.io/custom/path/${NAME}:custom-tag` is not a super link now. Verified on 4.6.0-0.nightly-2020-07-25-091217
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196