Skip to content

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04#6812

Merged
openshift-merge-bot[bot] merged 7 commits into
openshift:mainfrom
pacevedom:rebase-rebase-93e835e2a-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04
Jun 5, 2026
Merged

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04#6812
openshift-merge-bot[bot] merged 7 commits into
openshift:mainfrom
pacevedom:rebase-rebase-93e835e2a-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04-5.0.0-0.nightly-2026-06-04-190102_amd64-2026-06-04_arm64-2026-06-04

Conversation

@pacevedom

@pacevedom pacevedom commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores

    • Updated to newer nightly build versions (June 4, 2026) for both aarch64 and x86_64 architectures
    • Refreshed container image digests for core components including CLI, DNS, routing, OLM, and Multus
  • New Features

    • DNS daemonset now supports dynamic resource request and limit configuration through template values
  • Bug Fixes

    • Improved Route CRD TLS validation rule ordering for clearer error handling

@openshift-ci-robot

Copy link
Copy Markdown

@pacevedom: This pull request explicitly references no jira issue.

Details

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 5, 2026
@coderabbitai

coderabbitai Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

This PR bumps the OpenShift nightly build version from 2026-05-27 to 2026-06-04 across both x86_64 and aarch64 architectures. Version variables, release manifest base identifiers, component image digests (Multus, OLM, core services), CRI-O pause image pins, and build automation metadata are all updated to pin the newer nightly build artifacts.

Changes

Nightly Build Update

Layer / File(s) Summary
Version and release base updates
Makefile.version.aarch64.var, Makefile.version.x86_64.var, scripts/auto-rebase/last_rebase.sh
OCP_VERSION variables and last-rebase invocation arguments are updated to the 2026-06-04 nightly identifiers for both architectures.
Multus component image updates
assets/components/multus/kustomization.aarch64.yaml, assets/components/multus/kustomization.x86_64.yaml, assets/components/multus/release-multus-aarch64.json, assets/components/multus/release-multus-x86_64.json
Kustomization image overrides and release manifest digests for multus-cni-microshift and containernetworking-plugins-microshift are refreshed to new ocp-v5.0-art-dev SHA256 values.
OLM component image updates
assets/optional/operator-lifecycle-manager/kustomization.aarch64.yaml, assets/optional/operator-lifecycle-manager/kustomization.x86_64.yaml, assets/optional/operator-lifecycle-manager/release-olm-aarch64.json, assets/optional/operator-lifecycle-manager/release-olm-x86_64.json
Image digests for operator-lifecycle-manager, operator-registry, and kube-rbac-proxy are updated in kustomization files (including JSON6902 patch environment variables) and release manifests.
Core release manifests
assets/release/release-aarch64.json, assets/release/release-x86_64.json
Release base version and image digests for cli, coredns, haproxy-router, kube-rbac-proxy, ovn-kubernetes-microshift, pod, service-ca-operator, and csi-snapshot-controller are pinned to new nightly build digests; lvms_operator remains unchanged.
CRI-O container runtime configuration
packaging/crio.conf.d/10-microshift_amd64.conf, packaging/crio.conf.d/10-microshift_arm64.conf
Pause image references are updated to new nightly build digests.
Route CRD schema and build automation updates
assets/crd/route.crd.yaml, scripts/auto-rebase/commits.txt, scripts/auto-rebase/manifests_patches/020-dns-daemonset-resources.patch
Route CRD TLS validation rules are reordered; build metadata (embedded-component and image commit IDs) is updated; DNS daemonset resources now render dynamically from .DNSRequests and .DNSLimits template values.

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: a rebase/release update to nightly version 2026-06-04-190102 for both amd64 and arm64 architectures, which is reflected in the file updates throughout the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed No Go test files with Ginkgo tests were modified in this PR. The PR updates build configuration, manifests, and version files only, making this check inapplicable.
Test Structure And Quality ✅ Passed PR contains no Ginkgo test files (*_test.go). The check requires reviewing Ginkgo test code, which is not present in this rebase/release configuration update PR.
Microshift Test Compatibility ✅ Passed PR contains no new Ginkgo e2e tests. Changes are limited to version updates, image digests, manifests, configs, and patches - no test code added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR contains no new Ginkgo e2e tests; changes are version/digest updates and manifest patches only.
Topology-Aware Scheduling Compatibility ✅ Passed PR only updates versions, image digests, and templating. No topology-unaware scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR only modifies config/metadata files (YAML, JSON, Makefiles, scripts, patches). No Go source files or test binaries changed, so OTE stdout contract cannot be violated.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No new Ginkgo e2e tests added. This PR is a rebase/release update with manifest and config changes only. Unit tests added use testify, not Ginkgo.
No-Weak-Crypto ✅ Passed No weak cryptography (MD5, SHA1, DES, RC4, Blowfish, ECB) or custom crypto implementations detected. PR only updates versions and image digests.
Container-Privileges ✅ Passed No container privilege escalation settings (privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation) were added in this rebase/release update PR.
No-Sensitive-Data-In-Logs ✅ Passed PR contains only configuration, manifest, and data file updates with no new logging code or sensitive data exposed in logs.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from ggiguash and vanhalenar June 5, 2026 10:07
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2026
@ggiguash

ggiguash commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 5, 2026
@openshift-ci

openshift-ci Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, 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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/auto-rebase/manifests_patches/020-dns-daemonset-resources.patch`:
- Around line 14-19: Remove the conditional that omits the limits block so the
DaemonSet always contains resources.limits; in the template around the "limits:"
line (where it currently checks "{{- if .DNSLimits }}" and ranges "{{- range
$key, $value := .DNSLimits }}"), make the "limits:" stanza unconditional and
either iterate .DNSLimits if present or emit a deterministic fallback (e.g.,
default cpu and memory values) so resources.limits is always rendered for the
DNS container.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 5d1fe5bf-7554-448b-b705-c6434a673344

📥 Commits

Reviewing files that changed from the base of the PR and between 93e835e and ca39b9c.

⛔ Files ignored due to path filters (2)
  • etcd/vendor/github.com/openshift/microshift/pkg/config/config.go is excluded by !**/vendor/**
  • etcd/vendor/github.com/openshift/microshift/pkg/config/dns.go is excluded by !**/vendor/**
📒 Files selected for processing (19)
  • Makefile.version.aarch64.var
  • Makefile.version.x86_64.var
  • assets/components/multus/kustomization.aarch64.yaml
  • assets/components/multus/kustomization.x86_64.yaml
  • assets/components/multus/release-multus-aarch64.json
  • assets/components/multus/release-multus-x86_64.json
  • assets/crd/route.crd.yaml
  • assets/optional/operator-lifecycle-manager/kustomization.aarch64.yaml
  • assets/optional/operator-lifecycle-manager/kustomization.x86_64.yaml
  • assets/optional/operator-lifecycle-manager/release-olm-aarch64.json
  • assets/optional/operator-lifecycle-manager/release-olm-x86_64.json
  • assets/release/release-aarch64.json
  • assets/release/release-x86_64.json
  • packaging/crio.conf.d/10-microshift_amd64.conf
  • packaging/crio.conf.d/10-microshift_arm64.conf
  • scripts/auto-rebase/changelog.txt
  • scripts/auto-rebase/commits.txt
  • scripts/auto-rebase/last_rebase.sh
  • scripts/auto-rebase/manifests_patches/020-dns-daemonset-resources.patch
💤 Files with no reviewable changes (1)
  • scripts/auto-rebase/changelog.txt

@pacevedom

Copy link
Copy Markdown
Contributor Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

/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 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

@pacevedom: 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 ed34e7f into openshift:main Jun 5, 2026
17 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. lgtm Indicates that a PR is ready to be merged. 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