> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/best-practice-guides.md). # Best Practice Guides - [WEKA and Slurm integration](https://docs.weka.io/best-practice-guides/weka-and-slurm-integration.md): Explore the architecture and configuration of an HPC cluster using the Slurm workload manager for job scheduling and WEKA as the high-performance data platform. - [Configure Kubernetes and WEKA for CoreWeave SUNK](https://docs.weka.io/best-practice-guides/weka-and-slurm-integration/configure-kubernetes-and-weka-for-coreweave-sunk.md): Configure CoreWeave SUNK so NeuralMesh Axon keeps stable, non-contended CPU access while Slurm manages the remaining compute resources on shared nodes. - [Manage CPU allocations for WEKA and Slurm](https://docs.weka.io/best-practice-guides/weka-and-slurm-integration/avoid-conflicting-cpu-allocations.md): Allocate CPU resources between WEKA and Slurm workloads. - [Best practices for WEKA stateless client and Kubernetes](https://docs.weka.io/best-practice-guides/best-practices-for-weka-stateless-client-and-kubernetes.md): Use the WEKA Operator for WEKA CSI in Kubernetes. If using stateless clients, follow practices to reserve CPU, prevent contention, and ensure stable IO. - [Storage expansion best practice](https://docs.weka.io/best-practice-guides/storage-expansion-best-practice.md): Explore the best practices for expanding WEKA clusters, focusing on maintaining optimal performance in heterogeneous environments. - [Maximize GPU infrastructure resilience with NeuralMesh AXON](https://docs.weka.io/best-practice-guides/maximize-gpu-infrastructure-resilience-with-neuralmesh-axon.md): Deliver enterprise-grade reliability in converged GPU environments with failure domains. This approach keeps data protected and accessible, even when high-performance apps cause frequent reboots. - [WEKA and KVM integration](https://docs.weka.io/best-practice-guides/weka-and-kvm-integration.md): Explore the options for providing WEKA storage to virtual machines running on a KVM hypervisor. - [Deploy the WEKA client on a KVM server](https://docs.weka.io/best-practice-guides/weka-and-kvm-integration/deploy-the-weka-client-on-a-kvm-server.md): Provide WEKA storage to virtual machines through virtio-fs. - [Deploy the WEKA client on KVM virtual machines](https://docs.weka.io/best-practice-guides/weka-and-kvm-integration/deploy-the-weka-client-on-kvm-virtual-machines.md): Deploy WEKA clients in KVM guest VMs with SR-IOV and VF-LAG for isolated, high-performance storage access. - [Troubleshoot KVM integration issues](https://docs.weka.io/best-practice-guides/weka-and-kvm-integration/troubleshoot-kvm-integration-issues.md): Review the following known issues and their resolutions when integrating WEKA with KVM. --- # 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.weka.io/best-practice-guides.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.