Bug 2229903

Summary:	Mechanism to create configmaps under appropriate namespace based on tektonPipelinesNamespace & tektonTasksNamespace
Product:	Container Native Virtualization (CNV)	Reporter:	Geetika Kapoor <gkapoor>
Component:	Infrastructure	Assignee:	Karel Šimon <ksimon>
Status:	POST ---	QA Contact:	Ying Cui <ycui>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	4.14.0
Target Milestone:	---
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Geetika Kapoor 2023-08-08 07:10:07 UTC

Description of problem:

In HCO, there are two fields:
tektonPipelinesNamespace: test-01
tektonTasksNamespace: test-01
If i enable them then pipelines will get created under test-01 namespace and also all the rbac and rolebindings are set up for test-01. Having configmaps under these custom namespace seems to be more useful and logical because by setting this user intend to use test-01. Currently, they are getting created under openshift-virtualization-os-images.

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

How reproducible:
always 

Steps to Reproduce:
1.add above mentioned fields in HCO under spec.
2. save and see if test-01 has pipelines created and rbac.
3.

Actual results:
configmaps still created under openshift-virtualization-os-images.

Expected results:
configmaps  should be created based on fields tektonPipelinesNamespace and tektonTasksNamespace

Additional info: