-
Notifications
You must be signed in to change notification settings - Fork 344
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
do not include runtime artefacts in operator image by default #468
Comments
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Feb 22, 2019
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Feb 22, 2019
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Feb 25, 2019
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Feb 25, 2019
lburgazzoli
added a commit
that referenced
this issue
Feb 25, 2019
Fixed by #486 |
valdar
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
May 21, 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
As today we bundle the runtime artefacts as part of the operator docker images by default but that should be an optional task used for local development.
The text was updated successfully, but these errors were encountered: