A Profile to Rule Them All: The Key to Cluster Consistency

Introduction

As organizations accelerate their hybrid multicloud journeys, a silent infrastructure bottleneck is emerging. It isn’t storage performance or compute capacity—it’s operational complexity. Today, IT teams are no longer managing just a couple of isolated clusters in a central datacenter. They oversee a massive, distributed fleet that stretches across data center locations,  regional hubs, public clouds via Nutanix Cloud Clusters (NC2), and hundreds of remote edge locations. When an environment grows to this scale, a critical question arises: How do you keep your entire infrastructure secure, updated, and aligned with corporate standards without burning out your IT teams?

In large-scale environments, settings inevitably change over time. A local administrator tweaks an NTP server to troubleshoot a time-sync issue, a firewall change requires a new DNS target, or a manual script fails to update a filesystem allowlist on a few isolated nodes.This is known as configuration drift. Historically, identifying and preventing drift meant logging into dozens of clusters one by one to verify the configuration settings.

The solution to these problems lies in Nutanix Cluster Profiles. While this capability debuted in previous releases, we are taking a moment to spotlight how it further advances the operational simplicity that defines the Nutanix platform.

What are Nutanix cluster profiles?

A cluster profile is a centralized blueprint for your core infrastructure settings. Instead of managing configuration options at the individual cluster level, administrators define a Cluster Profile in Prism Central and assign it to a group of clusters.

Currently, Cluster Profiles allow organizations to standardize critical environmental settings across their infrastructure. These include alert and notification configurations like SMTP and Syslog servers. They also cover general settings like Pulse, various network configurations including Name servers, NTP servers, and SNMP, alongside security features like the Filesystem allowlist.

Once the Cluster Profile is defined and the settings are configured, it can be assigned to any number of clusters. When modifications are made to the configuration settings of any of these clusters in the future, it would show up as a drifting cluster and corrective action can be taken by the administrator with a single click. There is also an option to import settings from an existing cluster rather than creating the Cluster Profile from scratch.

How Cluster Profiles Benefit Our Customers

1. Efficiency & Scaling

For our customers deploying new infrastructure—whether standardizing regional datacenters or rolling out edge nodes across retail or manufacturing sites, this is largely beneficial. Instead of manually configuring parameters on every new cluster, you simply bind the new cluster to an existing Cluster Profile. The cluster inherits all settings quickly, allowing your IT team to manage a large footprint efficiently.

2. Drift Detection & Support Compliance Efforts

You can’t fix what you can’t see. Cluster Profiles continuously monitor your entire Nutanix fleet. If a local change is made that deviates from the Cluster Profile, Prism Central immediately flags the cluster as "drifting cluster". Administrators can then remediate the drift with one click and the cluster will fall back into alignment, this is designed to help promote predictability across the environment. 

3. Governance

For organizations in highly regulated sectors like finance, healthcare, or government, proving compliance is a continuous burden. Cluster Profiles offer a centralized dashboard for compliance status. Instead of logging into each cluster, you can quickly demonstrate your cluster configurations across your Nutanix environment to assist with governance

How can I leverage this feature?

It’s very easy to get started. For this example we will focus on a cluster setting that is accidentally deleted from the cluster, its discovery and how to quickly return the cluster to the desired state. A cluster profile has already been pre-created with the name “durham_clusters”. In the profile we have both Pulse and NTP server settings configured. We will focus on the configuration of the NTP Servers. As you can see three NTP servers are configured in the cluster profile. These are also the same NTP servers that were applied to the cluster during the initial deployment.

From here you simply assign the profile to the cluster. Once applied, the cluster will be checked to validate its existing settings against those configured in the assigned cluster profile. Any differences are changed to reflect the configuration within the profile. As you can see below the cluster has the same NTP servers configured and matches the configured cluster profile. This will result in the cluster being in compliance with the desired settings.

As mentioned earlier, cluster profiles are great for driving consistency in the application of specific cluster settings. Let’s say someone accidentally removes or modifies a setting on an assigned cluster, this action could go unnoticed for quite some time. This will create a drift in the actual state vs the desired state, resulting in a non-compliant configuration. A drift that could go un-noticed for longer than a business is comfortable with.

As the above image notes, the assigned cluster is “Non-compliant” to the applied policy. This discovery will occur as part of regular polling (every 24hrs) that runs to confirm that all clusters assigned to a given policy are in compliance with the desired state as configured in the profile. Additional details are available on which setting has drifted, making it easy to understand what needs to be restored to the desired value. In our case the cluster has a mismatch in the configured NTP servers. In this example we intentionally removed one of the configured NTP servers from the cluster settings.

Restoring settings to your desired configuration is straightforward; you simply need to reapply the profile through the Prism Central UI. Similar to the initial application of the profile, the cluster will be evaluated and the settings in non-compliance will be re-applied to the selected cluster. This is accomplished through Prism Central leveraging APIs to communicate directly with the impacted cluster to quickly restore the NTP server configuration.

While this is just a single cluster example, imagine needing to make a change across multiple clusters at once? What if instead of the deletion of a setting, a new entry needs to be added? What if you had clusters across 2, 5, 10 or more sites that needed to be changed? With Cluster Profiles it's simple: add the new entity to the desired cluster profile(s) and re-apply. In the background each of the assigned clusters will have the new entity configured. Configure once, apply to many! This allows you to spend less time administrating and more time building!

Conclusion

As the world moves toward highly distributed cloud architectures, success belongs to organizations that embrace automation and standardization. Nutanix Cluster Profiles eliminate the tedious, repetitive tasks that slow businesses down, replacing them with a streamlined, fleet-wide governance model. It is designed to help promote predictability across the environment.

©2026 Nutanix, Inc. All rights reserved. Nutanix, the Nutanix logo and all Nutanix product and service names mentioned are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. All other brand names mentioned are for identification purposes only and may be the trademarks of their respective holder(s).This content reflects an experiment in a test environment. Results, benefits, savings, or other outcomes described depend on a variety of factors including use case, individual requirements, and operating environments, and this publication should not be construed as a promise or obligation to deliver specific outcomes.