- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.8k
Implement set-security-context feature for affinity assistant containers #8182
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.
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
Implement set-security-context feature for affinity assistant containers #8182
Conversation
| Hi @kristofferchr. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with  Once the patch is verified, the new status will be reflected by the  I understand the commands that are listed here. Instructions 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/test-infra repository. | 
| /kind feature | 
| The following is the coverage report on the affected files. 
 | 
d78fc27    to
    8c3d09f      
    Compare
  
    | The following is the coverage report on the affected files. 
 | 
8c3d09f    to
    d7d9791      
    Compare
  
    | @vdemeester is this /ok-to-test ? | 
| The following is the coverage report on the affected files. 
 | 
| /ok-to-test | 
| The following is the coverage report on the affected files. 
 | 
| /retest | 
| /lgtm | 
d7d9791    to
    1c07e21      
    Compare
  
    | The following is the coverage report on the affected files. 
 | 
| The following is the coverage report on the affected files. 
 | 
| @chitrangpatel this needs a new lgtm, had to rebase. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
| [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here 
Needs approval from an approver in each of these files:
 
 Approvers can indicate their approval by writing  | 
1c07e21    to
    2f787ae      
    Compare
  
    Ensures that when using Affinity Assistant, one can adhere to restricted pod security standards. Enables users to apply a container level securityContext for Affinity Assistants.
2f787ae    to
    3173496      
    Compare
  
    | The following is the coverage report on the affected files. 
 | 
| The following is the coverage report on the affected files. 
 | 
| The following is the coverage report on the affected files. 
 | 
| /test pull-tekton-pipeline-integration-tests | 
| /test pull-tekton-pipeline-beta-integration-tests | 
| /test pull-tekton-pipeline-go-coverage-df | 
| @kristofferchr: The specified target(s) for  
 The following commands are available to trigger optional jobs: 
 Use  In response to this: 
 Instructions 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/test-infra repository. | 
| @vdemeester need another /lgtm rebase changes again. | 
| The following is the coverage report on the affected files. 
 | 
| /lgtm | 
Solves #8181
Needed for this issue: #8183
Changes
Added container securityContext for affinity assistant when feature flag
set-security-contextis set to true.Implemented for both windows and linux OS. )
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes