You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my scenario, containers use PV/PVC to set up Volume/VolumeMount. In this case, the Mount.Destinationand Mount.Type in annotations. mounts.nri.io/container.container001is explicitly specified in the YAML configuration file without Mount.Source. I only want to specify the destination/type in the mount annotation, and then the NRI can automatically complete the other fields of Mount from the Container.Mount[i] by comparing the destination.
I understand that the current processing logic does not automatically complete the omitted Source/Options. This is not user-friendly for users who use CSI/PV/PVC.
(1) pareMount in device-injector needs have an argument container *api.Container not container Name.
(2) Unmarshal(annotation, &mounts)
(3) look up the containerMounts, with the Destination specified in annotation, if the annotion.Source is None, Just fill mounts with container.Mounts[i],Source;
Okay, so basically instead of injecting a new mount into a container you would like to adjusts the mount type (?) and options of an existing mount which would be matched/identified by its destination path ?
In my scenario, containers use PV/PVC to set up Volume/VolumeMount. In this case, the
Mount.Destination
andMount.Type
inannotations. mounts.nri.io/container.container001
is explicitly specified in the YAML configuration file withoutMount.Source
. I only want to specify the destination/type in the mount annotation, and then the NRI can automatically complete the other fields ofMount
from theContainer.Mount[i]
by comparing the destination.I understand that the current processing logic does not automatically complete the omitted Source/Options. This is not user-friendly for users who use CSI/PV/PVC.
The yaml as below looks like:
And just with the destination
/vol_x0000000002
in the annotationI have a solution to make it work well:
(1) pareMount in device-injector needs have an argument
container *api.Container
not container Name.(2) Unmarshal(annotation, &mounts)
(3) look up the containerMounts, with the Destination specified in annotation, if the annotion.Source is None, Just fill mounts with container.Mounts[i],Source;
Here is a rough code implementation:
The text was updated successfully, but these errors were encountered: