> 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/self-managed-cloud-platform/5.11/managed-cluster-add-ons/resource-mgmt-overview.md). # Resource Management Overview Kubernetes typically abstracts the organization of workload details away from the user. However, it sometimes becomes necessary to guarantee resources like CPU, memory, and device locality optimizations needed for the nodes to operate at peak efficiency. Situations that require high-efficiency processing like data analytics, machine learning, scientific computing, financial services, and telecommunications can be adjusted by policies that better regulate the actions governing these elements. The two management policies that specifically address these demands are the Topology Manager and the CPU Manager. These management tools are part of the Kubelet agent that coordinates the components responsible for these optimizations. --- # 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/self-managed-cloud-platform/5.11/managed-cluster-add-ons/resource-mgmt-overview.md?ask=&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.