Repository navigation
Replies: 1 comment 4 replies
|
Tekton Pipeline doesn't set What you're seeing comes from the base container images themselves. Tekton's internal images (entrypoint, workingdirinit, place-scripts init container, etc.) are built on On full OpenShift, the Pipelines Operator handles SCC compatibility for you. On MicroShift without the operator, you'd need to either:
The |
Uh oh!
There was an error while loading. Please reload this page.
Dear all,
I am currently doing Tekton Pipelines "the hard way", as I am evaluating MicroShift. This is almost like OpenShift, but is different in some aspects. One of them is that there are no Operators provided by RedHat, which means I have to install Tekton Pipelines manually.
I got that working with a lot of fiddling (patching the release.yaml via kustomize in ArgoCD to remove things like
runAsUserorrunAsGroup).I can create Tasks, TaskRuns, Pipelines and PipelineRuns, but unfortunately somewhere there is a default for the
podTemplatethat does not work on MicroShift. MicroShift has the SCC just like regular OpenShift, which means I have to "unset" / "undefine" things in thesecurityContextas usual.The configMap
config-defaultsdoes not contain adefault-pod-templatesection, so this seems to come from within the Tekton installation. As this is working on a regular OpenShift cluster, something apparently is being done differently under the hood.Does anyone have any pointers for me, where that might be? Is this something that RedHat did in its OpenShift Pipelines Operator?
Or, to rephrase the question:
Is is possible to "unset" things via the
podTemplatein a PipelineRun? I.e. I do not want to set a specific user inRunAsUser, I want that field to be removed / unset...Kind Regards,
Johannes
All reactions