VCFA provisioned databases auto spin out or crash during VKS upgrade.

Products

• VMware Data Services Manager for VCF

Issue/Introduction

• When upgrading Kubernetes Services from 3.4.1-embedded+v1.33 to 3.5.0+v1.34, all databases provisioned from VCFA auto spin out new DB and perform cut over.
• Databases created using VCFA would go down during this activity. However, databases created from DSM managed, do not encounter this issues.

Environment

• VMware Data Services Manager 9.0.1
• VKS 3.5.0+

Cause

This is due to the compatibility issue with VKS where VMware Data Services Manager 9.0 is not compatible with vSphere Kubernetes Service (VKS) 3.5.0.

Refer: VMware Data Services Manager 9.0.1 Release Notes

 

Resolution

Workaround:

There is no option to revert the VKS version. As a workaround, we need to destroy and re-create supervisor cluster.