OCPBUGS-61949: Remove references to cluster-api-operator image

[mdbooth]

Summary by CodeRabbit

• Chores
  • Removed the cluster-kube-cluster-api-operator image from development image mappings, configuration, and image stream tags.
  • Streamlines the image inventory by eliminating an unused reference; remaining images are unchanged.
  • No impact on existing functionality or cluster behavior; this is a cleanup of obsolete image entries.
  • Reduces maintenance overhead and potential confusion in image lists without altering workflows or deployment processes.

[openshift-ci-robot]

@mdbooth: This pull request references Jira Issue OCPBUGS-61949, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

The bug has been updated to refer to the pull request using the external bug tracker.

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.

[coderabbitai]

Walkthrough

Removed the cluster-kube-cluster-api-operator image entry across three locations: dev-images.json, the cluster-capi-operator-images ConfigMap data (images.json), and the image stream tags in manifests/image-references. No other keys, structures, or tags were altered.

Changes

Cohort / File(s)	Summary
Image reference removal dev-images.json, manifests/0000_30_cluster-api_01_images.configmap.yaml, manifests/image-references	Deleted the cluster-kube-cluster-api-operator image entry from local dev mappings, the ConfigMap images.json, and the imagestream tags; all other entries unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I hop through tags and prune the vine,
One image gone—clean, neat, fine.
Fewer carrots in the crate today,
But every sprout still points the way.
Thump, thump—repos light and clear,
A tidy burrow for release is near. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title accurately reflects the core change of removing all references to the cluster-api-operator image and includes the relevant bug tracking number in a concise form, making it clear to reviewers what the pull request accomplishes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between eea205c and 2597826.

📒 Files selected for processing (3)

• dev-images.json (0 hunks)
• manifests/0000_30_cluster-api_01_images.configmap.yaml (0 hunks)
• manifests/image-references (0 hunks)

💤 Files with no reviewable changes (3)

• dev-images.json
• manifests/0000_30_cluster-api_01_images.configmap.yaml
• manifests/image-references

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[chrischdi]

/lgtm

[damdo]

/test ?

[openshift-ci]

@damdo: The following commands are available to trigger required jobs:

/test build

/test e2e-aws-capi-techpreview

/test e2e-aws-ovn

/test e2e-aws-ovn-serial-1of2

/test e2e-aws-ovn-serial-2of2

/test e2e-aws-ovn-techpreview

/test e2e-aws-ovn-techpreview-upgrade

/test e2e-azure-capi-techpreview

/test e2e-azure-ovn-techpreview-upgrade

/test e2e-gcp-capi-techpreview

/test e2e-gcp-ovn-techpreview

/test e2e-openstack-capi-techpreview

/test e2e-openstack-ovn-techpreview

/test e2e-vsphere-capi-techpreview

/test images

/test lint

/test okd-scos-images

/test unit

/test vendor

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-azure-ovn-techpreview

/test e2e-metal3-capi-techpreview

/test okd-scos-e2e-aws-ovn

/test regression-clusterinfra-aws-ipi-techpreview-capi

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cluster-capi-operator-main-build

pull-ci-openshift-cluster-capi-operator-main-images

pull-ci-openshift-cluster-capi-operator-main-lint

pull-ci-openshift-cluster-capi-operator-main-okd-scos-e2e-aws-ovn

pull-ci-openshift-cluster-capi-operator-main-okd-scos-images

pull-ci-openshift-cluster-capi-operator-main-unit

pull-ci-openshift-cluster-capi-operator-main-vendor

pull-ci-openshift-cluster-capi-operator-main-verify-deps

In response to this:

/test ?

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.

[damdo]

/test regression-clusterinfra-aws-ipi-techpreview-capi
/test e2e-aws-ovn-techpreview-upgrade
/test e2e-aws-capi-techpreview
/test e2e-aws-ovn
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2

[damdo]

/approve
/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [damdo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[damdo]

/verified bypass

No need for formal QE verification on this

[openshift-ci-robot]

@damdo: The verified label has been added.

In response to this:

/verified bypass

No need to formal QE verification on 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.

[damdo]

/unhold

[damdo]

/hold

[openshift-ci]

@mdbooth: all tests passed!

Full PR test history. Your PR dashboard.

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.