Tanzu Platform Hub: Updates to AWS/Azure/GCP Event Streams

Products

• VMware Tanzu Platform

Issue/Introduction

These instructions are for all accounts other than Secure Clouds/Guardrails only customers.  As of October 31st, 2024 Secure Clouds/Guardrails went End of Life (EOL) and customer instances and data were deleted.  If you have additional questions, please reach out to your Broadcom Account Team.

VMware Tanzu Platform will be migrating our backend cloud hosting service from AWS to GCP resulting in changes to the endpoints utilized for our data collection workflows.  In order to maintain continuity of service our customers will have to make associated changes as described below.  Failure to make such changes will result in data inconsistencies post migration. 

Updates to AWS/Azure/GCP Event Streams

• Post GCP migration, all cloud accounts (AWS/Azure/GCP) onboarded to hub which had EventStream Event Monitoring connected, will start showing as ‘Not Configured’ in the Tanzu hub configure/accounts UI as they are no longer connected to our AWS infra. 
  • From the Tanzu Platform hub UI, navigate to Setup & Configuration > Cloud Accounts and select the applicable cloud account to verify.  

Resolution

Customers will have to run the event stream configuration steps from the Tanzu UI for all cloud accounts they wish to re-enable. 

1. 1. For all cloud accounts browse to Setup & Configuration >  Cloud Accounts, you will see that accounts have "Not configured" status for the "Event Monitoring Column" (the screen shots below show AWS account as an example but the steps apply to AWS, Azure and GCP). 
      
   2. Click the chevron (double arrows) next to the account to access account details. Here you can click "Configure Event Monitoring"
      
      
      
   3. Follow the steps to activate Account Onboarding for event stream
      
      
      
   4. After some time, the status of the Event Monitoring will change to a check mark indicating the event stream is working.
      
      

Updates to Remote Collectors

Kubernetes

All k8s collectors previously attached to AWS will now show collector status as "Offline" as they are no longer connected to the back end system. 

1. For collectors installed via UCO workflow the collector version will be automatically updated.
2. For collectors installed via Install.sh workflow the collector will be shown as "offline", these need to be manually detached and re-attached by Customer by following UI instructions.  Customer may then do a collector update. 
   1. All Collectors will have Status "Offline"

                

                b. Customers will have to detach and re-attach the onboarded VCF collectors.

               

               

c.Re attach

                

For collectors bootstrapped using an automated workflow, the automation should auto update.  This should be verified by showing the collector status as "on-line"  

VCF

1. All VCF collectors will have Collector Status as "Offline"
   
   
   
2. Customers will have to detach and re-attach the onboarded VCF collectors.
   - Detach
   
   
   
   
   
   

          
    - Re-Attach 

TAS

1. Customers will have to delete the TAS collector tile in Opsman.
2. Detach the foundations onboarded in Hub UI.
3. Install new tile for TAS collector (new version in-conjunction with the GCP migration)
4. Re-Attach Foundation in Hub UI.
5. Confirm that the collector is in the ready state.