-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
True
-
CLOSED
-
Green
-
-
No
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
- external trackers