You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenShift has extra security features which prevent most service accounts from creating privileged pods, containers that run as uid 0, and so forth. Because of the way Tekton currently checks permissions when creating TaskRun objects, the Tekton controller needs elevated privileges that are specific to OpenShift to create build runs with most of our sample build strategies.
There are a few approaches we can take (not mutually exclusive):
Augment our install-tekton.sh script to add the right roles and role bindings for OpenShift. Ex: install-tekton.sh openshift adds the extra logic.
Instruct users and contributors to install the OpenShift Pipelines operator via Operator Hub in the web console.
Add a script that installs the OpenShift Pipelines operator via the command line.
@gabemontero is separately working with upstream Tekton to remove this limitation.
The text was updated successfully, but these errors were encountered:
adambkaplan
added
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
and removed
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
labels
Sep 2, 2020
adambkaplan
changed the title
Add elevated security permissions for the Tekton deployment script on OpenShift
Add elevated security permissions to the Tekton deployment script for OpenShift
Sep 2, 2020
When deploying Tekton on openshift, grant the tekton-pipelines-
controller use of the priveleged security context constraint. This
will let the Tekton controller create privileged containers. Build
strategies such as buildah currently require use of the priveleged SCC.
Fixesshipwright-io#378
When deploying Tekton on openshift, grant the tekton-pipelines-
controller use of the priveleged security context constraint. This
will let the Tekton controller create privileged containers. Build
strategies such as buildah currently require use of the priveleged SCC.
Fixesshipwright-io#378
OpenShift has extra security features which prevent most service accounts from creating privileged pods, containers that run as uid 0, and so forth. Because of the way Tekton currently checks permissions when creating
TaskRun
objects, the Tekton controller needs elevated privileges that are specific to OpenShift to create build runs with most of our sample build strategies.There are a few approaches we can take (not mutually exclusive):
install-tekton.sh
script to add the right roles and role bindings for OpenShift. Ex:install-tekton.sh openshift
adds the extra logic.@gabemontero is separately working with upstream Tekton to remove this limitation.
The text was updated successfully, but these errors were encountered: