MinIO Object Store support deprecated in DSM 9.0.1

Products

• VMware Data Services Manager

Issue/Introduction

As part of the 9.0.1 release, Broadcom have deprecated support for Minio ObjectStore. Therefore, users will not be able to:

• Create MinioProvider resource (rejected by webhook)
• Create ObjectstoreVCFABinding (rejected by webhook)
• Make any update to existing MinioProvider resource (rejected by webhook)
  
  

• Broadcom have removed MinioProvider DSV from 9.0.1 DataPlaceBundle

Environment

Upgrade from DSM 9.0.0 to DSM 9.0.1

Resolution

Users are advised to delete all the MinIO ObjectStore related resources manually, (DSM gateway kubeconfig is needed as the Minio section is removed from the DSM UI)

• Log in by using an SSH client to the VMware Data Services Manager appliance as root

• Delete all the MinioProviders manually. List them and delete using below commands.
  
   

  kubectl get minioproviders -A NAME STATUS HEALTH VERSION AGE test-minio Ready Healthy 2.1.0+vmware.v9.0.0.0 31h
   

  kubectl delete minioproviders -n <namespace> <minioprovider-name>
• Delete all the ObjectStoreVCFABindings manually. List them and delete using the below commands
  
   

  kubectl get objectstorevcfabinding -A NAME OBJECTSTOREVENDOR OBJECTSTORENAME AGE test-minio vcf test-minio 107m
   

  kubectl delete objectstorevcfabinding -n <namespace> <objectstorevcfabinding-name>
• If there is an OBJECT_STORE_ADMIN dsmrolebinding,
  
   

  kubectl get dsmrolebindings NAME ROLE AGE dsmadmin DSM_ADMIN 20h dsmosa OBJECT_STORE_ADMIN 20h dsmuser DSM_USER 20h
  
  
  • Check for the users with OBJECT_STORE_ADMIN roles in the permissions tab in DSM UI.
  • Delete the OBJECT_STORE_ADMIN dsmrolebinding
    
     

    kubectl delete dsmrolebindings dsmosa
  • Delete the OSE admins from DSM
    Using the DSM UI, delete all the OSE admins - These users will have empty roles now as dsmrolebinding is now deleted