Description of problem: KnativeServing link in Global Configuration is using obselete apiVersion which results in a 404 when legacy KnativeServing is not created. Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-02-05-220946 How reproducible: Always Steps to Reproduce: 1. install OpenShift Serverless Operator to all namespaces 2. create knative-serving namespace 3. Create Custom Resource 'Knative Serving' into 'knative-serving' project, a knative-serving instance can be succesfully created # oc get KnativeServing.operator.knative.dev -n knative-serving NAME VERSION READY REASON knative-serving 0.11.1 False NotReady 4. Visit Administration -> Cluster Settings -> Global Configuration -> click KnativeServing Actual results: 4. It reports 404 Not Found https://console-openshift-console.apps.qe-uiyapei44.qe.devcluster.openshift.com/k8s/ns/knative-serving/serving.knative.dev~v1alpha1~KnativeServing/knative-serving Expected results: 4. The correct URL to get KnativeServing is https://console-openshift-console.apps.qe-uiyapei44.qe.devcluster.openshift.com/k8s/ns/knative-serving/operator.knative.dev~v1alpha1~KnativeServing/knative-serving/yaml. From OpenShift Serverless Operator, it seems apiVersion serving.knative.dev/v1alpha1 is obselete Additional info:
Created attachment 1658138 [details] One Obselete and the other one
*** This bug has been marked as a duplicate of bug 1800598 ***