Credential Rotation Management for VMware Aria Operations Management Pack for Kubernetes

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Aria Operations Management Pack for Kubernetes adapter enters a "Warning" or "Invalid credentials" state following credential rotation in TKG or Supervisor clusters. The adapter relies on static secrets (tokens or certificates) that do not automatically synchronize when underlying cluster authentication mechanisms are rotated

Environment

Aria Operations 8.18.x

Cause

Adapter authentication relies on static Kubernetes secret objects. These objects maintain current credentials until manually updated within the Aria Operations adapter configuration.

Resolution

Perform one of the following procedures after rotating credentials on TKG or Supervisor clusters:

1. Manual Update: Navigate to the Aria Operations Management Pack for Kubernetes adapter configuration in the UI. Update the credentials for the affected adapter instance to match the newly generated token.
2. Manual Update: Implement an automated workflow to update adapter credentials via the Aria Operations API following rotation events. This method is recommended for large environments with frequent security rotation policies.

• • Utilize the Aria Operations REST API to update the credential field for the specific adapter instance identified by ####.  Refer to VMware Aria Operations API Programming Guide (8.18) for more information. 
  • Ensure the integration pipeline triggers this API call immediately after the cluster rotation is finalized.

Additional Information

Subscribe to this article (reference: Subscribe to a Broadcom knowledge article by article or product) to receive updates regarding potential product enhancements