With #5845 we are bundling the Kamelets coming from the Camel dependency distribution. With this model we make sure that the Kamelets provided in the cluster are the ones compatible with the IntegrationPlatform. However, those Kamelets may not be compatible with any other Camel versions we want to run.
In order to avoid compatibility issues, and, related to the work initiated in #4395, we should instead use the approach taken from Camel core, which is bundling the Kamelet catalog with the given Maven dependency. We may provide a catalog-dependency parameter in order to let the user provide his own catalog as well.
Eventually we may turn the Kamelet catalog specification bundled in the cluster as kind of "read only", where the user can have a look at the specification as a reference. However, this specification may be different as the runtime would use the one coming from the maven dependency compatible with the given Camel version.
With #5845 we are bundling the Kamelets coming from the Camel dependency distribution. With this model we make sure that the Kamelets provided in the cluster are the ones compatible with the IntegrationPlatform. However, those Kamelets may not be compatible with any other Camel versions we want to run.
In order to avoid compatibility issues, and, related to the work initiated in #4395, we should instead use the approach taken from Camel core, which is bundling the Kamelet catalog with the given Maven dependency. We may provide a
catalog-dependencyparameter in order to let the user provide his own catalog as well.Eventually we may turn the Kamelet catalog specification bundled in the cluster as kind of "read only", where the user can have a look at the specification as a reference. However, this specification may be different as the runtime would use the one coming from the maven dependency compatible with the given Camel version.