-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Enhancement: Enable skaffold build to output kustomize edit set image instructions #2957
Comments
skaffold build
to output a file with kustomize edit set image
instructionsskaffold build
to output kustomize edit set image
instructions
skaffold build
to output kustomize edit set image
instructions
@tejal29 Thanks. That PR looks like it is for kubectl. Does it also work with Kustomize? |
@wstrange kustomize implementation in the works, it'll go out with the next release. will having rendered manifests solve this issue for you? |
Rendered kustomize manifests definitely solves our most pressing issue for CD integration. It would be really neat if skaffold could output # build, tag and push
skaffold build
# This also outputs a kustomize.edit.sh file... containing commands like
# kustomize edit set image busybox=alpine:3.6
# CD process runs:
# ./kustomize.edit.sh
# Then deploys:
# kustomize build ./path | kubectl apply -f - If the image output file was a simple csv or json mapping, the edit commands could also be derived from that. |
Thank you for the idea! I'm closing this issue as it's been open a while, and it is not clear if it's still an open issue. No one has recently stated an interest in addressing this, but if you feel strongly about it, please feel free to add a comment. |
This is also an issue for our use case. Looking into how we could utilise hooks to achieve the |
@ngfgrant I don't see why not. try configuring a |
This is related to #1187.
I'm not sure how the Kustomize deployer fixes up docker image names before deployment.
The "kustomize" way of setting image names is documented here: https://github.com/kubernetes-sigs/kustomize/blob/master/examples/image.md
If the
build
phase of skaffold could output a file that contains a series ofkustomize edit set image
transformations, this largely solves the problem of using skaffold in a CD pipeline where you want another tool (say argo) to manage the deployment.The workflow would be .
skaffold build
, to build, tag and push the final images, and then hand the generated kustomize edit file to the CD deployer to fix up the image names before sending to the cluster.Hope that makes sense.
The text was updated successfully, but these errors were encountered: