Bug 1858422 - "Custom Resource Definitions" page use `apiextensions.k8s.io/v1beta1` API while "Search" page use `apiextensions.k8s.io/v1beta1` API for CRD
Summary: "Custom Resource Definitions" page use `apiextensions.k8s.io/v1beta1` API whi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-17 21:35 UTC by tony.wu
Modified: 2020-10-27 16:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:15:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6302 0 None closed Bug 1858422: update CRD apiVersion to v1 2020-08-24 07:41:27 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:16:18 UTC

Description tony.wu 2020-07-17 21:35:32 UTC
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:

Comment 1 Joe Caiani 2020-07-31 20:31:11 UTC
looking into this for upcoming sprint. need to change the model to update to v1 and see if there is an api impact

Comment 4 Yadan Pei 2020-08-26 09:51:47 UTC
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

Comment 6 errata-xmlrpc 2020-10-27 16:15:58 UTC
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


Note You need to log in before you can comment on or make changes to this bug.