install_kustomize.sh fails "cp: can't stat './kustomize': No such file or directory"

[Janny221199]

What happened?

I use the kustomize CLI in my gitlab CICD Pipeline. It always worked.

Lately my job fails while installing kustomize. I use the latest version.

Logs of my Gitlab Job:

$ curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"  | bash
cp: can't stat './kustomize': No such file or directory
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1

I use the gitlab-runner 16.3.0~beta.108.g2b6048b4 on green-2.saas-linux-small-amd64.runners-manager.gitlab.com/default

I use alpine:3.17.0 as image for my pipeline job

It would be really great if that will work again 👍🏻 If you need any help with that, please let me know!

Thank you very much!!

What did you expect to happen?

Running the installation script properly without any error.

How can we reproduce it (as minimally and precisely as possible)?

.deploy-job:
  image: alpine:3.17.0
  before_script:
    - apk add --no-cache git curl bash
    - curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"  | bash
    - mv kustomize /usr/local/bin/

Expected output

successful kustomize installation

Actual output

$ curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh"  | bash
cp: can't stat './kustomize': No such file or directory
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1

Kustomize version

latest

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

[sealneaward]

This just broke our gitops ci/cd pipelines as well.

[maxdanilov]

Looks like this issue is introduced by #5220 (PR: #5239): in the .tar.gz release artifacts starting 5.2.0, the kustomize binary is now inside the output directory (previously was in the root)

[natasha41575]

We are aware of the problem and have a fix in flight.

[natasha41575]

This is a duplicate of #5396, so closing.