Skip to content

NE-2822: Update kube-rbac-proxy to latest v4.19 - #544

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
grzpiotrowski:bump-kube-rbac-proxy-july
Jul 31, 2026
Merged

NE-2822: Update kube-rbac-proxy to latest v4.19#544
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
grzpiotrowski:bump-kube-rbac-proxy-july

Conversation

@grzpiotrowski

Copy link
Copy Markdown
Contributor

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

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

openshift-ci-robot commented Jul 30, 2026

Copy link
Copy Markdown

@grzpiotrowski: This pull request references NE-2820 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.0.0" version, but no target version was set.

Details

In response to this:

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

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 Jul 30, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

Updates the kube-rbac-proxy image declaration from v4.18 to v4.19, including its catalog reference and KUBE_RBAC_PROXY_IMAGE_PULLSPEC digest.

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
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 Only bundle-hack/container_digest.sh changed; no Ginkgo tests or titles were added or edited.
Test Structure And Quality ✅ Passed Only bundle-hack/container_digest.sh changed; no Ginkgo test code was added or modified, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only bundle-hack/container_digest.sh changed; no Ginkgo tests or new test bodies were added, so MicroShift compatibility isn’t implicated.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR only updates bundle-hack/container_digest.sh; no Ginkgo/e2e tests were added or modified, so there’s no SNO-specific test compatibility risk.
Topology-Aware Scheduling Compatibility ✅ Passed Only a container digest/comment update in bundle-hack/container_digest.sh; no scheduling, manifests, or controllers were modified.
Ote Binary Stdout Contract ✅ Passed Diff only updates bundle-hack/container_digest.sh image digests/comments; no process-level stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only a container digest script changed; no new Ginkgo tests or network/IP logic were added.
No-Weak-Crypto ✅ Passed Patch only updates kube-rbac-proxy image digest/comments in container_digest.sh; no MD5/SHA1/DES/RC4/ECB, custom crypto, or secret comparisons present.
Container-Privileges ✅ Passed PR only updates kube-rbac-proxy digest/comments in bundle-hack/container_digest.sh; no manifest changes or privileged settings were introduced.
No-Sensitive-Data-In-Logs ✅ Passed The only changed file adds image-pullspec comments and an export; no logging, secrets, or PII exposure was introduced.
Title check ✅ Passed The title clearly summarizes the main change: upgrading kube-rbac-proxy to v4.19.
Description check ✅ Passed The description is directly related to the image bump and maintenance release context.
✨ 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.

@grzpiotrowski
grzpiotrowski force-pushed the bump-kube-rbac-proxy-july branch from d983025 to 3cd37b5 Compare July 30, 2026 09:32
@openshift-ci
openshift-ci Bot requested review from bentito and davidesalerno July 30, 2026 09:32
@grzpiotrowski

grzpiotrowski commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

/retitle NE-2822: Update kube-rbac-proxy to latest v4.19

@openshift-ci openshift-ci Bot changed the title NE-2820: Update kube-rbac-proxy to latest v4.19 NE-2822: Update kube-rbac-proxy to latest v4.19 Jul 30, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 30, 2026

Copy link
Copy Markdown

@grzpiotrowski: This pull request references NE-2822 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.0.0" version, but no target version was set.

Details

In response to this:

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

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 Jul 30, 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.

@alebedev87 alebedev87 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.

/lgtm
/approve

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

openshift-ci Bot commented Jul 31, 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 Jul 31, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 26e868b into openshift:main Jul 31, 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