Open kriswuollett opened 2 months ago
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.
Seems to be a usage error on my part, but the error message was not informative. I noticed that another one of my modules worked and slowly morphed it into the example above. The incorrect config was either lack of a namespace, or I had included things in generators which should have been in resources accidentally while I as debugging.
Instead updating title to exec plugin errors need to be more descriptive, i.e., what exact namespace / name / path was expected to be present. The above error seems like it writes the old/deprecated error regarding Go plugins, if any method of plugin lookup did not work.
What happened?
I've written multiple alpha exec plugins using bash scripts. They work fine on Linux (debian-12) with kustomize v5.4.1. However running the same build command on macOS with either the homebrew v5.4.1 or the direct download binary version of v5.4.1 it fails with an error about not being able to find the plugin.
It's as if the command line parameter help for those options were compiled in, but the updated logic was not:
Copying an example of one of my generators below that exhibits this problem.
What did you expect to happen?
The macOS build of kustomize runs identically to the Linux version under these options, so that I can test mini versions of my clusters locally on my mac... without looking into a workaround of running kustomize in a Linux docker container.
How can we reproduce it (as minimally and precisely as possible)?
kustomization.yaml
l2AddressPool.yaml
./plugins/docker-l2-address-pool.sh
Run in shell:
Expected output
Actual output
Kustomize version
v5.4.1
Operating system
MacOS