piraeus-operator icon indicating copy to clipboard operation
piraeus-operator copied to clipboard

Published 20 hours ago • verified publisher icon piraeusdatastore

linstor-server adds extra CRDs

Open jeremyascott opened this issue 7 months ago • 2 comments

We noticed that there were several LINSTOR CRDs being added to our cluster that were not included in the piraeus operator release, for example;

  • linstorversion.internal.linstor.linbit.com
  • nodenetinterfaces.internal.linstor.linbit.com
  • nodes.internal.linstor.linbit.com

When we remove Piraeus from our cluster these CRDs persist, which resulted in unwanted state being preserved on future deployments of Piraeus. Specifically the satellites would come back up in an EVACUATE state. It seems like these CRDs should be removed by Piraeus when the linstor cluster has been deleted. Additionally, I think these extra CRDs should be documented to remove any potential future confusion.

jeremyascott avatar Apr 16 '25 10:04 jeremyascott

@WanzenBug i don't believe this is soley a documentation issue

fs185143 avatar Apr 25 '25 08:04 fs185143

Whatever solution we come up with, I don't think it will involve automatically wiping the database. This would be extremly painful for cases where the "LinstorCluster" resource was accidentally removed, and suddenly you lose access to all volumes.

I believe a more measured approach (perhaps on recreation somehow asking if the existing resources should be kept), is a better way.

WanzenBug avatar Apr 25 '25 10:04 WanzenBug