Add Mount trait example

[haanhvu]

fixes #3140

Release Note

NONE

[squakez]

We already have that scenario covered as suggested in the related issue https://github.com/apache/camel-k/tree/main/examples/volumes. I think we need to go beyond the simple timer to log example. One suggestion I can do is to provide some realistic situation. In the volume example, you can see I've created a producer Integration writing and a consumer Integration reading to/from a shared Volume.
You may think on some alternative situation, for example, showing how to log the camel k to an external volume (see https://stackoverflow.com/a/70063203/10974363 for details how to specify log file path). Then you can show how you can scrape that log from another integration.
It's just an idea. I guess the final goal of these activities is to get a bit of knowledge on the platform.

[haanhvu]

You may think on some alternative situation, for example, showing how to log the camel k to an external volume (see https://stackoverflow.com/a/70063203/10974363 for details how to specify log file path). Then you can show how you can scrape that log from another integration. It's just an idea. I guess the final goal of these activities is to get a bit of knowledge on the platform.

@squakez I took your idea. Can you review please?

[squakez]

I think we still need something. Let me provide here a sort of script the user could run, and you will be able to provide the related Integrations:

kamel run Producer.java --volume my-pv-claim:/tmp/log -p quarkus.log.file.path=/tmp/log/trace.log -p quarkus.log.file.enable=true

kamel run Consumer.java --volume my-pv-claim:/tmp/log

The Producer could be a timer to log Integration. You can provide some incremental counter, ie, simple language ${exchangeProperty.CamelTimerCounter}. Ideally the consumer should process the file in order to do something (ie, filtering for some number), so you can have a basic example with a few useful things in it.

[haanhvu]

I think we still need something. Let me provide here a sort of script the user could run, and you will be able to provide the related Integrations:

kamel run Producer.java --volume my-pv-claim:/tmp/log -p quarkus.log.file.path=/tmp/log/trace.log -p quarkus.log.file.enable=true

kamel run Consumer.java --volume my-pv-claim:/tmp/log

The Producer could be a timer to log Integration. You can provide some incremental counter, ie, simple language ${exchangeProperty.CamelTimerCounter}. Ideally the consumer should process the file in order to do something (ie, filtering for some number), so you can have a basic example with a few useful things in it.

@squakez I did this. Please review.

[squakez]

Good work, thanks! Just remove the references of the Pod creation which are superfluous.

[squakez]

You don't need any live Pod for the PVC to be usable. You can just remove this line.

[haanhvu]

done!

[squakez]

This yaml is not needed, you can remove it.

[haanhvu]

@squakez can this be merged now?