Skip to content

NO-JIRA: Update instaslice-daemonset-next to 18e0dea#1029

Merged
openshift-merge-bot[bot] merged 1 commit intonextfrom
konflux/component-updates/instaslice-operator-next-component-update-instaslice-daemonset-next
Apr 2, 2026
Merged

NO-JIRA: Update instaslice-daemonset-next to 18e0dea#1029
openshift-merge-bot[bot] merged 1 commit intonextfrom
konflux/component-updates/instaslice-operator-next-component-update-instaslice-daemonset-next

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

@red-hat-konflux red-hat-konflux Bot commented Mar 20, 2026

Image created from 'https://github.com/openshift/instaslice-operator?rev=8e80e6c3b7b59ed785506ffce237bc8d81bd01bc'

This PR contains the following updates:

Package Update Change
quay.io/redhat-user-workloads/dynamicacceleratorsl-tenant/instaslice-daemonset-next digest 340da56 -> 18e0dea

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test

@red-hat-konflux red-hat-konflux Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. konflux-nudge lgtm Indicates that a PR is ready to be merged. labels Mar 20, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Image created from 'https://github.com/openshift/instaslice-operator?rev=7a006e407a09427fed322224ffca0bfb09749a63'

This PR contains the following updates:

Package Update Change
quay.io/redhat-user-workloads/dynamicacceleratorsl-tenant/instaslice-daemonset-next digest 340da56 -> 66bbaf4

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test

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 added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 20, 2026
@openshift-ci openshift-ci Bot requested review from empovit and mrunalp March 20, 2026 15:18
@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update instaslice-daemonset-next to 66bbaf4 NO-JIRA: Update instaslice-daemonset-next to 8622c43 Mar 21, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/component-updates/instaslice-operator-next-component-update-instaslice-daemonset-next branch from e6ac776 to 69eb64d Compare March 21, 2026 07:22
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 21, 2026
Copy link
Copy Markdown
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD e07a84d and 2 for PR HEAD 69eb64d in total

@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update instaslice-daemonset-next to 8622c43 NO-JIRA: Update instaslice-daemonset-next to 09b789d Mar 31, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/component-updates/instaslice-operator-next-component-update-instaslice-daemonset-next branch from 69eb64d to 4642476 Compare March 31, 2026 08:35
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2026
Image created from 'https://github.com/openshift/instaslice-operator?rev=8e80e6c3b7b59ed785506ffce237bc8d81bd01bc'

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update instaslice-daemonset-next to 09b789d NO-JIRA: Update instaslice-daemonset-next to 18e0dea Apr 2, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/component-updates/instaslice-operator-next-component-update-instaslice-daemonset-next branch from 4642476 to 69b9733 Compare April 2, 2026 07:46
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 2, 2026

@red-hat-konflux[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

Copy link
Copy Markdown
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: red-hat-konflux[bot], sairameshv

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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-merge-bot openshift-merge-bot Bot merged commit e9101a5 into next Apr 2, 2026
11 checks passed
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. konflux-nudge lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants