Bug 1928932 - deploy/route_crd.yaml in openshift/router uses deprecated v1beta1 CRD API [NEEDINFO]
Summary: deploy/route_crd.yaml in openshift/router uses deprecated v1beta1 CRD API
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Ryan Fredette
QA Contact: Shudi Li
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-15 19:56 UTC by Ryan Fredette
Modified: 2022-08-10 10:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:35:38 UTC
Target Upstream Version:
chernand: needinfo? (mmasters)

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift router pull 349 0 None Merged Bug 1928932: Update deploy manifests to use stable apis 2022-03-02 17:45:10 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:36:00 UTC

Description Ryan Fredette 2021-02-15 19:56:26 UTC
Description of problem: the v1beta1 version of CustomResourceDefinition is being removed in k8s 1.22, in favor of the v1 version of the API.

deploy/route_crd.yaml in the openshift/router repo still uses the v1beta1 version and should be updated

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Stephen Greene 2021-04-29 20:54:48 UTC
Can we just delete https://github.com/openshift/router/tree/master/deploy from the router repo?

I don't think anything actually uses those files. They were added way back in https://github.com/openshift/router/pull/1. I'm not sure what they are for, to be honest.

Comment 13 errata-xmlrpc 2022-08-10 10:35:38 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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