Skip to content

Conversation

openshift-bot
Copy link

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2024-05-01 00:01:43 operator-framework/@a831774 dtfranz UPSTREAM: : Add OpenShift specific files
2024-05-01 00:01:43 operator-framework/@0b3cfdb Alexander Greene UPSTREAM: : Drop commitchecker
2024-05-01 00:01:43 operator-framework/@1ba4bc7 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml
2024-05-01 00:01:43 operator-framework/@30e85b0 Mikalai Radchuk UPSTREAM: : update owners
2024-05-01 00:01:43 operator-framework/@83def4d Brett Tofel UPSTREAM: : Add pointer to tooling README
2024-05-01 00:01:43 operator-framework/@11fd7e8 Mikalai Radchuk UPSTREAM: : Disable Validating Admission Policy APIs downstream
2024-05-01 00:01:43 operator-framework/@395fd76 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART for 4.16 Reconciling with https://github.com/openshift/ocp-build-data/tree/6250d54c4686a708ca5985afb73080e8ca9a1f7f/images/ose-olm-operator-controller.yml
2024-05-01 21:02:49 operator-framework/@bd56935 Mikalai Radchuk UPSTREAM: : Enable Validating Admission Policy APIs downstream
2024-05-02 15:56:24 operator-framework/@a1ca98e Ilias Rinis UPSTREAM: : manifests: set required-scc for openshift workloads

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

m1kola and others added 23 commits May 2, 2024 07:12
* Replace solver with simple catalog filtering

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>

* Remove solver leftovers

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>

---------

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
…s (#809)

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
It is an unused field.

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
E2E targets do not depend on envtest as they
use a real kind cluster.

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
… plain+v0 (#822)

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Due to the polling feature in the Catalog, the `lastPolledInterval` in the
Catalog's status gets updated. Because of this there is a reconcile is trigrred
every time the catalog is polled, even though there is no change in the
resolved image ref SHA.

This causes unnecessary continuous reconciles in the CE. To overcome this,
a Predicate is added to accept update events only when there is a change in
Resolved reference.

Signed-off-by: Varsha Prasad Narsing <varshaprasad96@gmail.com>
Bumps [pygments](https://github.com/pygments/pygments) from 2.17.2 to 2.18.0.
- [Release notes](https://github.com/pygments/pygments/releases)
- [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES)
- [Commits](pygments/pygments@2.17.2...2.18.0)

---
updated-dependencies:
- dependency-name: pygments
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [mkdocs-material](https://github.com/squidfunk/mkdocs-material) from 9.5.20 to 9.5.21.
- [Release notes](https://github.com/squidfunk/mkdocs-material/releases)
- [Changelog](https://github.com/squidfunk/mkdocs-material/blob/master/CHANGELOG)
- [Commits](squidfunk/mkdocs-material@9.5.20...9.5.21)

---
updated-dependencies:
- dependency-name: mkdocs-material
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.3 to 3.1.4.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst)
- [Commits](pallets/jinja@3.1.3...3.1.4)

---
updated-dependencies:
- dependency-name: jinja2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [babel](https://github.com/python-babel/babel) from 2.14.0 to 2.15.0.
- [Release notes](https://github.com/python-babel/babel/releases)
- [Changelog](https://github.com/python-babel/babel/blob/master/CHANGES.rst)
- [Commits](python-babel/babel@v2.14.0...v2.15.0)

---
updated-dependencies:
- dependency-name: babel
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Move SHELL definition ahead of any $(shell) use.

Signed-off-by: Todd Short <tshort@redhat.com>
Signed-off-by: yashoza19 <yoza@redhat.com>
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
Bumps [mkdocs-material](https://github.com/squidfunk/mkdocs-material) from 9.5.21 to 9.5.22.
- [Release notes](https://github.com/squidfunk/mkdocs-material/releases)
- [Changelog](https://github.com/squidfunk/mkdocs-material/blob/master/CHANGELOG)
- [Commits](squidfunk/mkdocs-material@9.5.21...9.5.22)

---
updated-dependencies:
- dependency-name: mkdocs-material
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [lxml](https://github.com/lxml/lxml) from 5.2.1 to 5.2.2.
- [Release notes](https://github.com/lxml/lxml/releases)
- [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt)
- [Commits](lxml/lxml@lxml-5.2.1...lxml-5.2.2)

---
updated-dependencies:
- dependency-name: lxml
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [regex](https://github.com/mrabarnett/mrab-regex) from 2024.4.28 to 2024.5.10.
- [Changelog](https://github.com/mrabarnett/mrab-regex/blob/hg/changelog.txt)
- [Commits](mrabarnett/mrab-regex@2024.4.28...2024.5.10)

---
updated-dependencies:
- dependency-name: regex
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
API servers can't guarantee uniqueness because they can handle
more than one concurrent request for the same resource and both
can be past admission but before storage.

There's also latency between creation and an update to the
binding's param informer. The problems gets worse in HA setups
when you have multiple kube-apiserver instances.

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
No bundles with webhooks are currently allowed
and we must be clearly indicated in the conditions
of `ClusterExtension`

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
@openshift-bot openshift-bot added tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 13, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2024
@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2024
@openshift-ci-robot
Copy link

@openshift-bot: This pull request explicitly references no jira issue.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2024-05-01 00:01:43 operator-framework/@a831774 dtfranz UPSTREAM: : Add OpenShift specific files
2024-05-01 00:01:43 operator-framework/@0b3cfdb Alexander Greene UPSTREAM: : Drop commitchecker
2024-05-01 00:01:43 operator-framework/@1ba4bc7 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml
2024-05-01 00:01:43 operator-framework/@30e85b0 Mikalai Radchuk UPSTREAM: : update owners
2024-05-01 00:01:43 operator-framework/@83def4d Brett Tofel UPSTREAM: : Add pointer to tooling README
2024-05-01 00:01:43 operator-framework/@11fd7e8 Mikalai Radchuk UPSTREAM: : Disable Validating Admission Policy APIs downstream
2024-05-01 00:01:43 operator-framework/@395fd76 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART for 4.16 Reconciling with https://github.com/openshift/ocp-build-data/tree/6250d54c4686a708ca5985afb73080e8ca9a1f7f/images/ose-olm-operator-controller.yml
2024-05-01 21:02:49 operator-framework/@bd56935 Mikalai Radchuk UPSTREAM: : Enable Validating Admission Policy APIs downstream
2024-05-02 15:56:24 operator-framework/@a1ca98e Ilias Rinis UPSTREAM: : manifests: set required-scc for openshift workloads

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

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 openshift-ci bot requested a review from a team May 13, 2024 15:59
Copy link
Contributor

openshift-ci bot commented May 13, 2024

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-runtime.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2024-05-01 00:01:43 operator-framework/@a831774 dtfranz UPSTREAM: : Add OpenShift specific files
2024-05-01 00:01:43 operator-framework/@0b3cfdb Alexander Greene UPSTREAM: : Drop commitchecker
2024-05-01 00:01:43 operator-framework/@1ba4bc7 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml
2024-05-01 00:01:43 operator-framework/@30e85b0 Mikalai Radchuk UPSTREAM: : update owners
2024-05-01 00:01:43 operator-framework/@83def4d Brett Tofel UPSTREAM: : Add pointer to tooling README
2024-05-01 00:01:43 operator-framework/@11fd7e8 Mikalai Radchuk UPSTREAM: : Disable Validating Admission Policy APIs downstream
2024-05-01 00:01:43 operator-framework/@395fd76 AOS Automation Release Team UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART for 4.16 Reconciling with https://github.com/openshift/ocp-build-data/tree/6250d54c4686a708ca5985afb73080e8ca9a1f7f/images/ose-olm-operator-controller.yml
2024-05-01 21:02:49 operator-framework/@bd56935 Mikalai Radchuk UPSTREAM: : Enable Validating Admission Policy APIs downstream
2024-05-02 15:56:24 operator-framework/@a1ca98e Ilias Rinis UPSTREAM: : manifests: set required-scc for openshift workloads

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

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.

Copy link
Contributor

openshift-ci bot commented May 13, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

1 similar comment
Copy link
Contributor

openshift-ci bot commented May 13, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a1ca98e and 2 for PR HEAD 5788986 in total

everettraven and others added 15 commits May 13, 2024 18:59
… (#852)

when unable to find docker or podman as this evaluation results in
an error in environments where docker or podman is not installed
even when using targets that do not require a container runtime

Signed-off-by: everettraven <everettraven@gmail.com>
Signed-off-by: dtfranz <dfranz@redhat.com>
Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
* Remove alumni from owners
* Add m1kola to approvers

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
* This reverts commit 3f079c4.
* Includes Validating Admission Policy manifests

Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
@openshift-bot openshift-bot force-pushed the synchronize-upstream branch from 5788986 to ee4f2d3 Compare May 14, 2024 00:03
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 14, 2024
Copy link
Contributor

openshift-ci bot commented May 14, 2024

@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-sigs/prow repository. I understand the commands that are listed here.

@everettraven
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 14, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 3c6254b into openshift:main May 14, 2024
@openshift-bot
Copy link
Author

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-olm-operator-controller-container-v4.16.0-202405141619.p0.g3c6254b.assembly.stream.el9 for distgit ose-olm-operator-controller.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.