Claudio Miranda

What do you think about using `kn quickstart` ?

Adding these libraries would be exactly what I need. Thanks.

https://github.com/apache/camel/blob/main/components/camel-google/camel-google-mail/src/main/java/org/apache/camel/component/google/mail/BatchGoogleMailClientFactory.java#L51 We use to process authentication, where we require the user to supply `clientId, clientSecret, refreshToken, accessToken`

The channel-based-broker link gives 404. I think is the right doc, to install the broker when the annotation is set in the trigger. https://knative.dev/docs/eventing/broker/triggers/#trigger-annotations

I would say yes, as the [trigger annotations](https://knative.dev/v1.6-docs/eventing/broker/triggers/#trigger-annotations) may be set in he [CreateTrigger function](https://github.com/apache/camel-k/blob/main/pkg/util/knative/knative.go#L90), this way the knative sugar controller takes care of it.

Sure, [setting the integration as a knative addressable resource](https://knative.dev/v1.6-docs/eventing/sinks/#using-custom-resources-as-sinks) adds more opportunity to knative users to add camel-k integrations as destinations of SinkBindings. However the target integration must be aware...

I have not used this camel-webhook before, but it is an interesting idea. From camel side, only telegram component is able to have the webhook configured. From camel-k perspective I...

It seems these flags just remove debugging information from the final binary file. So if developers want to debug kamel or operator binary, these flags should not be used.

It is fixed, see [an example on how to set the custom broker name](https://github.com/apache/camel-k/blob/main/e2e/global/knative/files/knative_broker_receiver.groovy#L21). I am closing this issue, thanks for reminding.

@christophd @squakez for review.