-
Notifications
You must be signed in to change notification settings - Fork 352
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
Publish some base images together with Camel K #312
Comments
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Jan 11, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
lburgazzoli
pushed a commit
that referenced
this issue
Jan 13, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an idea we should develop more, but it's powerful!
It's not always necessary to do a build to create the base image for an integration, we may publish some base images in advance when releasing Camel K.
This would be really awesome in the future if we start to produce native compiled images, because users will just use them, without having to produce them (as it seems it requires a lot of time and resources).
In the Knative context, for example, we can produce native images containing:
That image would be used automatically for the CamelSource-x, without requiring a new build inside Kubernetes.
The mechanism is useful also for standard JVM based images as it improves portability (does not require in-cluster build, that often require cluster-specific configuration).
The text was updated successfully, but these errors were encountered: