registry.k8s.io/ingress-nginx/controller:v1.10.0 has no s390x arch in the image manifest

[evanskinner]

What happened:

Running nginx-ingress on s390x arch in k8s and the nginx-ingress pod is showing: http://registry.k8s.io/ingress-nginx/controller:v1.10.0@sha256:42b3f0e5d08468761791cd3afeb5f1cbbe4259d6f35651dcc1b5c980925379c": no matching manifest for linux/s390x in the manifest list entries

What you expected to happen:

The image to be pulled and run on s390x. The v1.9.x images all had an s390x image

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Pod is not running

Kubernetes version (use kubectl version):
v1.28.8

• Others:

$ podman manifest inspect registry.k8s.io/ingress-nginx/controller:v1.10.0
{
    "schemaVersion": 2,
    "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
    "manifests": [
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3259,
            "digest": "sha256:67f647d99b087bebd5e8c7792cc7d5dd715343354698c43ea0edab81896b75f0",
            "platform": {
                "architecture": "amd64",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3259,
            "digest": "sha256:8ba60866fa132a2a6cef840f0c6f412b615f0f161455a1771f1e7432eaff1685",
            "platform": {
                "architecture": "arm",
                "os": "linux",
                "variant": "v7"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3259,
            "digest": "sha256:2e53c57c81ebad0263e98c98b66f0151217ce417eeeaacf911e62cc3dbae27e4",
            "platform": {
                "architecture": "arm64",
                "os": "linux"
            }
        }
    ]
}

whereas:

$ podman manifest inspect registry.k8s.io/ingress-nginx/controller:v1.9.6
{
    "schemaVersion": 2,
    "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
    "manifests": [
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3062,
            "digest": "sha256:0939639a1f338a9eaaa490fd38b4a7881e47a7fd1a473baf8749ce15952b55b8",
            "platform": {
                "architecture": "amd64",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3062,
            "digest": "sha256:dcea8d021e15cf27f59249ee0cfd211559ef9eb60b10651c3af299499848cf8b",
            "platform": {
                "architecture": "arm",
                "os": "linux",
                "variant": "v7"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3062,
            "digest": "sha256:5fb823cc617cbfbee4b250ad5e059c23078ea63e9a7e6acb6d4d30e4456eb0be",
            "platform": {
                "architecture": "arm64",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 3062,
            "digest": "sha256:fc53a604eb2d17fa0cf7a3f266d052c2f32fb97209869057d6826d1815cf622d",
            "platform": {
                "architecture": "s390x",
                "os": "linux"
            }
        }
    ]
}

How to reproduce this issue:
Run docker manifest inspect registry.k8s.io/ingress-nginx/controller:v1.10.0 and you will see the s390x image is missing

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[strongjz]

I believe there was an issue with the 1.25 nginx build; we also did not produce a chroot image.

[tao12345666333]

Yes. We have not fix the problem during NGINX v1.25 build on s390x.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.