Camel K - best practices

[Gerald Kallas <ca...@mailbox.org.INVALID>]

Dear community,

when using Camel K I'm interested in some best practices. Assuming the case of a REST API that needs to be securely called from an external application, process some data (with data transformation) and route the data to one ore more external (secured) HTTP endpoints (APIs or plain).
1. What's recommended for authentication of the API - defining the security for the API itself (leveraging Quarkus security) or using an dedicated gateway (ingress or similar). In the second case, how to publish the API endpoint when deploying the API?
2. Where to store configuration information for the routes? At deployment time only?
3. Where to store credentials for the external endpoints securely?
4. When coupling multiple routes that are defined in multiple applications, is Service Mesh recommended? If yes, how to interact from routes to other ones?
Best
Gerald