Unable to retire tanzukubernetescluster objects that were previously managed by TMC

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

While running the retirement workflow detailed in this Techdoc, tanzukubernetescluster objects fail to retire once the appropriate label is set. TKCRetired status still shows as false, with the following message:

Message:               retirement is skipped for TMC-managed TKCs
    Reason:                Skipped
    Severity:              Info
    Status:                False
    Type:                  TKCRetired

TKC is no longer managed by Tanzu Mission Control (TMC).

Cause

TMC-related labels are still present on the TKC object, such as:

    run.tanzu.vmware.com/vmware-system-tmc-cluster-group: non-production
    run.tanzu.vmware.com/vmware-system-tmc-managed: "false"

Even if the labels indicate that the TKC is no longer TMC-managed, such as in the above example, the retirement workflow will still fail to move forward with the labels present.

Labels may not be present on the cluster object, but still present on the tanzukubernetescluster object.

Resolution

Remove the labels from the TKC object manually, which will allow the retirement to complete.