Bug 1819288 - Drop ownership of kubernetes-nmstate CRDs
Summary: Drop ownership of kubernetes-nmstate CRDs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 2.3.0
Assignee: Petr Horáček
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-31 15:59 UTC by Petr Horáček
Modified: 2020-05-04 19:11 UTC (History)
3 users (show)

Fixed In Version: cluster-network-addons-operator-container-v2.3.0-27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 19:10:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt cluster-network-addons-operator pull 357 0 None closed don't remove CRDs when their comonents are gone 2020-08-19 12:18:06 UTC
Red Hat Product Errata RHEA-2020:2011 0 None None None 2020-05-04 19:10:59 UTC

Description Petr Horáček 2020-03-31 15:59:16 UTC 
Description of problem:
In the next version of CNV, the ownership of kubernetes-nmstate objects will be transferred to a different operator. In order to prepare for this change, we have to drop our own ownerships now.

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

How reproducible:
Always

Steps to Reproduce:
1. Deploy CNV
2. Check NodeNetworkConfigurationPolicy, NodeNetworkConfigurationEnactment and NodeNetworkState CRDs
3. See their ownershipReference

Actual results:
They are bound to NetworkAddonsConfig.

Expected results:
There should be no ownership reference.
Comment 4 errata-xmlrpc 2020-05-04 19:10: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, 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/RHEA-2020:2011
Note You need to log in before you can comment on or make changes to this bug.