[GitHub] [camel-k] astefanutti opened a new issue #1998: Mount resource ConfigMaps as subPaths instead of volumes

[GitBox <gi...@apache.org>]

astefanutti opened a new issue #1998:
URL: https://github.com/apache/camel-k/issues/1998


   Following up the discussion from https://github.com/apache/camel-k-runtime/issues/593, it may be worth to explore mounting resources ConfigMap using `SubPath`. As opposed to mounting them as volumes, it's possible to project keys into an existing directory, which could alleviate the need to generate unique directory paths for each resource, and ease the work for users to reference them.
   
   The only side-effect of using `SubPath` is that updates to the ConfigMaps are not automatically projected into the containers. But I don't think that's an issue for Camel K.
   
   It hasn't been leveraged as `SubPath` was not historically supported for Knative service deployment. However, it seems that limitation has been removed in Knative: https://github.com/knative/serving/pull/3926.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-k] astefanutti closed issue #1998: Mount resource ConfigMaps as subPaths instead of volumes

[GitBox <gi...@apache.org>]

astefanutti closed issue #1998:
URL: https://github.com/apache/camel-k/issues/1998


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org