Update GPU Operator staging digest to sha256:a2d5ce3049990e195fce8b945827cdefdb924353af4b1ab5e9cd57fab54cf75d #61
Conversation
![red-hat-konflux[bot]](https://avatars.githubusercontent.com/in/296509?s=60&v=4){kind=small}
…5827cdefdb924353af4b1ab5e9cd57fab54cf75d Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a rh-ecosystem-edge member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
@red-hat-konflux[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
|
/hold @TomerNewman I think we can skip this if we test the PRs that update OpenShift versions. Also, can we limit the main branch tests to one, maybe two OpenShift versions? It will change frequently, and isn't a production version, so I think a quick sanity check would suffice. |
|
/uncc @fabiendupont |
openshift-ci
bot
requested review from
TomerNewman
and removed request for
fabiendupont
|
@TomerNewman I mean we can skip this PR as the same combination of bundle + OpenShift version will be already tested by the other red-hat-konflux bot PRs. My comment about OpenShift versions is related to the fact that the bundle will change often, and we only want to make sure it's not completely broken. So I think we need to test it only on - let's say - 4.18 and 4.12, instead of all versions: A release will have to pass through more comprehensive tests though, on all supported versions of OpenShift. |
|
/hold |
|
/unhold |
This PR contains the following updates:
3e44858->a2d5ce3/test 4.12-stable-nvidia-gpu-operator-e2e-master 4.14-stable-nvidia-gpu-operator-e2e-master 4.15-stable-nvidia-gpu-operator-e2e-master 4.16-stable-nvidia-gpu-operator-e2e-master 4.17-stable-nvidia-gpu-operator-e2e-master 4.18-stable-nvidia-gpu-operator-e2e-master
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).