Bug 2227950

Summary: Document tekton resource creation under custom namespace
Product: Container Native Virtualization (CNV) Reporter: Geetika Kapoor <gkapoor>
Component: InfrastructureAssignee: Dominik Holler <dholler>
Status: NEW --- QA Contact: Geetika Kapoor <gkapoor>
Severity: unspecified Docs Contact:
Priority: unspecified    
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-07-31 22:07:42 UTC 
Description of problem:

This is to track tekton resource creation under custom namespace. There are two possibilities:
1. Document steps needed to add tekton resources under custom namespace
2. Instead of user doing it manually we create a task that will pre-check and if missing create. 


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

How reproducible:
always

Steps to Reproduce:
1.Use a custom namespace during pipeline runs
2.
3.

Actual results:

Custom namespace works with some extra steps

Expected results:

Document how to work with custom namespaces.

Additional info:

How to do it : 
https://gitlab.cee.redhat.com/-/snippets/7023
Copy all needed config maps to custom namespace
for i in windows10-unattend windows10-bios-autounattend windows-sqlserver windows-vs-code windows11-unattend; do kubectl get configmap $i --namespace openshift-virtualization-os-images -o yaml |sed 's/namespace: openshift-virtualization-os-images/namespace: test-tekton-03/'|kubectl create -f -; done