> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/cloud/components/shapes.md). # Shapes Predefined instance types and sizes Shapes are used to define sizes of instances and to allow control over node selection for new instances. If there are high performance nodes and low performance nodes these can be placed into two instance shapes such as `m2-standard` and `m3-standard` . This will allow the user to select the shape suitable for the instance and a node will be selected based on which node has the most available CPU and memory. Shapes are associated with nodes by matching roles. This can be done for example by adding `shape-m2` to the shape *Roles* then adding that same role to all the nodes that fit that shape. ### Flexible Shapes Flexible shapes define default processor and memory size but allow these to be overridden when creating the instance or in the pod spec. --- # 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.pritunl.com/kb/cloud/components/shapes.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.