Wavefront Proxy Installation and Upgrade Issues with HELM

Products

• Observability
• DX OpenExplore

Issue/Introduction

Error response from daemon: manifest for projects.registry.<domainName>/tanzu_observability/proxy:13.7 not found: manifest unknown: The named manifest is not known to the registry.

dont see the image tag for, appear to be missing (JFrog Platform) https://projects.registry.<domain>/ui/packages/docker:%2F%2Ftanzu_observability%2Fproxy

Wavefront Proxy installation in Kubernetes environments where clusters were deployed using Helm or TKG (Tanzu Kubernetes Grid) are missing images for wavefront proxy v13.7 when upgrading. 

Environment

• Wavefront Proxy - Helm deployment.
• Wavefront Collector for Kubernetes

Cause

projects.registry.<domainName>/tanzu_observability/ no longer used for Wavefront Proxy version newer then 13.4 or Wavefront Operator-for-Kubernetes newer than Release v2.17.2

Resolution

As the Helm method of deploying a Wavefront-collector-for-Kubernetes was archived in December 2023. Customers needing to upgrade, install or reinstall proxies are directed to use the currently supported methods mentioned below.

• Observability for Kubernetes Operator:  Replacement for Wavefront Collector for Kubernetes. 

  • Ensure your cluster meets the prerequisites outlined in the installation guide which can be found on GitHub: Observability for Kubernetes Operator
    
    
  • For this deployment method first identify the Operator release that includes the desired Proxy version. Operator Release Versions  
    • For example, "Release v2.30.0" deploys proxy version 13.7.
      
      
  • Next, there are two locations where you can find all the necessary kubectl apply commands and wavefront.yaml configuration and instructions for deploying the Observability Operator. 
    • Within the UI, See Kubernetes Integration
    • GitHub: Deploy the Monitoring Agents with the Observability for Kubernetes Operator 
      
      
• Manual Installation for Proxy Upgrade: For users who prefer manual installation, you can follow these steps:
  • • After reviewing the current proxy configuration, Remove the existing proxy deployment from the cluster.
    • For the latest proxy see release link on our Github wavefrontHQ/wavefront-proxy page
    • For instructions on manual proxy installation please review our documentation at https://techdocs.broadcom.com/ 
      
      
• Custom deployment scripts that used legacy image location "tanzu_observability/proxy" must be updated to use the new location. 
  • If your proxy fails to deploy after upgrading using a custom script, verify your YAML configurations is using the supported deployment methods and the current image repository.

With the Broadcom acquisition of VMware, current image repositories have been updated to:

• Operator image location is under "caapm/kubernetes-operator"
• Stand-alone Kubernetes Proxy Image is under "caapm/proxy"

Additional Information

• New and Changed Integrations (2022) 
• Run a Proxy in a Kubernetes Container
• Run a Proxy and Telegraf in a Docker Container

If you have any issues or need assistance with the upgrade, please don’t hesitate to reach out to Wavefront support team.