Bug 2229903 - Mechanism to create configmaps under appropriate namespace based on tektonPipelinesNamespace & tektonTasksNamespace
Summary: Mechanism to create configmaps under appropriate namespace based on tektonPip...
Keywords:
Status: POST
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 4.14.0
Assignee: Karel Šimon
QA Contact: Ying Cui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-08 07:10 UTC by Geetika Kapoor
Modified: 2023-08-08 13:04 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt ssp-operator pull 646 0 None open feat: replace namespace of configMaps and roleBindings 2023-08-08 13:04:02 UTC
Red Hat Issue Tracker CNV-31858 0 None None None 2023-08-08 07:13:44 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.