Container is not available alert in Aria Operations after upgrading Tanzu Kubernetes cluster

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When a Tanzu Kubernetes cluster that is integrated with Aria Operations is upgraded an upgrade container otherwise known as upgrade pod is created to carry out the actual upgrade.
• When the upgrade has completed Aria Operations generates an alert that the 'Container is not available', cancelling the alert results in the alert activating again on the next collection cycle.

Environment

Aria Operations 8.18.x

Cause

• Upgrading a Tanzu Kubernetes cluster generates an upgrade job which in turn creates an upgrade container otherwise known as upgrade pod.
• Aria Operations during normal collection detects this new upgrade pod/container has been created and begins to monitor it.
• When the upgrade completes the pod/container is shutdown but not removed nor is the upgrade job removed, this is per design.

Resolution

• Presently the only way to resolve the alert in Aria Operations is to delete the upgrade pod/container in Kubernetes.
• Note do not delete the upgrade job and only remove the upgrade pod.
  • Deleting the upgrade job will result in the job being recreated and a new upgrade pod.