Display signature badge for multi-arch images in Container Registry

Background

The current implementation of signature badges in the Container Registry works well for regular images but does not function correctly for multi-arch images. This issue aims to extend the functionality to support multi-arch images.

Current Behavior

When viewing multi-arch images in the Container Registry, the signature badge is not displayed correctly. For example:

image.png

Expected Behavior

The signature badge should be displayed next to the image name for multi-arch images, similar to how it works for regular images.

Steps to Reproduce

  1. Follow the container signing tutorial in the GitLab documentation.
  2. Create and sign a multi-arch image.
  3. Push the image to the GitLab Container Registry.
  4. View the image in the Container Registry UI.

Proposed Solution

Extend the current implementation to handle multi-arch images:

  1. Investigate how multi-arch images are stored and represented in the Container Registry.
  2. Modify the backend API to include signature information for multi-arch images.
  3. Update the frontend code to properly display signature badges for multi-arch images.

Implementation Details

  • Research multi-arch image structure and how signatures are associated with them.
  • Update the backend API to include signature information for multi-arch images.
  • Modify the frontend code to handle and display signature information for multi-arch images.
  • Add tests to ensure proper functionality for both regular and multi-arch images.
  • Update documentation to reflect the changes and provide guidance for multi-arch image signatures.

Related Issues

  • #423814 (closed) (Container scanning - show signature badge next to image name)
Edited by 🤖 GitLab Bot 🤖