TMC-SM Install Fails with Contour CRD Ownership Error

Products

• VMware Tanzu Mission Control

Issue/Introduction

When installing Tanzu Mission Control Self-Managed (TMC-SM) on a guest cluster which is already using Contour, you will encounter an error similar to the one below:

Jan 01 12:00.000  INF > Ownership errors:

Jan 01 12:00.000 INF > - Resource 'customresourcedefinition/extensionservices.projectcontour.io (apiextensions.k8s.io/v1) cluster' is already associated with a different label 'kapp.k14s.io/app=###################'
 
Jan 01 12:00.000  INF > - Resource 'customresourcedefinition/httpproxies.projectcontour.io (apiextensions.k8s.io/v1) cluster' is already associated with a different label 'kapp.k14s.io/app=####################'. Reconcile failed: Error (see .status.usefulErrorMessage for details)
 
Jan 01 12:00.000  INF [FAILED ] STEP 10/13 [Install Tanzu Mission Control Self-Managed]
 
Jan 01 12:00.000  ERR failed to create PackageInstall tanzu-mission-control

Environment

TMC-SM

VKS

Cause

It is currently not supported to install TMC-SM on clusters where Contour is already deployed.

Resolution

To resolve this issue, remove the existing Contour installation and then restart the TMC-SM installation.

If Contour was installed as a VKS package, it can be removed from the cluster using the vcf cli