Skip to content

Domunented changing the installation target namespace for pipelines. #64362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Domunented changing the installation target namespace for pipelines. #64362

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions cicd/pipelines/customizing-configurations-in-the-tektonconfig-cr.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ toc::[]

In {pipelines-title}, you can customize the following configurations by using the `TektonConfig` custom resource (CR):

* Changing the {pipelines-shortname} installation target namespace
* Configuring the {pipelines-title} control plane
* Changing the default service account
* Disabling the service monitor
Expand All @@ -22,6 +23,8 @@ In {pipelines-title}, you can customize the following configurations by using th

* You have installed the {pipelines-title} Operator.

include::modules/op-changing-pipelines-installation-target-namespace.adoc[leveloffset=+1]

include::modules/op-configuring-pipelines-control-plane.adoc[leveloffset=+1]

include::modules/op-modifiable-fields-with-default-values.adoc[leveloffset=+2]
Expand Down
32 changes: 32 additions & 0 deletions modules/op-changing-pipelines-installation-target-namespace.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
// This module is included in the following assembly:
//
// *openshift_pipelines/customizing-configurations-in-the-tektonconfig-cr.adoc

:_content-type: PROCEDURE
[id="op-changing-pipelines-installation-target-namespace_{context}"]
= Changing the {pipelines-shortname} installation target namespace

By default, the {pipelines-shortname} is installed in the `openshift-pipelines` namespace.
You can change the {pipelines-shortname} installation target namespace by editing the `targetNamespace` field in the specificaton of the `TektonConfig` custom resource (CR) to a custom namespace, for example `<my-custom-namespace>`. The {pipelines-shortname} installation is automatically moved to the new namespace specified.

.Example
[source,yaml]
----
apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
spec:
targetNamespace: <my-custom-namespace> <1>
----

<1> Replace the variable <my-custom-namespace> your defined target namespace.

[NOTE]
====
Setting `openshift-operators` namespace as targetNamespace is not allowed. You will get an error if you set `openshift-operators` as targetNamespace.
====

[WARNING]
====
when you change the target namespace, the previous namespace (`openshift-pipelines` by default) is reomved and all resources in it, including pipelines, tasks, secrets and so on, are lost.
====