Skip to content

NE-2847: Bump kube-rbac-proxy, Bump operator version to 1.3.9 - #560

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
grzpiotrowski:kube-rbac-proxy-1-3-9-bump
Aug 25, 2026
Merged

openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
grzpiotrowski:kube-rbac-proxy-1-3-9-bump

Conversation

@grzpiotrowski

@grzpiotrowski grzpiotrowski commented Aug 24, 2026 •

Copy link
Copy Markdown
Contributor

Bumps kube-rbac-proxy to the latest v4.22 tag image:
https://catalog.redhat.com/en/software/containers/openshift4/ose-kube-rbac-proxy-rhel9/652809a5244cb343fb4a4b66?image=6a8440ea5bb0a84dedb3d79a
as a regular maintenance coming up for the next 1.3 release.

Increments the operator version to v1.3.9 in VERSION file, then run:
./hack/sync-version.sh
make bundle

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

openshift-ci-robot commented Aug 24, 2026 •

Copy link
Copy Markdown

@grzpiotrowski: This pull request references NE-2847 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Bumps kube-rbac-proxy to the latest v4.22 tag image:
https://catalog.redhat.com/en/software/containers/openshift4/ose-kube-rbac-proxy-rhel9/652809a5244cb343fb4a4b66?image=6a8440ea5bb0a84dedb3d79a
as a regular maintenance coming up for the next 1.3 release.

Increments the operator version to v1.3.9.

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.

@coderabbitai

coderabbitai Bot commented Aug 24, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: b6e8fcc8-8ee0-41ed-af67-b3d685cdb54c

📥 Commits

Reviewing files that changed from the base of the PR and between 7161b9f and 33c7c2b.

📒 Files selected for processing (4)
  • Containerfile.external-dns-operator
  • Containerfile.external-dns-operator-bundle
  • VERSION
  • bundle-hack/container_digest.sh

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The release version changes from 1.3.8 to 1.3.9 in the VERSION file and operator container metadata. The bundle version and release labels also change to 1.3.9. The pinned kube-rbac-proxy image changes from the v4.19 digest to the v4.22 digest, with its version comment and catalog URL refreshed.

Suggested reviewers: alebedev87

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed Docstring check was indeterminate for this PR — some files could not be analyzed in time. Not blocking.
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 The PR changes only container labels, VERSION, and an image digest script; it adds or modifies no Ginkgo test titles or dynamic test-name values.
Test Structure And Quality ✅ Passed The PR changes only container labels, VERSION, and an image digest; no Ginkgo test files or test code changed, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The pull-request diff changes only container labels, VERSION, and an image digest; it adds no Ginkgo e2e tests or MicroShift-sensitive test behavior.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only two Containerfiles, VERSION, and bundle-hack/container_digest.sh; no Ginkgo e2e tests or test declarations were added.
Topology-Aware Scheduling Compatibility ✅ Passed The PR diff only changes image/version labels and the kube-rbac-proxy pullspec; it adds no topology, affinity, selector, toleration, replica, spread, or PDB scheduling constraint.
Ote Binary Stdout Contract ✅ Passed The PR changes only image/version labels and a kube-rbac-proxy digest; no OTE binary or process-level stdout write changes are present.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes only image/version metadata and a kube-rbac-proxy digest; no Ginkgo e2e tests or test code were added or modified.
No-Weak-Crypto ✅ Passed The PR adds only version labels, a version value, and a SHA256 image digest; no weak-crypto or secret-comparison code is introduced. Existing sha1sum drift checks are unchanged.
Container-Privileges ✅ Passed The PR changes only image/version labels and a pull-spec; manifests retain runAsNonRoot=true, privileged=false, and allowPrivilegeEscalation=false, with no prohibited host settings or SYS_ADMIN.
No-Sensitive-Data-In-Logs ✅ Passed The PR adds only version labels, a version value, and a public image digest/catalog link; it introduces no logging or sensitive-data output.
Title check ✅ Passed The title clearly identifies both primary changes: the kube-rbac-proxy update and the operator version increment to 1.3.9.
Description check ✅ Passed The description accurately explains the kube-rbac-proxy update, operator version increment, and related maintenance commands.
✨ 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.

@openshift-ci
openshift-ci Bot requested review from gcs278 and rikatz August 24, 2026 14:41
@grzpiotrowski
grzpiotrowski force-pushed the kube-rbac-proxy-1-3-9-bump branch from 33c7c2b to 8c3940a Compare August 24, 2026 14:55
@alebedev87

Copy link
Copy Markdown
Contributor

/lgtm
/approve

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

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 25, 2026
@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@grzpiotrowski: 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 c2af854 into openshift:main Aug 25, 2026
35 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants