Two embedded harbor registries created in Supervisor Cluster

Products

• Tanzu Kubernetes Runtime

Issue/Introduction

• Embedded harbor registry is enabled in Supervisor cluster.
• Power outage in the whole system and another embedded harbor registry created with different namespace of 'vmware-system-registry-xxxxxxxx'
• Under Cluster - Configure - Supervisor Cluster - Image Registry it shows the last registry information and IP address.
• Both embedded harbor registries can work normally.

Environment

vSphere with Tanzu 7.0

Resolution

Delete the last embedded harbor registry:

1. Make sure the last embedded harbor registry is in use or not. If there are container images stored in this registry, suggest to export them to local. 
2. Disable the last embedded harbor registry from Cluster - Configure - Supervisor Cluster - Image Registry

After that the old embedded harbor registry becomes active in the Image Registry and can be managed.