-
Notifications
You must be signed in to change notification settings - Fork 71
OPECO-3066: Synchronize From Upstream Repositories #606
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
OPECO-3066: Synchronize From Upstream Repositories #606
Conversation
@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-ecosystem. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: openshift-bot 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 |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: openshift-bot 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 |
We broke cluster bootstrap with RBAC? @awgreene |
7508f37
to
be1af2a
Compare
/lgtm |
sippy panic or something? /retest |
be1af2a
to
e54e97c
Compare
/lgtm |
/label acknowledge-critical-fixes-only No docs impacts, indicated by |
Discussed with @stevekuznetsov @grokspawn @dtfranz @awgreene and 👍 to merging now |
@openshift-bot: 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 kubernetes/test-infra repository. |
FFS please merge |
Signed-off-by: Steve Kuznetsov <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 7d4f29f923579a3b2363dd031c724139b88b8100
Signed-off-by: Steve Kuznetsov <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3ca07184d743816796af94f66ccdb9c3fd0b44d1
Signed-off-by: Jordan Keister <[email protected]> Upstream-repository: operator-registry Upstream-commit: f7c6429a51fcfd3c27f1e340a81c622c8429b716
Signed-off-by: guoguangwu <[email protected]> Upstream-repository: operator-registry Upstream-commit: 6cb25c26756c4eeadd29a43ffc4d45cd43159e4e
…ndle). (openshift#307) Signed-off-by: dtfranz <[email protected]> Upstream-repository: api Upstream-commit: 047dce1d23b997e02349c97c38733c8ab047aabe
e54e97c
to
90de9ff
Compare
/lgtm |
@openshift-bot: 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/test-infra repository. I understand the commands that are listed here. |
[ART PR BUILD NOTIFIER] This PR has been included in build operator-registry-container-v4.15.0-202311150532.p0.ge7e63bc.assembly.stream for distgit operator-registry. |
[ART PR BUILD NOTIFIER] This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202311150532.p0.ge7e63bc.assembly.stream for distgit operator-lifecycle-manager. |
/retitle OPECO-3066: Synchronize From Upstream Repositories |
The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:
This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.
/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem