CMP-3405: Update seccompprofile and seclinuxprofile related commands as both CRD scope… #98326
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@xiaojiey: This pull request references OSDOCS-15847 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.20.0" version, but no target version was set. 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. |
openshift-ci
bot
added
the
size/M
xiaojiey
changed the title
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. 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. |
…s are cluster wide now
xiaojiey
force-pushed
the
spo-cr-scope
branch
from
232d775 to
eb59c94
Compare
|
@xiaojiey: all tests passed! 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. |
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. 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. |
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. 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. |
xiaojiey
changed the title
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. 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. |
|
@yuumasato @rhmdnd @Vincent056 @Anna-Koudelkova Could you please help to review? Thanks. |
|
/label qe-approved |
openshift-ci
bot
added
the
qe-approved
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. 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. |
|
@xiaojiey: This pull request references CMP-3405 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. 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. |
bscott-rh
added
the
merge-review-in-progress
bscott-rh
added
branch/enterprise-4.14
branch/enterprise-4.15
branch/enterprise-4.16
branch/enterprise-4.17
branch/enterprise-4.18
branch/enterprise-4.19
and removed
merge-review-in-progress
|
Cherrypicking to 4.14+ per James Brigman in Slack. |
|
/cherrypick enterprise-4.14 |
|
@bscott-rh: new pull request created: #99084 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99085 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99086 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99087 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99088 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99089 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-sigs/prow repository. |
|
@bscott-rh: new pull request created: #99090 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-sigs/prow repository. |
8 participants
… are cluster wide now
Version(s):
SPOv0.9.0
Issue:
In PR kubernetes-sigs/security-profiles-operator#2735, the security profiles CRDs scope has been updated to cluster wide. In this PR, the security profiles related commands are updated accordingly.
Link to docs preview:
QE review:
Additional information: