Skip to content

Commit dac99ee

Browse files
authored
Merge pull request #40749 from sounix000/3304-default-pipeline-SA
RHDEVDOCS-3304 Document disabling the default pipelines SA
2 parents b94c971 + f660a4c commit dac99ee

File tree

2 files changed

+45
-1
lines changed

2 files changed

+45
-1
lines changed

cicd/pipelines/installing-pipelines.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
[role="_abstract"]
910
This guide walks cluster administrators through the process of installing the {pipelines-title} Operator to an {product-title} cluster.
1011

1112
// Prerequisites for installing OpenShift Operator
@@ -36,13 +37,17 @@ include::modules/op-installing-pipelines-operator-using-the-cli.adoc[leveloffset
3637

3738
include::modules/op-pipelines-operator-in-restricted-environment.adoc[leveloffset=+1]
3839

40+
// Disabling automatic creation of RBAC resources
41+
42+
include::modules/op-disabling-automatic-creation-of-rbac-resources.adoc[leveloffset=+1]
43+
3944

4045
[role="_additional-resources"]
4146
== Additional resources
4247

4348
* You can learn more about installing Operators on {product-title} in the xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-adding-operators-to-a-cluster[adding Operators to a cluster] section.
4449

45-
* For more information on using pipelines in a restricted environment see:
50+
* For more information on using pipelines in a restricted environment, see:
4651

4752
** xref:../../cicd/pipelines/creating-applications-with-cicd-pipelines.html#op-mirroring-images-to-run-pipelines-in-restricted-environment_creating-applications-with-cicd-pipelines[Mirroring images to run pipelines in a restricted environment]
4853

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
// Module included in the following assemblies:
2+
//
3+
// */openshift_pipelines/installing-pipelines.adoc
4+
:_content-type: CONCEPT
5+
[id="op-disabling-automatic-creation-of-rbac-resources_{context}"]
6+
= Disabling the automatic creation of RBAC resources
7+
8+
[role="_abstract"]
9+
The default installation of the {pipelines-title} Operator creates multiple role-based access control (RBAC) resources for all namespaces in the cluster, except the namespaces matching the `^(openshift|kube)-*` regular expression pattern. Among these RBAC resources, the `pipelines-scc-rolebinding` security context constraint (SCC) role binding resource is a potential security issue, because the associated `pipelines-scc` SCC has the `RunAsAny` privilege.
10+
11+
To disable the automatic creation of cluster-wide RBAC resources after the {pipelines-title} Operator is installed, cluster administrators can set the `createRbacResource` parameter to `false` in the cluster-level `TektonConfig` custom resource (CR).
12+
13+
.Example `TektonConfig` CR
14+
[source,yaml]
15+
----
16+
apiVersion: operator.tekton.dev/v1alpha1
17+
kind: TektonConfig
18+
metadata:
19+
name: config
20+
spec:
21+
params:
22+
- name: createRbacResource
23+
value: "false"
24+
profile: all
25+
targetNamespace: openshift-pipelines
26+
addon:
27+
params:
28+
- name: clusterTasks
29+
value: "true"
30+
- name: pipelineTemplates
31+
value: "true"
32+
...
33+
----
34+
35+
[WARNING]
36+
====
37+
As a cluster administrator or an user with appropriate privileges, when you disable the automatic creation of RBAC resources for all namespaces, the default `ClusterTask` resource does not work. For the `ClusterTask` resource to function, you must create the RBAC resources manually for each intended namespace.
38+
====
39+

0 commit comments

Comments
 (0)