-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow using kubectl built-in kustomize if separate kustomize binary is missing #63
Comments
The feature to add a custom binary recently got added(#62), maybe it can be used to solve this problem. |
As far as I can tell I could just feed Lines 128 to 138 in a67147a
I'm using chartify through helmfile, so I'll wait until this feature lands in helmfile to verify. |
Managed to get around testing this. So problem is that when I pass
I did manage to write a #!/usr/bin/env bash
if [ "$1" == "version" ]; then
kubectl version --client --short 2>/dev/null | awk '/Kustomize/{print $NF}'
exit
elif [ "$1" == "build" ]; then
shift
exec kubectl kustomize $@
else
echo "Could not shim kustomize: $@" >&2
exit 99
fi Then in
|
Turns out the above shim doesn't always work because chartify also runs |
You can run kustomize commands with kubectl like this:
Either fall back automatically to the kubectl built-in kustomize, or allow the user to select it.
The text was updated successfully, but these errors were encountered: