#How to refresh tridentvolume if we move ONTAP volume from one aggregate to another?

1 messages · Page 1 of 1 (latest)

bitter cave
#

We have moved Trident provisioned K8s volumes from one aggregate to another via ONTAP CLI. We have manually restarted tridentctontroller, so it can refresh the list of available Aggregates on SVN. But this did not trigger update of the tridentvloume CRs. These are still show old aggregate name on "POOL" field.

bitter cave
#

letting Trident known about new Aggregate on SVM can be achieved via: kubectl -n trident-operator rollout restart deployment/trident-controller

#

but moving volume in between aggregates won't refresh tridentvolume CRs pool assignment no matter what we try