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

Syndesis 2.0 to use Camel K as runtime engine #7790

Open
lburgazzoli opened this issue Feb 3, 2020 · 3 comments
Open

Syndesis 2.0 to use Camel K as runtime engine #7790

lburgazzoli opened this issue Feb 3, 2020 · 3 comments
Labels
cat/enhancement Enhancements to existing features and capabilities group/camel-k group/extension Tools for developing Syndesis extensions group/meta Service for connector meta-data and verification of connections group/operator Infrastructure operator related group/server REST backend for managing integrations status/never-stale Marker that this issue should not be marked as stale
Projects

Comments

@lburgazzoli
Copy link
Collaborator

lburgazzoli commented Feb 3, 2020

This is a...


[X] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

Description

As camel-k is heading toward version 1.0.0 I think it would be good to start planning to make it the default runtime engine and completely drop spring-boot support.

image

There are a number of reason to switch to camel-k as default engine, like:

  • fast iterations as camel-k can make intelligent choices about how and when new container images have to be created in contrast to the spring-boot model that required to rebuild the fat-jar every time
  • native support for Knative
  • native support for Quarkus

The switch is not free as there are a number of areas in which both Syndesis and camel-k need to be enhanced, like:

We may also think about generating integrations using camel-k's YAML DSL to further decouple Syndesis from the runtime integration implementation

References

@lburgazzoli lburgazzoli added group/server REST backend for managing integrations group/meta Service for connector meta-data and verification of connections status/never-stale Marker that this issue should not be marked as stale cat/enhancement Enhancements to existing features and capabilities group/camel-k group/operator Infrastructure operator related group/extension Tools for developing Syndesis extensions labels Feb 3, 2020
@delokman
Copy link

Hello @lburgazzoli
thanks to open this issue,
how long take time to implement this feature?

@Delawen Delawen added this to To do in Camel-K 1.0 via automation Jun 19, 2020
@Delawen
Copy link
Contributor

Delawen commented Jul 9, 2020

@lburgazzoli we are moving forwards with this (see https://github.com/syndesisio/syndesis/projects/8).

Is this still accurate? Did something changed after the release? Any hints you can share?

@lburgazzoli
Copy link
Collaborator Author

Except for the extensions, the other bits are still accurate.

About extension I'd wait a little bit more as we are working on the kamelets see:

And that could completely change how we deal with extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat/enhancement Enhancements to existing features and capabilities group/camel-k group/extension Tools for developing Syndesis extensions group/meta Service for connector meta-data and verification of connections group/operator Infrastructure operator related group/server REST backend for managing integrations status/never-stale Marker that this issue should not be marked as stale
Projects
No open projects
Camel-K 1.0
  
To do
Development

No branches or pull requests

3 participants