This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2227950 - Document tekton resource creation under custom namespace
Summary: Document tekton resource creation under custom namespace
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Documentation
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.14.0
Assignee: Avital Pinnick
QA Contact: Oded Ramraz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-31 22:07 UTC by Geetika Kapoor
Modified: 2023-09-06 09:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-06 09:17:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt user-guide pull 712 0 None open feat: add paragraph about deploying tekton pipelines in different namespace 2023-09-06 07:00:10 UTC
Red Hat Issue Tracker   CNV-31571 0 None None None 2023-09-06 09:17:05 UTC

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

Comment 1 Dominik Holler 2023-09-06 09:11:57 UTC
Karel, thanks for the upstream change.
Using this bug to ensure that also the downstream doc is updated.


Note You need to log in before you can comment on or make changes to this bug.