I've updated the InterLink Plugin SDK with the types to add support for PersistentVolumeClaims, see:
and accordingly I've updated the Interlink Kubernetes Plugin to create such PVCs on the kubernetes remote side when they are provided in the create call.
Currently, the Interlink Kubernetes Plugin handles volumes (and in particular PVCs) as explained here (we can discuss about it):
To test the implementation, I need the InterLink API Server to support the PVC use case, i.e. when a POD referencing a PVC is submitted, I expect the API Server to forward to the plugin a create request with the PVC definition as well, so that the same PVC can be created on the remote side (if it does not exist already).
Also, since the POD is submitted to the local cluster, the PVC must exist on the local cluster as well, otherwise Kubernetes won't schedule it on the VirtualNode (and the POD won't be offloaded). I don't know if this requirement can be dropped somehow.
Thanks.
I've updated the InterLink Plugin SDK with the types to add support for PersistentVolumeClaims, see:
and accordingly I've updated the Interlink Kubernetes Plugin to create such PVCs on the kubernetes remote side when they are provided in the create call.
Currently, the Interlink Kubernetes Plugin handles volumes (and in particular PVCs) as explained here (we can discuss about it):
To test the implementation, I need the InterLink API Server to support the PVC use case, i.e. when a POD referencing a PVC is submitted, I expect the API Server to forward to the plugin a create request with the PVC definition as well, so that the same PVC can be created on the remote side (if it does not exist already).
Also, since the POD is submitted to the local cluster, the PVC must exist on the local cluster as well, otherwise Kubernetes won't schedule it on the VirtualNode (and the POD won't be offloaded). I don't know if this requirement can be dropped somehow.
Thanks.