I highly doubt it... but you can easily find out using kubectl get pv and see what's out there 🙂
Regarding your error, it seems suspicious that the PersistentVolume "elasticsearch-pv" is in namespace "" - shouldn't it be in the old trains namespace? In any case, you'll need to make sure there's no conflict...
Hi DeliciousBluewhale87 ,
Well, we did discontinue support for the bare-metal k8s templates, as they were basically duplicated in the Helm chart.
Could it be another applications's "elasticsearch-pv" and not clearml's