cdi: Renaming binaries in the SPEC file to align with upstream naming conventions

[sharath-srikanth-chellappa]

The cdi binaries are misnamed in the SPEC file leading to additional Dockerfile commands to rename the binaries. Changing the SPEC file naming conventions to align with upstream and removing Dockerfile workarounds.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

The cdi binaries are misnamed in the SPEC file leading to additional Dockerfile commands to rename the binaries. Changing the SPEC file naming conventions to align with upstream and removing Dockerfile workarounds.

Change Log

Does this affect the toolchain?

NO

Associated issues

• #56050776

Links to CVEs

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=727053&view=results
• Container Pipeline Build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=728225&view=results

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-uploadserver:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet
[sudo] password for sharath:

acrafoimages.azurecr.io/base/kubevirt/cdi-uploadserver:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-uploadproxy:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-uploadproxy:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-operator:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-operator:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-importer:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-importer:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-controller:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-controller:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-cloner:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-cloner:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

(base) sharath@sharath-2:~$ sudo trivy image  --exit-code 1 --severity HIGH,CRITICAL,MEDIUM "acrafoimages.azurecr.io/base/kubevirt/cdi-apiserver:1.57.0-10.3.0.20250204-amd64" --ignore-unfixed --quiet

acrafoimages.azurecr.io/base/kubevirt/cdi-apiserver:1.57.0-10.3.0.20250204-amd64 (azurelinux 3.0)

Total: 0 (MEDIUM: 0, HIGH: 0, CRITICAL: 0)

[romoh]

LGTM

[mandeepsplaha]

The changes look good. Can you please run a container build for the cdi components and ensure they build successfully, and can you also link the build run in the PR description?

[sharath-srikanth-chellappa]

The changes look good. Can you please run a container build for the cdi components and ensure they build successfully, and can you also link the build run in the PR description?

Added that information to the PR description. Also added a manual trivy scan of the container images