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

Evaluate Knative build #49

Closed
miwurster opened this issue Oct 30, 2018 · 1 comment
Closed

Evaluate Knative build #49

miwurster opened this issue Oct 30, 2018 · 1 comment
Assignees
Labels
L Large issue size

Comments

@miwurster
Copy link
Contributor

miwurster commented Oct 30, 2018

As a user, I want to exploit a source-to-URL workflow with Kubernetes when services are specified with a Dockerfile only.


MICO enables the import of services based on a plain GitHub repository where a Dockerfile is hosted.
In order to deploy this service, a respective Docker image has to be built beforehand.
Here, we want to evaluate if and how we can exploit the source-to-URL workflow example by Knative.


Which options exist to build a Docker image based on a Dockerfile and sources on the Kubernetes cluster where also MICO is running on.

ADR discussing the options

  • Kaniko
  • Knative build
@miwurster miwurster added the L Large issue size label Oct 30, 2018
@Jojo134 Jojo134 assigned Jojo134, davidkopp and tSneijdr and unassigned Jojo134 Oct 30, 2018
@davidkopp davidkopp assigned davidkopp and unassigned davidkopp Oct 30, 2018
@davidkopp
Copy link
Contributor

davidkopp commented Nov 26, 2018

I wrote two ADRs that are related to this user story:

To summarize it: Knative Build let us achieve a source-to-image workflow in a descriptive way (describing build steps) that uses e.g. Kaniko as the Builder for the creation of the resulting image. To achieve a source-to-url workflow we would need also Knative Serving (and Istio).

@spethso spethso closed this as completed Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L Large issue size
Projects
None yet
Development

No branches or pull requests

5 participants