[CAMEL-21036] Recovering cloud native properties

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.8.0
• Estimated Complexity: Unknown
• Assignee: Pasquale Congiusti
• Reporter: Pasquale Congiusti
• Created: 31/Jul/24 08:08
• Updated: 13/Aug/24 14:08
• Resolved: 13/Aug/24 14:08

Description

When we run a Camel application on the cloud we may leverage the cloud native way of setting configuration. For example, when running on Kubernetes we may leverage the configmap and secret which are typically mounted as a key/value files.

Given the following Secret:

apiVersion: v1
data:
  org.acme.my-key: czNjcjN0
kind: Secret
...

and the following Camel application Deployment volume mounted leveraging such a secret:

          volumeMounts:
          - mountPath: /etc/camel/conf.d/_secret/my-properties
            name: my-properties
            readOnly: true

We may expect that at startup, the application scans a given directory (ie /etc/camel/conf.d/_configmaps|_secrets/) and add the parameter to the regular properties available to the context. From that moment onward, the application could leverage the properties placeholder, ie using org.acme.my-key.

Ideally we should have a couple of properties to control the behavior, ie:

cloud.config.scan=false (not sure if enable this by default)
cloud.config.location=/etc/camel/conf.d