> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/etcd-recommendations-for-platform9-stack.md). # ETCD Recommendations for Platform9 Stack ## Problem This article talks about resource recommendations for ETCD component in the Kubernetes clusters deployed on Platform9 Managed Kubernetes (PMK) or Platform9 Self Managed Cloud Platform (SMCP) environments. **Please Note:** The recommendations suggested here come from a broader perspective of known issues and the recommendations on the [Official ETCD Documentations](https://etcd.io/docs/v3.5/op-guide/hardware/) and should be not considered as an absolute hardware recommendation for optimal ETCD performance. The performance of ETCD has numerous contributing factors and in cases of issues, would often need expert troubleshooting. However, these can certainly be treated as minimum recommendations for an optimal ETCD performance. Environment * Platform9 Managed Kubernetes - v4.0 and Higher * Platform9 Self Managed Cloud Platform - v5.9.1 and Higher ## Answer * For small clusters, below are the minimum resource and disk recommendations. * 4 vCPUs, 8GB Memory * For large clusters, below are the minimum resource and disk recommendations. * 8 - 16 vCPUs, 16 - 64GB Memory. **Disk recommendations:** Fast backend disks are quintessential for ETCD Performance and Stability. Typically, SSDs are recommended to be used as ETCD storage. If Spinning Disks are to be used as ETCD storage, the recommendation is to use the fastest possible disk of RPMs at around 15000 --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://platform9.com/kb/pmk/frequently-asked-questions/etcd-recommendations-for-platform9-stack.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 `build a script that syncs our docs to a CMS` 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.