MULTIARCH-5800: Images with attestation manifests lead the operator to set a node affinity for the architecture "unknown"

[AnnaZivkovic]

{
  "schemaVersion": 2,
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "manifests": [
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
      "size": 5436,
      "platform": {
        "architecture": "amd64",
        "os": "linux"
      }
    },
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "digest": "sha256:6eba444dd58a8748225335c4dcc53232c53d8252370f4a01ecfa6e692925db73",
      "size": 568,
      "annotations": {
        "vnd.docker.reference.digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
        "vnd.docker.reference.type": "attestation-manifest"
      },
      "platform": {
        "architecture": "unknown",
        "os": "unknown"
      }

Some container images (e.g., ghcr.io/llm-d/llm-d-cuda-dev:pr-230) include attestation manifests alongside runnable image manifests. These attestation manifests have:

• Platform architecture set to "unknown"
• Platform OS set to "unknown"
• An annotation vnd.docker.reference.type: attestation-manifest

The operator was processing these attestation manifests as valid image manifests, leading to:

1. "unknown" being added to the set of supported architectures
2. Node affinity requirements being set for kubernetes.io/arch=unknown
3. Pods failing to schedule since no nodes match this architecture

[openshift-ci-robot]

@AnnaZivkovic: This pull request references MULTIARCH-5800 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 bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

{
 "schemaVersion": 2,
 "mediaType": "application/vnd.oci.image.index.v1+json",
 "manifests": [
   {
     "mediaType": "application/vnd.oci.image.manifest.v1+json",
     "digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
     "size": 5436,
     "platform": {
       "architecture": "amd64",
       "os": "linux"
     }
   },
   {
     "mediaType": "application/vnd.oci.image.manifest.v1+json",
     "digest": "sha256:6eba444dd58a8748225335c4dcc53232c53d8252370f4a01ecfa6e692925db73",
     "size": 568,
     "annotations": {
       "vnd.docker.reference.digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
       "vnd.docker.reference.type": "attestation-manifest"
     },
     "platform": {
       "architecture": "unknown",
       "os": "unknown"
     }

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AnnaZivkovic

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [AnnaZivkovic]

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

[openshift-ci-robot]

@AnnaZivkovic: This pull request references MULTIARCH-5800 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 bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

{
 "schemaVersion": 2,
 "mediaType": "application/vnd.oci.image.index.v1+json",
 "manifests": [
   {
     "mediaType": "application/vnd.oci.image.manifest.v1+json",
     "digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
     "size": 5436,
     "platform": {
       "architecture": "amd64",
       "os": "linux"
     }
   },
   {
     "mediaType": "application/vnd.oci.image.manifest.v1+json",
     "digest": "sha256:6eba444dd58a8748225335c4dcc53232c53d8252370f4a01ecfa6e692925db73",
     "size": 568,
     "annotations": {
       "vnd.docker.reference.digest": "sha256:0298f7c3ceec45da42b10f52b8edd4c5ebe5edb8011d62b8e5d66fef749ce124",
       "vnd.docker.reference.type": "attestation-manifest"
     },
     "platform": {
       "architecture": "unknown",
       "os": "unknown"
     }

Some container images (e.g., ghcr.io/llm-d/llm-d-cuda-dev:pr-230) include attestation manifests alongside runnable image manifests. These attestation manifests have:

• Platform architecture set to "unknown"
• Platform OS set to "unknown"
• An annotation vnd.docker.reference.type: attestation-manifest

The operator was processing these attestation manifests as valid image manifests, leading to:

1. "unknown" being added to the set of supported architectures
2. Node affinity requirements being set for kubernetes.io/arch=unknown
3. Pods failing to schedule since no nodes match this architecture

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.

[AnnaZivkovic]

/test ocp420-e2e-gcp
/test ocp416-e2e-gcp

[openshift-ci]

@AnnaZivkovic: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ocp416-e2e-gcp	c7c603f	link	true	/test ocp416-e2e-gcp

Full PR test history. Your PR dashboard.

Details

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.