TMC TO (Wavefront) Solution - GitOps

Products

• Tanzu Mission Control

Issue/Introduction

The integrations feature which enabled customers to automatically onboard K8s clusters from Tanzu Mission Control (TMC) to Tanzu Observability (TO) and Tanzu Service Mesh (TSM) was removed on November 22, 2024. This document provides a workaround which was previously using TMC to manage TO (Wavefront) cluster onboarding and agent management via integrations. This solution enables customers to automate deployment and updates of the Wavefront operator packages using the TMC Flux Continuous Delivery capability. This enables customers to deploy the Wavefront operator directly to single clusters or to multiple clusters in a cluster group declaratively via git. This document outlines the design, implementation details, and usage instructions for this new Tanzu Observability solution, ensuring a seamless transition and continuity of monitoring and observability capabilities through TO. The process highlighted in this document is specific to automating package deployments at the TMC cluster group level, but could also be performed on individual clusters.

 

Supportability Guidance: Support for this process is dependent on users deploying TO/Wavefront using TMC's Flux Continuous Delivery capability. Other methods of installation are not supported. Support for this process extends to getting the TO/Wavefront pods into running state. Runtime and configuration support will not be provided for this configuration.

Resolution

Getting Started 

Prerequisites

1. Upstream conformant K8s cluster managed by or attached to TMC 
2. User with TMC ClusterGroup or Cluster admin access
3. Wavefront access token
4. Wavefront URL

Installation

Step 1 : Enable Continuous Delivery at the Cluster Group level

1. From the TMC UI, navigate to Cluster groups and select the appropriate cluster group
2. From the cluster group context, select Actions > Enable continuous delivery
   1. Enabling CD will bootstrap associated clusters with the Flux source and kustomize controllers
   2. This process can take up to 5 minutes to complete
   3. Note: This process and those documented below can also be performed against individual clusters based on your requirements.

 

Step 2 : Add Git Repository

1. Download tmc-wavefront-solution.zip from the Attachment and add the code to a new git repo.
   1. Create a new git repo
   2. Add the folders along with files to the newly created git repo
   3. Update Wavefront URL in Wavefront ---> wavefront.yaml
   4. Push changes to the newly created repo.
2. From the cluster group, navigate to Add-ons > Git repositories and select Add Git repository
3. Input the necessary information and click Add Git repository
   1. For the repository URL use the git repo created in Step 1.
   2. Make sure the git repo name in TMC is "wavefront"

 

Step 3 : Create a Kubernetes Secret containing Wavefront Token

1. From the cluster group context, navigate to Add-ons → Kubernetes Secrets 
1. Click on Create Kubernetes Secret 
2. Follow the instructions in the screenshot to complete the details. Make sure you have a wavefront token ready.

Click Finish, this would create Kubernetes Secret in the observability-system namespace. Once the secret is ready you will see the status APPLIED.

 

Step 4 : Add a Kustomization 

1. From the cluster group context, navigate to Add-ons → Installed Kustomizations 
1. Click on Add Kustomization
2. Provide the details about git repository created in Step 2
3. Add “clustergroup” path

 

      2. Click on Add Kustomization. This will apply kustomization to the fleet of clusters which are part of the cluster group. 

 

 

     3. Review the status at Cluster Group → Add Ons → Cluster Sync Status

 

 

Upgrade

To upgrade wavefront-operator take the relevant wavefront-operator.yaml from official wavefront repository and push it through your git repo.