Description of problem: It's been noticed if searching CRD from the "Search" page, it gets the API from `apiextensions.k8s.io/v1` while from “Admin Nav Section” --> "Custom Resource Definitions" page, it shows the API from `apiextensions.k8s.io/v1beta1` Version-Release number of selected component (if applicable): 4.6.0-0.ci-2020-07-17-015005 How reproducible: 100% Steps to Reproduce: 1. Go to “Admin Nav Section” --> "Custom Resource Definitions" page, check any CRD YAML, see `apiVersion: apiextensions.k8s.io/v1beta1` 2. Go to "Search" page, select "CRD" in the Resource dropdown, check any CRD YAML, see `apiVersion: apiextensions.k8s.io/v1` Actual results: As mentioned above. Expected results: “Admin Nav Section” --> "Custom Resource Definitions" could be updated to `apiVersion: apiextensions.k8s.io/v1` as well. Additional info:
looking into this for upcoming sprint. need to change the model to update to v1 and see if there is an api impact
1. Goes to Administration -> Custom Resource Definition page, click on any CRD and check YAML, CRD apiVersion is apiextensions.k8s.io/v1 kind: CustomResourceDefinition apiVersion: apiextensions.k8s.io/v1 metadata: name: catalogsources.operators.coreos.com 2. on Home -> Search page, the CRD is searched with apiextensions.k8s.io/v1 too Verified on 4.6.0-0.nightly-2020-08-25-204643
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