forked from rook/rook
The upgrade integration test was from rook v1.6 to the latest master. This was necessary until we are ready for the v1.8 release, from which time we want to focus the upgrade testing from v1.7 to the latest master. The duplication in the test CRs and other resources is now reduced by the upgrade calling a thin wrapper to forward a call to the master version of the resource. When a new feature is added that needs to be differentiated from the previous version, the method then can be implemented instead of wrapping the master implementation. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>