Part 1 - Introduction and Environment Details¶
On June 29th VMware launched VMware Tanzu Mission Control Self-Managed which enabled the users to bring the power of Tanzu Mission Control SaaS deployment model to their self-managed infrastructures. The official VMware documentation details the features included as part of the initial release.
Tanzu Mission Control Self-Managed is a comprehensive API-driven cluster management platform, provided through a packaged deployment model, that allows you to monitor and manage your fleet of Kubernetes clusters from a single point of control. Tanzu Mission Control Self-Managed builds on the success of the SaaS deployment model for Tanzu Mission Control by enabling you to deploy the cluster management stack atop your own infrastructure.
TMC Self-Managed provides a very smooth installation experience to its users, one of the easiest installation workflows in the Tanzu product suite. This series of posts is aimed at providing a detailed walkthrough to users who want to get started with deploying TMC Self-Managed on their own and explore its capabilities.
Installing Tanzu Mission Control Self-Managed Series¶
- Part 1 - Introduction and Environment Details
- Part 2 - Setting Up Harbor as an Image Registry
- Part 3 - Configuring Okta as Identity Provider
- Part 4 - Configuring Other Prerequisites
- Part 5 - Tanzu Kubernetes Grid Cluster Setup
- Part 6 - Installing Tanzu Mission Control Self-Managed
For a detailed set of prerequisites and compatibility matrix please refer to Preparing your cluster for Tanzu Mission Control Self-Managed section of the VMware documentation. For this series, the environment details are as follows
|VMware vCenter Server||7.0 Update 3l, build-21477706|
|VMware ESXi||7.0 Update 3m, build-21686933|
|Tanzu Kubernetes Grid||v2.2|
|Load Balancer||VMware NSX ALB (Avi) v22.1.2|
|Harbor Image Registry||Photon v4 Harbor v2.7.1 OVA|
|OIDC Compliant identity provider||Okta|