Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design a mechanism to update the soda with all the existing CSI driver deployment in k8s. #411

Open
asifdxtreme opened this issue Apr 7, 2021 · 1 comment

Comments

@asifdxtreme
Copy link
Member

Issue/Feature Description:
Design a mechanism to update the SODA dynamically with the metadata of all the existing deploymen of CSI drivers in k8s.

Why this issue to fixed / feature is needed(give scenarios or use cases):
We need to fix this issue so that SODA can automatically decide with CSI driver needs to be picked for volume provisioning.

@kumarashit kumarashit added this to To Do in SODA - Jerba Release v1.4.0(Q2 2021) via automation Apr 7, 2021
@asifdxtreme asifdxtreme self-assigned this Apr 8, 2021
@asifdxtreme asifdxtreme moved this from To Do to In progress in SODA - Jerba Release v1.4.0(Q2 2021) May 7, 2021
@asifdxtreme asifdxtreme added this to the Iter2_Jerba milestone May 12, 2021
@asifdxtreme asifdxtreme modified the milestones: Iter2_Jerba, Iter3_Jerba May 20, 2021
@asifdxtreme
Copy link
Member Author

We can have 2 approach here :

  1. We can make use of sidecars to update the soda-api-server with all the details of (StorageClass, PV, PVC ) whenever these sidecars gets a request to change the state of these objects. Problem with this approach might be that we might not get full state of K8s env unless and until any request lands to sidecar. And also we have to tweak all the sidecars of CSI to get this working.
  2. We can develop a soda-syncer which will watch on the objects(SC, PV, PVC, CSINodes, CSIDrivers) and update the state of these objects to soda-api-server, this appraoch will help to get the full state of k8s env and also will help soda-csi-provisioner to enable the intelligence while picking the driver. This approach will require user to deploy this syncer in k8s env with proper permissions to connect with k8s-api-server.

@sushanthakumar @AmitRoushan @kumarashit @skdwriting @rajat-soda
Please give your suggestion on which approach will be better for this requirement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant