Skip to content

NO-ISSUE: rebase-release-4.21-4.21.0-0.nightly-2026-03-11-185944_amd64-2026-03-11_arm64-2026-03-14#6357

Merged
openshift-merge-bot[bot] merged 6 commits intorelease-4.21from
rebase-release-4.21-4.21.0-0.nightly-2026-03-11-185944_amd64-2026-03-11_arm64-2026-03-14
Mar 16, 2026
Merged

NO-ISSUE: rebase-release-4.21-4.21.0-0.nightly-2026-03-11-185944_amd64-2026-03-11_arm64-2026-03-14#6357
openshift-merge-bot[bot] merged 6 commits intorelease-4.21from
rebase-release-4.21-4.21.0-0.nightly-2026-03-11-185944_amd64-2026-03-11_arm64-2026-03-14

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.21.0-0.nightly-2026-03-11-185944
arm64: 4.21.0-0.nightly-arm64-2026-03-14-053350
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/2033393022992912384

  • kubernetes image-arm64 1dcb406c2ca2033c3a01617372afbfe8bf09ac71 to 8b1d67b459cd554cd4b6d878e9bf4d425b3bf9a0
    • dc33209f7 2026-02-27T11:26:39-05:00 UPSTREAM: : hack/update-vendor.sh, make update and update image
    • ebfac0573 2026-02-26T20:03:29Z Release commit for Kubernetes v1.34.5
    • f3b756a0c 2026-02-12T14:11:01+01:00 Bump images and versions to go 1.24.13 and distroless iptables
    • 9b1432f35 2026-02-10T13:04:54Z Update CHANGELOG/CHANGELOG-1.34.md for v1.34.4

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

@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 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.21.0-0.nightly-2026-03-11-185944
arm64: 4.21.0-0.nightly-arm64-2026-03-14-053350
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/2033393022992912384

  • kubernetes image-arm64 1dcb406c2ca2033c3a01617372afbfe8bf09ac71 to 8b1d67b459cd554cd4b6d878e9bf4d425b3bf9a0
  • dc33209f7 2026-02-27T11:26:39-05:00 UPSTREAM: : hack/update-vendor.sh, make update and update image
  • ebfac0573 2026-02-26T20:03:29Z Release commit for Kubernetes v1.34.5
  • f3b756a0c 2026-02-12T14:11:01+01:00 Bump images and versions to go 1.24.13 and distroless iptables
  • 9b1432f35 2026-02-10T13:04:54Z Update CHANGELOG/CHANGELOG-1.34.md for v1.34.4

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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 tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 16, 2026
@openshift-ci openshift-ci bot requested review from eslutsky and jogeo March 16, 2026 04:24
@pacevedom
Copy link
Copy Markdown
Contributor

/approve
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/approve
/verified by CI

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2026
@copejon
Copy link
Copy Markdown
Contributor

copejon commented Mar 16, 2026

/lgtm

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

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, microshift-rebase-script[bot], pacevedom

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-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 16, 2026

@microshift-rebase-script[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.

@openshift-merge-bot openshift-merge-bot bot merged commit 0e4f859 into release-4.21 Mar 16, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.21-4.21.0-0.nightly-2026-03-11-185944_amd64-2026-03-11_arm64-2026-03-14 branch March 16, 2026 17:10
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants