Christoph Deppisch
Christoph Deppisch
This is related to #3522 where the integration pod fails right after the start because K_SINK has not been injected by Knative sink binding controller before the Camel route starts....
When there is an error in the operator during the reconciliation of a KameletBinding (e.g. a trait raises some error) the KameletBinding should reflect this error state in its status....
The Camel K operator tries to resolve dependencies for a given integration by having a look at the source code of the integration (e.g. by looking at the used Camel...
The Knative documentation uses a very old and obsolete description of the Camel event source. We should update this to reflect Kamelet catalog and a quickstart how to use KameletBindings...
Use latest Knative v1.5.0 for eventing and serving
As a result of #3358 the default integration platform is automatically created during the operator startup phase. This makes the default platform generation in the platform trait obsolete. We should...
The IntegrationPlatform resource should be visible to other viewers in order to see operator ids that are already present on the cluster. At the moment there is a special role...
This is a follow-up on #3358 We should allow to install multiple operators in a single namespace for the sake of multi operator handling on a single cluster. At the...
Support extended Knative trigger filters in KameletBindings on source/sink level https://knative.dev/docs/eventing/experimental-features/new-trigger-filters/
- Load and extract structural logging artifacts from Camel K runtime module - Use logback configuration provided by this runtime module - Add logging artifacts during Dockerfile image build IMPORTANT:...