Skip to content
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

Updates to ko builder design proposal to add implementation approach #6046

Merged
merged 3 commits into from
Jun 23, 2021

Conversation

halvards
Copy link
Contributor

Tracking: #6041

Description
Update resolved questions and add section for implementation approach.

Specifically, document that the implementation will be a series of small PRs that can be merged one-by-one, rather than all at once when the feature is done. The PRs will not surface any new user-visible behavior until the feature is ready to be released.

Update resolved questions and add section for implementation approach.
@halvards halvards requested a review from a team as a code owner June 21, 2021 08:51
@halvards halvards requested a review from MarlonGamez June 21, 2021 08:51
@google-cla google-cla bot added the cla: yes label Jun 21, 2021
@halvards halvards mentioned this pull request Jun 21, 2021
@codecov
Copy link

codecov bot commented Jun 21, 2021

Codecov Report

Merging #6046 (7a0fbe5) into master (46c8933) will decrease coverage by 0.20%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6046      +/-   ##
==========================================
- Coverage   70.76%   70.55%   -0.21%     
==========================================
  Files         466      468       +2     
  Lines       17956    18036      +80     
==========================================
+ Hits        12706    12726      +20     
- Misses       4320     4375      +55     
- Partials      930      935       +5     
Impacted Files Coverage Δ
pkg/skaffold/util/tar.go 50.66% <0.00%> (-5.34%) ⬇️
pkg/skaffold/event/v2/application_logs.go 45.45% <0.00%> (-4.55%) ⬇️
pkg/skaffold/gcp/auth.go 23.33% <0.00%> (-1.67%) ⬇️
pkg/skaffold/kubernetes/logger/log.go 36.60% <0.00%> (-0.90%) ⬇️
pkg/skaffold/schema/versions.go 83.20% <0.00%> (ø)
pkg/skaffold/schema/v2beta17/upgrade.go 100.00% <0.00%> (ø)
pkg/skaffold/schema/v2beta17/config.go 20.58% <0.00%> (ø)
pkg/skaffold/output/color.go 91.48% <0.00%> (+0.58%) ⬆️
pkg/skaffold/docker/parse.go 87.14% <0.00%> (+0.95%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46c8933...7a0fbe5. Read the comment docs.

Add rough steps to Approach section.
Copy link
Contributor

@MarlonGamez MarlonGamez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one tiny typo and response to a question

docs/design_proposals/ko-builder.md Outdated Show resolved Hide resolved
Comment on lines +345 to +347
4. Should the ko builder be the default for `skaffold init`, instead of
buildpacks, for Go apps, when there's no Dockerfile and no Bazel workspace
file?
Copy link
Contributor

@MarlonGamez MarlonGamez Jun 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would be a good option. The way init treats buildpacks currently is pretty much like a catch all if we can't find a more specific builder to use for the project. So ko would be a good option to use first in this case

@MarlonGamez MarlonGamez enabled auto-merge (squash) June 23, 2021 20:51
@MarlonGamez MarlonGamez merged commit 6ac28cc into GoogleContainerTools:master Jun 23, 2021
@halvards halvards deleted the ko-design-proposal branch February 22, 2022 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants