As a developer I want a way to add volume references to my integrations and also use the mount trait to mount configmaps/secrets. Currently this is not possible without interfering with the mount trait.
Problem
The pod template can be used to add volume references to an integration however this overrides any volumes/mounts that are set with the mount trait. This leaves a situation where a configmap can be mounted through the mount trait, a pod template can define an emptyDir volume and only the emptyDir from the template will actually propagate to the integration pod resulting in failures.
Proposal
A suggestion from Zulip is to enhance the mount trait to allow for volume support in addition to the existing persistent-volume-claim support.
Requirement
As a developer I want a way to add volume references to my integrations and also use the mount trait to mount configmaps/secrets. Currently this is not possible without interfering with the mount trait.
Problem
The pod template can be used to add volume references to an integration however this overrides any volumes/mounts that are set with the mount trait. This leaves a situation where a configmap can be mounted through the mount trait, a pod template can define an
emptyDirvolume and only theemptyDirfrom the template will actually propagate to the integration pod resulting in failures.Proposal
A suggestion from Zulip is to enhance the mount trait to allow for volume support in addition to the existing persistent-volume-claim support.
Open questions
No response