-
Notifications
You must be signed in to change notification settings - Fork 60
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
NO-ISSUE: Synchronize From Upstream Repositories #742
Conversation
@perdasilva: 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. |
* update go.mod to go 1.22 * update Dockerfile to use go v1.22.2 Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> --------- Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 01d4a00cadfeb59d9023d0a05105b84c43e2bbde
…source pods (#3206) * Refactor security context configuration in pod reconciler This change updates the logic for setting security contexts within the OLM pod reconciler. Now, it differentiates between 'Restricted' and 'Legacy' security contexts more explicitly. The 'Restricted' security context applies default security settings unless overridden, while the 'Legacy' context clears all security settings. When no security context is configured, it defaults to restricted. Additionally, the related tests have been updated to reflect these changes and ensure correct behavior. Signed-off-by: btofel <btofel@redhat.com> * Add checking of the namespace PSA restrictions Signed-off-by: btofel <btofel@redhat.com> * Fix linter issues Signed-off-by: btofel <btofel@redhat.com> Signed-off-by: Brett Tofel <btofel@redhat.com> * fixes Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> --------- Signed-off-by: btofel <btofel@redhat.com> Signed-off-by: Brett Tofel <btofel@redhat.com> Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Brett Tofel <btofel@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9b2802151528e556d78b5fe55bcb8c89070efe58
… CRD specifies a conversion strategy (#3209) * warn but allow CRD upgrade when validations fail but new CRD has conversion strategy Signed-off-by: everettraven <everettraven@gmail.com> * unexport validationError Signed-off-by: everettraven <everettraven@gmail.com> * updating warning message to be more descriptive, add warning event on installplan Signed-off-by: everettraven <everettraven@gmail.com> * update warning templ per review comments Signed-off-by: everettraven <everettraven@gmail.com> --------- Signed-off-by: everettraven <everettraven@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: c3e17741c5dde8d67203a9e34bba81c4ad2bddcd
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 157af3287d4c3138c54d503838e13581d9ab4ea8
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: perdasilva 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 |
@perdasilva: The following tests 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/test-infra repository. I understand the commands that are listed here. |
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-ecosystemopenshift-bot:synchronize-upstreammastersynchronize-upstreamtrue &{0xc0003f6770 0xc00042f500 false {0 0} 0xc00042f4a0} [] true