-
Notifications
You must be signed in to change notification settings - Fork 404
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 setting KO_DOCKER_REPO
in .ko.yaml
#627
Comments
will you work on that @embano1? 🙋🏻♂️ |
Sure! My only real question is what do we want it to look like in |
Initially I thought a top-level Then I thought, how likely is it that multiple images should be pushed to different registries/locations? I.e. something similar we do with |
|
Hw about tags? Can they also be included in the .ko.yaml file to tag each build individually? Shall I create a tracking issue for this or there's a reason for not doing that? |
What's your use case for wanting each image in a The typical use case for tags is associating images with a release ( |
oops, sorry. I'm interested in different tags for |
You can already |
kindly ping @imjasonh |
This issue is stale because it has been open for 90 days with no |
Based on a Twitter conversation, it was raised whether
KO_DOCKER_REPO
should also be a configuration option in.ko.yaml
(mainly for consistency purposes).IMHO since this is not a build but publish option, it might have to go in
PublishOptions
parsing (related: #351).The text was updated successfully, but these errors were encountered: