forked from rook/rook
The rook.io/v1 package was only an internal implementation detail and does not have any CRDs that rely on it. The CRD deserialization should handle the change in internal types without any issue. This separation gives more flexibility for the storage providers to implement exactly what is needed for their storage provider instead of forcing to use the same types and risk affecting another storage provider. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>