Unable to provision new DBs on VMware Data Services Manager(DSM) 9.0.1, after upgrading vSphere Kubernetes Service(VKS)from 3.4.1 to 3.5.

Products

• VMware Data Services Manager for VCF

Issue/Introduction

Unable to provision DBs on the DSM 9.0.1 environment after upgrading vSphere Kubernetes Service (VFS) from 3.4.1 to 3.5. 

Environment

VMware Data Services Manager for VCF 9.0.1

Cause

VMware Data Services Manager 9.0 is not compatible with vSphere Kubernetes Service (VKS) 3.5.0.

See 9.0.1 release notes for more detail.

Resolution

1. Revert VKS to 3.4.1.
   This will require the deletion and re-creation of the supervisor using VKS 3.4.1. Side effects will be that existing DSM clusters will be deleted, and the vSAN File Services fixes that are in 3.5 will be reverted as well.
   
   
2. Wait for DSM 9.0.2 to be released that corrects the VKS API incompatibility issue, and in parallel stick to DSM Classic for existing testing.
   
   
3. Make no changes to the existing supervisor and environment, and build another environment for DSM with VKS 3.4.1.