Tanzu Mission Control CLI functionality impacted by Kubernetes APIs deprecated in the Kubernetes v1.22 release

Products

• Tanzu Mission Control

Issue/Introduction

Symptoms:
Tanzu Mission Control (TMC) Customers may experience issues with the Tanzu Mission Control CLI (tmc) due to certain Kubernetes APIs being deprecated in the upcoming Kubernetes v1.22 release.

TMC UI/UX users may see this banner stating:

You MUST run "tmc update" to upgrade your TMC CLI to version 0.3.0 or higher before August 23, 2021.

The Tanzu Mission Control CLI based cluster attach operation fails while applying agent manifest with v1 CRDs.
Your output may look similar to the following:
 
√ cluster "usahai-test-cli" created successfully
┤ Error: failure to fetch attach manifests: no kind "CustomResourceDefinition" is registered for version "apiextensions.k8s.io/v1" in scheme "pkg/runtime/scheme.go:101"

Cause

TMC CLI v0.2.1 and older use Kubernetes APIs that will be deprecated in the upcoming Kubernetes v1.22 release. For more information, refer to Kubernetes API and Feature Removals In 1.22: Here’s What You Need To Know.

Resolution

TMC is making Tanzu Mission Control CLI v0.3.0 available in advance of support for Kubernetes v1.22 to give users time to upgrade before the older Tanzu Mission Control CLI versions stop working.

Upgrade to Tanzu Mission Control CLI Version v0.3.0 or newer. You can update to the latest version of Tanzu Mission Control CLI by running this command:

tmc update