-
Notifications
You must be signed in to change notification settings - Fork 345
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 buildless direct deploy #31
Comments
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Sep 13, 2018
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Sep 13, 2018
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Sep 13, 2018
nicolaferraro
pushed a commit
that referenced
this issue
Sep 13, 2018
ipolyzos
referenced
this issue
in ipolyzos/camel-k
Jul 31, 2019
squakez
referenced
this issue
in squakez/camel-k
Jun 2, 2021
Add -mod=vendor to the go generate command
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The general way of doing builds expects a build phase where a docker image is generated.
In some cases, when there are no additional dependencies to load respect to "camel-core" (or respect to a "prebuilt context" we will add in the future), there's no need to build a docker image and we can run the integration directly.
We can mount the source file as configmap and load it directly in the runtime.
File mounting will also be the preferred strategy when dealing with ".js" files (independently of the build phase).
For the first stage, we can add a new strategy to the CR. When selected, the build will be performed without the source file, that will be later added at pod startup (e.g. mounted in a configmap). Later-on, we will add contexts to skip the build phase.
The text was updated successfully, but these errors were encountered: