Governance Navigation Change

We’ve heard your feedback! Governance and its sub-pages are now pulled out of the Setup section and moved to a new top-level section in the navigation pane, after Recommendations and before Setup. Please note URLs will not change as part of this move.

Amazon OpenSearch Rightsizing – Public Beta

We are excited to announce the public beta release of our new Amazon OpenSearch Rightsizing Recommendations. With Amazon OpenSearch Service, you can search, analyze, visualize, and secure up to petabytes of text and unstructured data for a number of use cases such as log analytics, application search, enterprise search, and more.

Built on our new rightsizing engine, our new OpenSearch Rightsizing feature generates recommendations in seconds, and offers up to 3 recommendations for each cluster. Complete with a new user interface, this feature delivers:

Cost and savings summaries
Customizable efficiency targets for resource utilization
Upsizing recommendations
The ability to drill down into each master/data node cluster to view usage

Data from our new rightsizing engine is available via a GraphQL API that enables you to programmatically set efficiency targets and consume recommendations. Learn more about our new rightsizing engine in this VMware Docs article.

Public Beta for Kubernetes (request-based) Rightsizing – Now Available for Azure

We are excited to announce the public beta release of Kubernetes (request-based) Rightsizing for Azure. Back in March, we released this service for Kubernetes-based workloads running on AWS, and today we are expanding support to K8 workloads running on Azure.   Built on our new rightsizing framework, Kubernetes Rightsizing provides recommendations for changing container Requests based on usage of CPU and memory.

Features include:

Custom Efficiency Targets: Users can customize these recommendations by setting specific targets for CPU and Memory. Users can choose to use CPU/Memory Averages or Maxes and set a desired range from 1% to 120% for each metric.
Filtering: Users can filter by cluster, namespace, or workload to drill down and look at a sub-set of resources.
FlexOrgs Aware: Kubernetes Rightsizing Recommendations work with FlexOrgs, so users in sub-OUs can only see and act on clusters that they have permission for.

Private Beta for New Kubernetes Cost History Report – Now Available for Azure

We are extending the private beta for the Kubernetes Cost Report to K8s running on Azure and making updates to the feature. These updates include the following changes:

Renaming the “Apportioned cost” measure to “Cost Allocation by Usage”
Addition of a new measure: “Cost Allocation by Requests”

The Kubernetes Cost History Report is backed by FlexReports and can be accessed via the FlexReports API. In tenants that are enabled for the private beta, you can access these reports by going to Reports -> Containers and selecting Kubernetes Cost History.

We’re currently opening this report to a limited set of private beta customers to complete validation and testing. If you’re interested in participating, please contact your Technical Account Manager to determine eligibility.

Update to FlexOrgs – ‘Select All Visible’

We are beginning a series of improvements to account management in FlexOrgs, working towards more simplified bulk actioning. As part of this, we have added the ability to select all visible rows in a table with the FlexOrgs > Accounts pages.

Updates to Kubernetes Usage Reports for FlexOrgs

Based on customer feedback, we are changing the measures in the new Kubernetes Usage Reports to match the measures in the classic Kubernetes Resources and Kubernetes Allocation reports.

This will impact the following reports:

Kubernetes Containers Usage

Kubernetes Nodes Usage

Azure Savings Plans Improvements

Azure Savings Plans are now treated as a direct cost in the Cost History report, are usable in Perspectives, and have their own Asset Report. In order to get Azure Savings Plans data in the platform, please follow the instructions found in VMware Docs.