> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.7/platform9-managed-add-ons-overview/profile-agent-addon.md).

# Profile Agent Addon

## Introduction

The Platform9 Profile Engine add-on simplifies RBAC administration and improves conformity across multiple clusters. It allows clients to:

* Create RBAC profiles based on existing clusters
* Edit profiles to ensure they contain the exact policies required
* Deploy the profile to managed clusters
* Employ drift analytics to analyze the cluster for non-conformance

For more information, read [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/kubernetes/rbac-profiles/README.md)

## YAML Specification

{% tabs %}
{% tab title="YAML" %}

```yaml
apiVersion: sunpike.platform9.com/v1alpha2
kind: ClusterAddon
metadata:
  labels:
    sunpike.pf9.io/cluster: '<clsuuid>'
    type: pf9-profile-agent
  name: <clsuuid>-pf9-profile-agent
  namespace: default
spec:
  clusterID: '<clsuuid>'
  override: {}
  type: pf9-profile-agent
  version: 2.0.0
  watch: true
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-kubernetes/5.7/platform9-managed-add-ons-overview/profile-agent-addon.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.