chore: update component image digests (excluding clusters-service) - #6371
chore: update component image digests (excluding clusters-service)#6371Inbharaj Mani (inbharajmani) wants to merge 4 commits into
Conversation
chore: render digests using materialize
Revert the clusters-service image digest to the previous version (9b8050b0c3af) and pin it in the image-updater config to prevent auto-updates while investigating E2E APIService readiness failures. Ref: AROSLSRE-1685
There was a problem hiding this comment.
Pull request overview
This PR updates multiple component image digests across the repo while explicitly pinning the clusters-service image updater source tag to a specific commit SHA to avoid the known E2E regression described in AROSLSRE-1685.
Changes:
- Pin
clusters-serviceintooling/image-updater/config.yamlto a specific commit SHA to prevent automatic updates. - Refresh image digests in
config/config.yamland correspondingconfig/rendered/dev/*outputs (HyperShift, Velero, ACM bundles, kubeEvents, Thanos SHA, etc.). - Update ACM multicluster-engine Helm chart version to
2.11.5and adjust scheduling constraints (move from preferred nodeAffinity to a required nodeSelector for infra nodes), including regenerated fixtures.
Reviewed changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| tooling/image-updater/config.yaml | Pins clusters-service updater to a specific tag (commit SHA) to block auto-updates. |
| config/config.yaml | Bumps multiple default image digests/SHAs and updates generated version comments. |
| config/rendered/dev/pers/westus3.yaml | Materialized config reflecting updated image digests. |
| config/rendered/dev/perf/westus3.yaml | Materialized config reflecting updated image digests. |
| config/rendered/dev/dev/westus3.yaml | Materialized config reflecting updated image digests. |
| config/rendered/dev/cspr/westus3.yaml | Materialized config reflecting updated image digests. |
| config/rendered/dev/ci01/centralus.yaml | Materialized config reflecting updated image digests. |
| config/rendered/dev/ci00/centralus.yaml | Materialized config reflecting updated image digests. |
| acm/deploy/helm/multicluster-engine/templates/multicluster-engine-operator.deployment.yaml | Updates MCE operator operands/versions and changes infra placement to a nodeSelector. |
| acm/deploy/helm/multicluster-engine/Chart.yaml | Bumps chart version/appVersion to 2.11.5 and updates source digest reference. |
| acm/deploy/helm/multicluster-engine-crds/Chart.yaml | Bumps CRD chart version/appVersion to 2.11.5 and updates source digest reference. |
| acm/zz_fixture_TestHelmTemplate_dev_westus3_mgmt_1_mce.yaml | Regenerated Helm fixture to match the MCE chart changes. |
Suppressed comments (1)
config/config.yaml:747
- Same issue as the SVC section: the MGMT Thanos image keeps
tag: v0.41.0while theshaupdate is annotated asv0.42.4. For clarity and to avoid future tag-only consumption mistakes, update the tag to match the digest’s version and re-materialize rendered configs.
thanos:
image:
registry: arohcpsvcdev.azurecr.io
repository: thanos/thanos
tag: v0.41.0
sha: b567818fe608067eb0f1d7c2c4fe361e7ad83c8a256234c97685f1d0bf670cc8 # v0.42.4 (2026-07-30 13:37)
| registry: arohcpsvcdev.azurecr.io | ||
| repository: thanos/thanos | ||
| tag: v0.41.0 | ||
| sha: 6249f7aaadd3695df637fb2eb4cb9a9955611eee691c3970892fe9c0dc3f2db6 # v0.42.2 (2026-07-16 20:22) | ||
| sha: b567818fe608067eb0f1d7c2c4fe361e7ad83c8a256234c97685f1d0bf670cc8 # v0.42.4 (2026-07-30 13:37) |
e33756e to
fecb712
Compare
|
/test e2e-parallel |
|
The failure doesn't seem CS related. See Related thread |
Rael Garcia (raelga)
left a comment
Rael Garcia (raelga)
left a comment
There was a problem hiding this comment.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: inbharajmani, raelga The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Although it's not a regression in CS itself, the change in CS has surfaced another regression on the Hypershift side (See details in the thread). Until the issues on that side are resolved we are going to revert CS PR. It's currently passing CI on that side |
|
/retest |
|
Inbharaj Mani (@inbharajmani): The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
https://github.com/openshift-online/aro-hcp-clusters-service/commit/d69e2520ff1222d1778947398a846d2ff62ec455 |
|
/close https://github.com/openshift-online/aro-hcp-clusters-service/commit/d69e2520ff1222d1778947398a846d2ff62ec455 |
|
Inbharaj Mani (@inbharajmani): Closed this PR. 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 kubernetes-sigs/prow repository. |
AROSLSRE-1685
Update images except cluster service
Note: clusters-service is pinned to
sha256:981637a1e08c(commit9b8050b0c3af, 2026-07-29) and commented out in the image-updater config. The new clusters-service image (commit 2b4f2a905a76) removed an API URL gate in the manifestwork controller that was masking a timing gap, causing E2E APIService readiness failures on OCP 4.19 clusters.Supersedes #6337