[DNM] [TEST ONLY] fix: add FSGroup to Tekton PipelineRun podTemplate for s390x/ppc64le#1508
Open
matejvasek wants to merge 2 commits into
Open
[DNM] [TEST ONLY] fix: add FSGroup to Tekton PipelineRun podTemplate for s390x/ppc64le#1508matejvasek wants to merge 2 commits into
matejvasek wants to merge 2 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matejvasek The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Collaborator
Author
|
/test 420-unit |
Collaborator
Author
|
/test 420-e2e-oncluster-test |
Collaborator
Author
|
/test 420-images |
Collaborator
Author
|
/test 420-e2e-oncluster-test |
serverless-qe
force-pushed
the
release-next
branch
from
f332406 to
2b6117b
Compare
…support Fixes knative#3515 Remote Quarkus builds were failing on s390x and ppc64le clusters due to FSGroup permissions not being honored on the build PersistentVolume. This fix adds a podTemplate with securityContext (including fsGroup) to both Pack and S2I PipelineRun templates. This ensures all Tekton task pods inherit proper security context for volume access on architectures where FSGroup permissions need explicit configuration. Changes: - Add podTemplate with securityContext to packRunTemplate - Add podTemplate with securityContext to packRunTemplatePAC - Add podTemplate with securityContext to s2iRunTemplate - Add podTemplate with securityContext to s2iRunTemplatePAC - Add test to verify podTemplate with securityContext is present Security context values: - runAsUser: 1001 (matches Tekton buildpack task) - runAsGroup: 0 (matches Tekton buildpack task) - fsGroup: 1002 (ensures volume ownership for non-root users)
serverless-qe
force-pushed
the
release-next
branch
8 times, most recently
from
f8a3e43 to
a01b87d
Compare
serverless-qe
force-pushed
the
release-next
branch
from
a01b87d to
1f49ded
Compare
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
serverless-qe
force-pushed
the
release-next
branch
6 times, most recently
from
3d9c8ce to
95363cd
Compare
serverless-qe
force-pushed
the
release-next
branch
8 times, most recently
from
9348f58 to
c003db1
Compare
serverless-qe
force-pushed
the
release-next
branch
7 times, most recently
from
9750b30 to
5090a1e
Compare
serverless-qe
force-pushed
the
release-next
branch
8 times, most recently
from
8ed9577 to
0f0fc35
Compare
serverless-qe
force-pushed
the
release-next
branch
2 times, most recently
from
bf712f1 to
af6aa72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.