ROSAENG-4015: Update ethtool exporter images from 4.16 to 4.21 - #2830
ROSAENG-4015: Update ethtool exporter images from 4.16 to 4.21#2830nephomaniac wants to merge 1 commit into
Conversation
Update the supplemental ethtool node-exporter and kube-rbac-proxy images to match the CMO node-exporter images running on the 4.21.16 MCs. All 13 production MCs were verified to be running identical images on OCP 4.21.16. Image updates: - node-exporter: sha256:85765701... -> sha256:f4d6a42d... - kube-rbac-proxy: sha256:82f5ad5a... -> sha256:731316e9... Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
@nephomaniac: This pull request references ROSAENG-4015 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 task to target the "5.0.0" version, but no target version was set. DetailsIn 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nephomaniac The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughThe DaemonSet’s three container image digests and associated source comments are updated from PROD 4.16.42 references to PROD 4.21.16 references. No runtime configuration or deployment behavior changes. ChangesEtHTool exporter image refresh
Estimated code review effort: 1 (Trivial) | ~5 minutes Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
@nephomaniac just a heads up that 4.22 upgrades are in flight so you might be able to remove this whole stack once that is done and enable the native collector |
Summary
images running on 4.21.16 MCs
to keep the images aligned with the CMO node-exporter images running on the MCs
sha256:85765701...->sha256:f4d6a42d...sha256:82f5ad5a...->sha256:731316e9...Note: Draft Status
This PR is marked as draft pending manual validation. The updated images need to be
manually applied and verified on an integration or staging MC before this PR is ready
for merge. Validation should confirm:
*_allowance_exceededmetrics are collectedOnce validated, this PR can be marked ready for review and promoted through the
standard integration -> staging -> production pipeline.
Note: Upstream CMO ethtool collector support
RFE-7342 (Enable the ethtool collector
for OpenShift Monitoring Node Exporter) is still in Refinement. The CMO configuration
support has landed upstream via CMO#2779,
but only for OCP 4.22+. The MCs are currently running 4.21.16 and are not yet on a
version that supports the native CMO ethtool collector. This supplemental node-exporter
remains necessary until the MCs upgrade to 4.22, at which point ROSAENG-1211
tracks removing this stop-gap and configuring the CMO-native collector instead.
Related
🤖 Generated with Claude Code