-
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
Support for ko
?
#1958
Comments
Thanks for opening this! Yes, this came up before, I'd love to see We are working on the extensibility model for skaffold builders currently, so things are a bit up in the air, as soon as that settled, we will be able to fit |
There is a `ko publish` mode which performs build and yaml replacement but
does not perform an apply.
…On Mon, Apr 15, 2019, 4:57 PM Balint Pato ***@***.***> wrote:
Thanks for opening this! Yes, this came up before, I'd love to see ko
integrated. One tricky bit is that ko is a builder and a deployer at the
same time, but probably we can work something out.
We are working on the extensibility model for skaffold builders currently,
so things are a bit up in the air, as soon as that settled, we will be able
to fit ko in theoretically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1958 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHlyN9TLqsQJ5t8wH2ex_YR1JISvWHNYks5vhRIHgaJpZM4cux0x>
.
|
We should try to add an example for ko custom builder. Maybe we could add this for github.com/tektoncd/pipelines |
@evankanderson please feel free to take a stab as per the docs mentioned https://skaffold.dev/docs/how-tos/builders/#custom-build-script-run-locally |
I'm closing this as it's been a while, and there are still no plans to create a 'ko' builder. That said, we now show how to use |
I'd like to be able to use
ko
to build binaries with SkaffoldExpected behavior
There are some docs about how to use
ko
withskaffold
.Actual behavior
No docs.
Information
/kind feature-request
The text was updated successfully, but these errors were encountered: