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
Issue/Feature Description:
The custom plugin will move the PlugNPlay in-tree code to csi-external provisioner
Why this issue to fixed / feature is needed(give scenarios or use cases):
With this enhancement users doesn't need to patch their exsisting deployment to use SODA CSI plugNplay features.
The text was updated successfully, but these errors were encountered:
Issue has been raised in external-provisioner project to discuss the possibility of integrating the Soda CSI pnp code either inside the external-provisioner or finding some mechanism to add the intelligence of soda without make any changes to external-provisioner. kubernetes-csi/external-provisioner#570
asifdxtreme
changed the title
Propose custom plugin for sidecars to CSI SIG.
Propose custom plugin for sidecars to external-provisioner
Feb 26, 2021
As per the comments from @pohlykubernetes-csi/external-provisioner#570 (comment) , we can try the second option of adding a proxy in between the sidecar and plugins, we have already tried the first option given by him but we are facing the issue in managing the code of different versions.
I will try out a poc for second option and post the response here.....
Issue/Feature Description:
The custom plugin will move the PlugNPlay in-tree code to csi-external provisioner
Why this issue to fixed / feature is needed(give scenarios or use cases):
With this enhancement users doesn't need to patch their exsisting deployment to use SODA CSI plugNplay features.
The text was updated successfully, but these errors were encountered: