# Drift Analytics

## What is Drift Analytics?

The new Profile Engine can also compare any managed cluster's RBAC configuration to any RBAC Profile, including automatically detecting drift for clusters with a profile applied. In addition, drift Analytics enables clients to quickly identify and resolve any RBAC Policy changes made on a cluster that is not compliant with the current profile.

## Testing

To begin, select a profile and a cluster to start analyzing the drift. As noted below, only active and published profiles are made available for testing. Therefore, no profile drafts are shown.

<figure><img src="/files/OrW0BDYi12EVg14IF7gZ" alt=""><figcaption></figcaption></figure>

Next, select the cluster.

<figure><img src="/files/A2tsjt4389Js5KhUaFmh" alt=""><figcaption></figcaption></figure>

Once the profile and cluster are chosen, click the *Show Drift Analysis* button. The evaluation starts and the overview screen below informs us it is processing the profile review.

{% hint style="info" %}
**Info**

Clicking outside the Drift Analysis screen stops the testing process.
{% endhint %}

<figure><img src="/files/y1rKVeuXo3KVqN4DmtQv" alt=""><figcaption></figcaption></figure>

## Drift Summary

Once the test completes, it will show a Drift Summary including the profile name, the cluster it is attached to, the total number of rules in Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings.

<figure><img src="/files/jWa9vlFxdKotWjVfXswK" alt=""><figcaption></figcaption></figure>

Below this, we have the final option to implement the new profile. Click the *Deploy Profile* button to install the profile.

### Roles / ClusterRoles / RoleBindings / ClusterRoleBindings Tabs

In each of the four tabs (*Roles, ClusterRoles, RoleBindings,* and *ClusterRoleBindings*), we see the total number of impacted roles, whether they are missing or compliant, and the number observed on the cluster. Below that, it shows the roles, namespaces, and the number of API/Permissions involved.

<figure><img src="/files/202qJtIwpLymcoEe3Ur3" alt=""><figcaption></figcaption></figure>

The following terms reveal the presence or absence of resources, and whether additional permissions are available.

* **Total X Affected:** The X value changes per tab depending on the role and presents the total number of Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings affected by the modification.
* **Missing on Cluster:** Indicates that these resources are missing on the cluster. To bring them into compliance, deploy them on the profile.
* **Not Compliant:** This means that these resources on the cluster are missing or have additional APIs or Verb Access. On the right side, you will see the term.
* **Present on Cluster:** This signifies that these resources are present on the cluster but are not included in the profile.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.platform9.com/managed-kubernetes/5.8/rbac-profiles/drift-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.