-
Notifications
You must be signed in to change notification settings - Fork 1.9k
NO-JIRA: add security test for karpenter-provider-aws #64815
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
base: master
Are you sure you want to change the base?
Conversation
I'm going through the threat assessment, and this is one of the things I know we're going to have to set up, so I'd rather set it up now so I can say "yes, it's already done" and know what the damage (if any) is than come back and set it up later.
@jkyros: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jkyros 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 |
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse pull-ci-openshift-aws-karpenter-provider-aws-main-security |
@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@jkyros: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
I'm going through the security threat assessment survey, and this is one of the things I know we're going to have to set up, so I'd rather set it up now so I can say "yes, it's already done" and know what the damage (if any) is rather than come back and set it up later.