> 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/rbac-profiles/profiles-engine-faq.md).

# Profiles Engine Faq

**Q**: Can I add the Profile Engine Agent to an existing cluster?

**A**: Yes, but it will cause a temporary cluster interruption. Version 5.4 will include the agent in the Add-on Manager.

***

**Q**: When I deploy a profile, what happens to pre-existing policies on the cluster?

**A**: Existing policies will have any missing verbs or bindings added. ***Nothing will be removed***. Future releases will include the ability to add and remove verbs/bindings from existing policies.

***

**Q**: Does this work on all clusters, including EKS, AKS, and GKE?

**A**: No. Version 5.5 will introduce support for Add-on Manager and Profile Engine.

***

**Q**: How do Cluster RBAC Profiles differ from RBAC Settings?

**A**: The RBAC settings UI enables users to create and edit **individual** Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings obects. Cluster RBAC Profiles are a templating mechanism to enable operators to manage cluster RBAC at scale using the concept of Profiles.


---

# 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/rbac-profiles/profiles-engine-faq.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.