v5.5.0 is missing on registry.k8s.io/kustomize

[odise]

What happened?

Docker image v5.5.0 is missing in registry.k8s.io/kustomize.

What did you expect to happen?

The image should be available.

Expected output

v5.5.0: Pulling from kustomize/kustomize
....

Actual output

$ docker pull registry.k8s.io/kustomize/kustomize:v5.5.0
registry.k8s.io/kustomize/kustomize:v5.5.0
Error response from daemon: manifest for registry.k8s.io/kustomize/kustomize:v5.5.0 not found: manifest unknown: Failed to fetch "v5.5.0"

Kustomize version

v5.5.0

Operating system

Linux

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

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-sigs/prow repository.

[marshallford]

Still bumping into this. Can the workflow which publishes the container image be rerun or must a new version be cut to resolve?

[koba1t]

Hi @odise

That problem is a CI problem and that was fixed in the PR.
#5785

But, we need to make a new release tag to create a new image.
I plan to make a new kustomize release in this week. Please wait for us to create a new one.