Updates to Kubernetes Flex Reports: Dataset Migration and UI Changes

Products

• CloudHealth

Issue/Introduction

We are updating how our Kubernetes FlexReports are structured to ensure full compatibility across both our Classic and NX platforms. As part of this update, several key Kubernetes reports have been successfully migrated to a new, cross-platform data structure. While most of these changes happen automatically behind the scenes, you may notice some minor updates to the user interface, and in a few cases, you may need to recreate older reports if they could not be automatically migrated.

Cause

Previously, Kubernetes FlexReports were built using a backend structure called a "view," which was only compatible with our Classic platform and did not function in NX. To provide a seamless, unified experience across both platforms, we have migrated the underlying data source for these reports from "views" to "datasets."

Resolution

The transition to datasets is largely automated. Here is what you need to know about the changes and any actions you may need to take:

1. Affected Reports The migration applies to Flex Reports utilizing the following datasets:

• AWS Kubernetes Cost History

• Azure Kubernetes Cost History

• Kubernetes Containers Usage

• Kubernetes Nodes Usage

2. What You Will See in the UI When building or interacting with FlexReports, you will notice a few minor adjustments:

• Dataset Selection: The dropdown list will now display the new dataset options and will no longer show the older, view-based datasets.

• Label Adjustments: The text labels for certain measures and dimensions have been slightly updated to align with the new dataset definitions.

3. Action Required for Unmigrated Reports While the vast majority of reports were migrated successfully, a small number could not be updated automatically (typically due to invalid queries in the original report or deleted user accounts).

• Viewing: You can continue to render and view these older reports without any issues.

• Editing: You will not be able to modify or edit reports that failed to migrate. If you need to make changes to an unmigrated report, you will need to recreate it from scratch using the new dataset available in the dropdown menu.